Windows XP

[ChaosOverlord]

At the risk of sounding redundant, I pose this question to any who read it. I recently just upgraded to Windows XP and I had given up on doom wad editing for some time. Now I've found myself in the mood for it again, and much to my dismay ... Wintex no longer works. I'm assuming this is because I am running a new operating system. I know that this isn't really a message board for Wintex support, but I do know that most of you here are editors, and in being editors, you obviously still have access to tools such as Wintex and the like ... so ... my question basically is: Is there a way to make Wintex work on newer OSes, or is there some sort of new program that everyone is using to do their graphics, music, sounds, lump editing? I'm at a complete stand still in my editing process until I find something that works, so please ... any help would be greatly appreciated.

[Medricel]

I suppose you could XWE, but I've never really run into problems using WinTex on Windows XP before... It wasn't the latest version though...
Also, do you have that VBRun300.DLL or whatever it required?
[offtopic]...and speaking of which, I still need to get around to reinstalling it...[/offtopic]

[ChaosOverlord]

Hm. I tried downloading VBRun300.dll and put it into my system folder, but still no luck. The exact message I get when I try running Wintex is as follows:
(blue title bar)16 Bit Windows Subsystem

C:\WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications. Chose 'Close' to terminate the application.

Oh. I'm using Windows XP Pro, if that makes any kind of difference. Any ideas, or am I out of luck?

[chaoscentral]

Hmmm... it might be your windows because I'm currently running Windows XP Pro and I can use WinTex. Make sure you are using WinTex 5 and you have the VBRun300.dll and Threed.vbx files.

[Kirby]

I had some problems when I tried using WinTex on WindowsXP. After delving into the problem a little, I found a solution.

First things first - make sure you have VBRUN300.dll in your wintex folder. It cannot run without that.

The problem I got after that was that it could not find shell.dll and I figured out how to fix this.

1)Go to c:\windows\system32
2)Copy the file "shell.dll"
3)Go to c:\windows\system
4)Paste Shell.dll

It should work from there

EDIT: I suggest you get the most recent version of wintex before you do this as well

[MartinHowe]

FWIW, I am running 4.3 in XP Pro with no problems. All it needed was shell.dll and vbrun300.dll in %SystemRoot%\System (no need for the latest versions, unless they have a feature the user wants).

[ChaosOverlord]

Sigh!

Well, thank you for all the help guys, but none of it fixed my problem. I really appreciate the reply, though. I'm so lost without Wintex. I can't do ANYTHING. ): I just don't understand. What could the problem be? Especially if everyone else's works. I must have some kind of setting wrong or something.

I guess I'll mess with a different program ... but if you guys ever come up with any more suggestions, please let me know! I'm so comfortable and used to Wintex. It would be a joy to use it again.

Anyway! Thanks for all your help.

edit: Hmm, well apparently it's doing this for ALL DOS based programs. Know of anything offhand that could cause my dos based programs to not run properly?

[Medricel]

Well, it seems to potentially have something to do with that AUTOEXEC.NT file... posted below is the contents of mine... see if its perhaps somewhat similar.

---

@echo off

REM AUTOEXEC.BAT is not used to initialize the MS-DOS environment.
REM AUTOEXEC.NT is used to initialize the MS-DOS environment unless a
REM different startup file is specified in an application's PIF.

REM Install CD ROM extensions
lh %SystemRoot%\system32\mscdexnt.exe

REM Install network redirector (load before dosx.exe)
lh %SystemRoot%\system32\redir

REM Install DPMI support
lh %SystemRoot%\system32\dosx

REM The following line enables Sound Blaster 2.0 support on NTVDM.
REM The command for setting the BLASTER environment is as follows:
REM SET BLASTER=A220 I5 D1 P330
REM where:
REM A specifies the sound blaster's base I/O port
REM I specifies the interrupt request line
REM D specifies the 8-bit DMA channel
REM P specifies the MPU-401 base I/O port
REM T specifies the type of sound blaster card
REM 1 - Sound Blaster 1.5
REM 2 - Sound Blaster Pro I
REM 3 - Sound Blaster 2.0
REM 4 - Sound Blaster Pro II
REM 6 - SOund Blaster 16/AWE 32/32/64
REM
REM The default value is A220 I5 D1 T3 and P330. If any of the switches is
REM left unspecified, the default value will be used. (NOTE, since all the
REM ports are virtualized, the information provided here does not have to
REM match the real hardware setting.) NTVDM supports Sound Blaster 2.0 only.
REM The T switch must be set to 3, if specified.
SET BLASTER=A220 I5 D1 P330 T3

REM To disable the sound blaster 2.0 support on NTVDM, specify an invalid
REM SB base I/O port address. For example:
REM SET BLASTER=A0

EDIT: This page seems to have some more info as well:
http://unodocs.nmsu.edu/RoboDocs/WebHel ... /ji_05.htm

[ChaosOverlord]

Well, bro! You are my new hero! Thanks to that helpful link you posted, everything is back to working order. It had to do with the Service Pack 2 installation. I really appreciate you going out of your way to find that link and help me out. That's awesome! And now I have Wintex again! YAY. Alright.. I guess I'm off to mod at long last! Thanks again! (:

[Medricel]

No problem... I had been spending about 10 minutes hounding Google for THREED.VBX, so I figured a quick extra search wouldn't hurt Good to see that your problem was easily fixable... Strange though... I have SP2 and I had the file no problem... (Oh well, stranger things have happened, I guess )