DOS ain't dead

I like HX, obviously, but normally I don't run GUI apps because a). I can't think of much that I'd want to use, and b). stuff I tried never works. Anyways, here's some comments I thought might be vaguely interesting.

Recently I've done a lot of digging up on ID Software's Doom (esp. for DOS source ports and FreeDoom), Quake (also Hexen2), and now Wolfenstein 3D. All of these are open source but not freeware.

http://img268.imageshack.us/g/wlf4sdl1.gif/

EDIT: This is only two snapshots, which are intentionally devoid of any "illegal" symbols.

This shows that I got Wolf4SDL (demo .EXE, for shareware episode, 1WOLF14.ZIP) to work on my Pentium 4 (HXRT + HXGUI: needs 386+, VESA2). These were screenshots taken by HX itself (menu key), converted to .GIFs from (large, 500K !!) .BMPs by Pictview.


 Directory of A:\

08/01/2009  04:18 PM            45,161 KERNEL.SYS
12/03/2007  05:00 AM            66,932 COMMAND.COM
11/27/2009  09:00 AM             4,006 XMGR.SYS
12/10/2009  10:42 PM               290 FDCONFIG.SYS
12/11/2009  01:18 AM               469 FDAUTO.BAT
12/03/2007  05:08 AM             5,089 CTMOUSE.EXE
11/27/2009  09:00 AM             1,536 RDISK.COM
12/10/2009  03:53 PM           881,360 wolf4sdl.p8f
12/07/2009  11:57 PM            95,280 paq8f.exe
09/25/2009  08:19 AM               512 FINDDISK.COM
03/16/1996  02:00 PM             4,096 EZEDIT.COM
06/17/1994  01:03 AM             2,925 XGREP.COM
12/10/2009  04:04 PM           124,359 hx.p8f
12/10/2009  10:38 PM           115,179 msvcrt.p8f
12/11/2009  01:17 AM            31,695 W4SDLBMP.P8F


Both SDL.DLL and SDL_MIXER.DLL (which I renamed / hacked to SDL_MIX.DLL, not sure if totally necessary) are inside the WOLF4SDL archive. MSVCRT.DLL is from XP (since Vista's doesn't work??), approx. 343000 bytes. I never got it working under DOSBox (wrong MSVCRT) or DOSEMU (no relocs), both of which are presumably due to using MinGW or MSVC (hence recompiling with OpenWatcom should solve both problems). However, you must "set SDL_AUDIODRIVER=dummy" since both "dsound" (default) and "waveout" don't work (or at least only work on SB-compatibles, e.g. not on my P4's EMU10k1) and hence won't let the game even start. Original Wolf3d supports PC speaker or Adlib or Soundblaster. There's a third-party patch called WOLFSPK4.EXE that makes the PC speaker output digital .WAV sounds [sounds better], but it doesn't seem to work in the shareware episode [only full??].)

Mouse mostly worked but had trouble moving forward for me, might be my mouse itself, who knows. I don't prefer the mouse at all, actually. Even keys had some minor troubles. Main was that it seemed to take a step and "pause" ever other move with NumLock on (so I turned that off). The minor nit was that for some reason Shift (run) plus left arrow or right arrow seemed to change weapon. I'm not sure if that was a "feature" of Wolf4SDL or not (doubt it).

Why? No reason, just wanted to test it. (EDIT: Well, for instance, full-screen without status bar isn't present in Wolf4GW.) The predecessor to Wolf4SDL (2008) was Wolf4GW (DOS/4GW, aka OpenWatcom) from 2006. I've recently re-compiled that myself (had to, my full copy is the Apogee version, default .EXE is Activision), even made a simple .BAT to do so (soon to be posted to OW newsgroup) since the default .ZIP only contains IDE project files (ugh). Hence it can be built in DOS w/ SFNs, even. (Wolf4SDL does not support PC speaker.) Actually, Wolf4GW was converted to C++, for some odd reason.

All other versions of Wolfenstein 3D used Borland C 3.x and TASM. Heck, Mike Chambers (leetIRC dude) ported it to his 8086/VGA/640k/4.77 Mhz, but it runs really slowly (5fps) in a small "windowed" view. He also added a cheat menu, though. He gave me the sources, but the default .EXE itself was incompatible with my data (and I don't have an 8086 nor BC++ 3).

BTW, the original WOLFSRC.ZIP had two .EXEs, original real-mode WOLF3D.EXE (which optionally uses XMS or EMS if found) and Borland 16-bit extended WOLF.EXE (needing DPMI16BI.OVL + RTM.EXE) although I never got the latter to work under DOSBox. (But I forgot that perhaps HDPMI16 / DPMILD16 would work?????)

P.S. I really hate the fact that it's such a disputed game (e.g. Germany), but there are so many mods (Hotel Romanstein, Barneystein, Halloween, Christmas, etc.) there should be a legal way for such users to still play the game (whose engine is also allegedly the basis of Catacombs 3D, Blake Stone, R.O.T.T., etc).

EDIT: Wolf4GW seems abandoned, and I got the idea to run under HX because the author suggested such to someone on some forum as a way to still run it under DOS. I think his main motivation for moving to SDL was portability and also getting sound to work well / correctly under modern NT-based Windows.

P.P.S. I still think this parody is funny.

> P.P.S. I still think this
> parody is funny.

LOL, I saw only original version where he's playing UT or such newer game, don't remember...

---
DOS gives me freedom to unlimited HW access.

> I like HX, obviously, but normally I don't run GUI apps because a). I can't
> think of much that I'd want to use



> and b). stuff I tried never works.

MPLAYER used to (I mailed Sherpya about this just yesterday ...)

GNASH never did usefully (and what is the latest version having a Win32 binary ???)

VLC sucks even on Windaube, so what

Firefox used to work ( 2007-04-01 )

Puzzle "15" done with FASM does work

Many games do

AspackDie - I didn't test ... OOps, file selector

BOCHS and QEMU do and are very useful

> http://img268.imageshack.us/g/wlf4sdl1.guf/
> screenshots taken by HX itself (menu
> key), converted to .GIFs from (large, 500K !!) .BMPs by Pictview

PNGOUT, OPTIPNG and DEFLOPT are your friends for next attempt

> Mike Chambers (leetIRC dude)
> ported it to his
> 8086/VGA/640k/4.77 Mhz

Yeah

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

> > I like HX, obviously, but normally I don't run GUI apps because a). I
> can't
> > think of much that I'd want to use
>
>
>
> > and b). stuff I tried never works.
>
> Firefox used to work (
> 2007-04-01
> )
>

Egads, what guts to try Firefox!!! Now that's a little ambitious!

BTW, I got Wolf4SDL to work on my Vista laptop under DOSBox 0.73 (don't ask me why, heh). First, I did "copy c:\windows\system32\msvcr71.dll msvcrt.dll", "copy SDL_MIXER.DLL SDL_MIX.DLL", hexedited the two references to the mixer DLL inside itself (-> "SDL_MIX.DLL\0\0") and WOLF4SDL.EXE (needed 'cause DOSBox API doesn't truncate LFNs to SFNs the same way as real DOS), "set SDL_AUDIODRIVER=dummy", and voila! If you don't disable audio, it won't even start up (seems to hang). And yes, obviously, it's extremely slow (1 fps), worse than Mike's 8086, but hey it works there too! (Obviously HX + Wolf4SDL in native DOS or DOS version under DOSBox is normal speed.)

P.S. The main issues I thought somebody (Japheth?) would be interested in were the Numlock quirk (or is that a debugging tool??), Shift + l/r arrows (feature??), and most importantly the fact that no supported sound doesn't just let you continue anyways and play silently. (BTW, I read that ScrLock might be needed for mouse in windowed mode [EDIT: yup!].)

>
> 12/10/2009  03:53 PM           881,360 wolf4sdl.p8f
> 12/07/2009  11:57 PM            95,280 paq8f.exe
> 12/10/2009  04:04 PM           124,359 hx.p8f
> 12/10/2009  10:38 PM           115,179 msvcrt.p8f
>

Forgot to mention that I used paq8f -5 for better compression. Probably not optimal (slightly slow even with SSE2, needs 200+ MB RAM), but I was short on time, so I didn't want to test every possible compressor, so I just grabbed what I knew would work. The HX archive only has \BIN\ from HXRT and HXGUI, no docs, and I replaced the WSOCK32 with the stub version for smaller size (since I knew I didn't need networking). I guess you could put it on two floppies instead, but that idea somehow annoyed me.

BTW, I posted my .BAT to compile Wolf4GW (real DOS predecessor to Wolf4SDL) with OpenWatcom in case anybody is curious.

> BTW, I got Wolf4SDL to work on my Vista laptop

natively ???

It didn't work for me, I have no idea about this project and didn't find the required data files to download ...

(yesterday)

> taken by HX itself (menu key), converted to .GIFs from (large, 500K !!) .BMPs by

There is nothing wrong about a 640x480x24bpp BMP hogging only 921'654 Byte's

> http://www.lootube.com/watch?v=5f7gW5X24ao
> http://www.lootube.com/watch?v=QGQkszIEMiw

Does it play for you in Open Source Arachne ??? You whine about "closed source" and "compatibility", but promote such stuff even more

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Fixed them for you, next time got a better way to do ???

http://tinyvid.tv/show/3nrej1hv0jcsz

http://tinyvid.tv/show/2g0zu7wft1qb1

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

> > BTW, I got Wolf4SDL to work on my Vista laptop
>
> natively ???

Yes. No sound, though, and IIRC CuteMouse doesn't like my BIOS, so I didn't use that.

FreeDOS on P4 - yes
FreeDOS on AMD64x2 - yes
FreeDOS on P166 - yes (but slow)
under DOSBox - yes (but very slow)

> It didn't work for me, I have no idea about this project and didn't find
> the required data files to download ...
>
> (yesterday)

I've made a boot disk, and (obviously) it even works on my P166 w/ 32 MB of RAM now (with UNIVBE and old-ass Win95 MSVCRT.DLL). Of course, since that has no MMX, PAQ8f is dirt slow (67 minutes!) vs. 2 mins. on my AMD64x2 laptop, and that's at lowest / fastest compression! Yeah, okay, maybe it doesn't need to be all crammed on one disk. Maybe I should've made an HX disk and put the game files separately on another disk. At least that would be fast. Sue me, I just thought one disk was ideal.

It might be pointless, but I'm going to document exactly what I did for this disk. Heck, except for MSVCRT, I could upload it (and sources, of course) for you if you really wanted to test it (shareware data). I also got permission from Mike to release his modified 8086 sources too, if you want that.

BTW, Japheth, it crashes / hangs when you quit the game! (that can't be intentional)

> > taken by HX itself (menu key), converted to .GIFs from (large,
> 500K !!) .BMPs by
>
> There is nothing wrong about a 640x480x24bpp BMP hogging only 921'654
> Byte's

These were 640x400x256 I think. Hence kinda overkill in size. I don't care, honestly, but surely it's less ideal for someone downloading them on dialup! (BTW, do modern browsers even support .BMP? [too lazy to check])

> > http://www.lootube.com/watch?v=5f7gW5X24ao
> > http://www.lootube.com/watch?v=QGQkszIEMiw
>
> Does it play for you in Open Source Arachne ??? You whine about "closed
> source" and "compatibility", but promote such stuff even more

Sorry, but that's never my intent, it's just what's out there in use! I can't control the world. My laptop doesn't work well with open source, e.g. Ubuntu 9.10 still loads slow from USB, Broadcom doesn't work and their driver seems to crash the OS (good luck finding working packet drivers and explaining to me how to use them!), sound mostly works (except no longer under DOSEMU?? bah, regression), suspend (which I never try since I never expect it to work) also hangs the machine. Hooray for me. I don't know, maybe we expect too much from hardware people, or maybe I should shop more open source consciously. I mean, damn, hardware compatibility is annoying!

> honestly, but surely it's less ideal for someone downloading them on dialup!

NO. Use PNGOUT, OPTIPNG, DEFLOPT

> (BTW, do modern browsers even support .BMP? [too lazy to check])

YES, but irrelevant, see above

> Sorry, but that's never my intent, it's just what's out there in use!
> I can't control the world.

No, but you can convert the movies yourself before boasting with them.

> My laptop doesn't work well with open source

Does DOS work ?

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

> > honestly, but surely it's less ideal for someone downloading them on
> dialup!
>
> NO. Use PNGOUT, OPTIPNG, DEFLOPT
>
> > (BTW, do modern browsers even support .BMP? [too lazy to check])
>
> YES, but irrelevant, see above

.GIF is "good enough" here (not bloated, widely supported, not patented anymore). No good reason to use .PNG here (only 256 colors).

> > Sorry, but that's never my intent, it's just what's out there in use!
> > I can't control the world.
>
> No, but you can convert the movies yourself before boasting with them.

I wouldn't even know how to convert those movies. I just thought the parody of the parody (he's an actor, BTW) was ultra funny. I think we've all played games that kill us even when we "win", heh. His reactions / screams are priceless!

The video of 8086 Wolfenstein was because I didn't have explicit permission to distribute the sources (yet, though now I do), and I still don't have them on my webpage. Of course, that's of questionable value anyways since probably nobody wants it, my site's now mostly dumped on Google Sites (somewhat annoying interface), but I definitely do wish to preserve his efforts!

> > My laptop doesn't work well with open source
>
> Does DOS work ?

No sound, no mouse, not even sure UIDE or LBACACHE works here, but otherwise sure. In contrast, my P4 has much much less trouble, almost everything works smoothly there. Hardware is annoying.

> > > I can't control the world.
> >
> > No, but you can convert the movies yourself before boasting with them.
>
> I wouldn't even know how to convert those movies. I just thought the
> parody of the parody (he's an actor, BTW) was ultra funny. I think we've
> all played games that kill us even when we "win", heh. His reactions /
> screams are priceless!

The DJGPP compile of APEGPLAY seems to accept the "Angry Kid" video (although it's like 39 MB download, heh).

> The video of 8086 Wolfenstein was because I didn't have explicit
> permission to distribute the sources (yet, though now I do),

"Your file has been saved and can now be downloaded 10 times. It will be deleted after 90 days without download."

http://rapidshare.com/files/319786791/wolfsrc-8086hack.zip.html
MD5: CE56A0FC558876E612DAEC8FF754087A

EDIT: Mike says it's "GPL just as the original" (although personally I thought the original said non-commercial only ... ah well, who cares, as if, right?)

> > The video of 8086 Wolfenstein was because I didn't have explicit
> > permission to distribute the sources (yet, though now I do),
Thank you this is very much appreciated. Indeed I can think of at least 3 people who will be interested in this. 2 of whom are now on this board :)

> http://rapidshare.com/files/319786791/wolfsrc-8086hack.zip.html
> MD5: CE56A0FC558876E612DAEC8FF754087A
"...This file can only be downloaded by becoming a Premium member..."

Doh ! Ok, I am not that keen to download it right now. So if someone posts it somewhere else let me know, many thanks.

> .GIF is "good enough"

NO

> here (not bloated

bad compression

> widely supported

... inertia of some people ...

> not patented anymore

indeed, but not very relevant (same a HFFS / LPFS / HPFS)

> No good reason to use .PNG here

Compression is not a good reason ?

> (only 256 colors).

I want the same format for >256 colors and for <=256 colors.

> I wouldn't even know how to convert those movies.

See 2 links above.

> > Does DOS work ?
> No sound

HDA ?

> no mouse

PS/2 or USB ?

> not even sure UIDE or LBACACHE works here

LBACACHE doesn't talk to any hardware. Did you test UIDE / XDMA / XDMA32 or not ?
Is the BIOS slow at all ?

> The DJGPP compile of APEGPLAY seems to accept the "Angry Kid" video

from where ???

> http://rapidshare.com/files/319786791/wolfsrc-8086hack.zip.html
> MD5: CE56A0FC558876E612DAEC8FF754087A

Arachne can't download from RapidS*** either. Same for FireFox or Opera with VirusMagnet (R) (formerly known as JavaS*** (R) technology) OFF.

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

> > > Does DOS work ?
> > No sound
>
> HDA ?

Yes. BTW, never heard back from Atila re: Mpxplay, guess he never got my e-mail. If you know of a better way to contact him .... But it's not urgent.

> > no mouse
>
> PS/2 or USB ?

Touchpad, and I guess the BIOS may be buggy as I had issues with CuteMouse in the past.

> > not even sure UIDE or LBACACHE works here
>
> LBACACHE doesn't talk to any hardware. Did you test UIDE / XDMA / XDMA32
> or not ?
> Is the BIOS slow at all ?

It just had some issues, and I didn't investigate further.

> > The DJGPP compile of APEGPLAY seems to accept the "Angry Kid" video
>
> from where ???

The one from a while back that Khusraw compiled. Search the forum archives.

> > http://rapidshare.com/files/319786791/wolfsrc-8086hack.zip.html
> > MD5: CE56A0FC558876E612DAEC8FF754087A
>
> Arachne can't download from RapidS*** either. Same for FireFox or Opera
> with VirusMagnet (R) (formerly known as JavaS*** (R) technology) OFF.
>
> "...This file can only be downloaded by becoming a Premium member..."
>
> Doh ! Ok, I am not that keen to download it right now. So if
> someone posts it somewhere else let me know, many thanks.

Sorry, I just uploaded to Rapidshare for quickness. It does not require "premium access" (which I also don't have), just click "Free User". But whatever, I've put it on my Google Site now. (However, the disk image + srcs for the Wolf4SDL won't fit on my site as I'm very low on space. Argh.)

http://rugxulo.googlepages.com/wolf8086.zip

P.S. This is the exact same archive as Mike gave me (except I added the separate "wolf8086.exe" to it, which you obviously would want). It has some cruft (WOLF.EXE -> Borland 16-bit DPMI .EXE that I can't seem to get to work at all, even with HDPMI16, originally from WOLFSRC.ZIP; also, WOLF3D.SYM takes up a ton of space and is probably useless). So it's an 882k .ZIP (not too big but anyways). Enjoy!

EDIT: Just to be clear, for whatever sad reason, the source has to be recompiled for each Wolf3d edition you want to use it with: shareware, Apogee full, Activision full, Spear of Destiny demo, Spear of Destiny full. (I think his .EXE is Activision full.) Sorry (and this is true for all Wolf3d ports, not Mike's fault)!!

> Sorry, I just uploaded to Rapidshare for quickness. It does not require
> "premium access" (which I also don't have), just click "Free User".
Did try that but didn't seem to work... oh well thank you for moving it :)

> http://rugxulo.googlepages.com/wolf8086.zip
3rd time lucky after discovering the above link is to an html page first....

> separate "wolf8086.exe" to it, which you obviously would want).
Cheers less hassle with compilers etc.

> all Wolf3d ports, not Mike's fault)!!
Thanks Mike / Rugxulo appreciate this interesting build upon John et al's work.

> (However, the disk image + srcs for the Wolf4SDL won't fit on
> my site as I'm very low on space. Argh.)

Finished, at least. Maybe I should've used a shareware mod (Barneystein ??) instead of stock 1.4 shareware so it would be more "universal" and not illegal for certain people. But anyways, I'll look into that later. Yes, I know, this is fairly useless and nobody cares, I just wanted an easy way to test it on several machines.

Here's the disk's contents (1.44 MB, of course). It doesn't even use FINDDISK and instead defaults to G:\ RAM drive, but I included it just in case someone needed it (plus it's small!).


Extract NT - Extract file in wImage - V 2.10 (c) 1991-96 Gilles Vollant
Visit web page : http://www.winimage.com/othertl.htm

image file : WOLF4SDL.IMG  no label
KERNEL.SYS                  45161  08.01.109  04:18p
COMMAND.COM                 66932  08.29.106  01:38a
XMGR.SYS                     4006  11.27.109  09:00a
CONFIG.SYS                    299  12.11.109  09:16p
AUTOEXEC.BAT                 1305  12.12.109  12:07p
MSVCRT.TXT                    405  12.12.109  12:56p
CTMOUSE.EXE                  5089  12.03.107  05:08a
RDISK.COM                    1536  11.27.109  09:00a
WOLF4SDL.P8F              1107549  12.11.109  09:11p
PAQ8F.EXE                   76804  12.11.109  10:00p
FINDDISK.COM                  512  09.25.109  08:19a
SBMIX.EXE                    4234  02.09.105  00:00a
1313832 bytes in 12 files, 141312 bytes free


And sources (10 MB):


Archive:  wolf4sdl.zip
Zip file size: 9511406 bytes, number of entries: 15
-rw-a--     2.0 fat  1749790 b- defN 08-Apr-03 16:50 com084_s.tbz
-rw-a--     2.0 fat   186874 b- defN 08-Jul-13 22:56 ctm21b4s.zip
-rw-a--     2.0 fat    59964 b- defN 04-Oct-24 22:54 d3x-090h.zip
-rw-a--     2.0 fat     6654 b- defN 05-Mar-23 16:41 finddisk.asm
-rw-a--     2.0 fat  1158258 b- defN 09-Nov-16 09:21 HXDEV216.zip
-rw-a--     2.0 fat  1166435 b- defN 09-Nov-16 09:37 HXSRC216.zip
-rw-a--     2.0 fat   115772 b- defN 09-Nov-27 09:00 jack_drv.zip
-rw-a--     2.0 fat   486350 b- defN 09-Aug-01 15:17 krn2039s.zip
-rw-a--     2.0 fat    42085 b- defN 09-Dec-12 13:09 paq8f.zip
-rw-a--     2.0 fat     7080 b- defN 05-Feb-09 00:00 sbmixs.zip
-rw-a--     2.0 fat  3582574 b- defN 09-Dec-12 13:03 sdl1214s.tbz
-rw-a--     2.0 fat   774853 b- defN 09-Dec-12 13:04 sdlmingw.tbz
-rw-a--     2.0 fat   281009 b- defN 08-Sep-01 14:10 w4sdl16s.zip
-rwxa--     2.0 fat      986 b- defN 09-Dec-10 00:24 wolf4gw.bat
-rw-a--     2.0 fat     5515 b- defN 09-Dec-12 14:56 wolf4sdl.txt
15 files, 9624199 bytes uncompressed, 9509896 bytes compressed:  1.2%


EDIT: Where is a good place to upload (not Rapidshare if you guys don't use JavaScript)???

> Here's the disk's contents (1.44 MB, of course). It doesn't even use
> FINDDISK and instead defaults to G:\ RAM drive, but I included it just in
> case someone needed it (plus it's small!).

You might just load RDISK in AUTOEXEC.BAT and provide it a drive letter to use; or is this what you meant by "defaults to G:" ?

> You might just load RDISK in AUTOEXEC.BAT and provide it a drive letter to
> use; or is this what you meant by "defaults to G:" ?

Yes, that's what I'm doing. Of course, that also assumes G: isn't taken. Hardcoding things is ugly, but since I was controlling the environment (my own hand-tailored CONFIG.SYS), it didn't matter. Still, I kept FINDDISK in mind.

In particular, if anybody knows of any "good" mods they would prefer, I would appreciate hearing feedback, so I can test it and maybe use it instead. (And I can upload to RapidShare if some people want, just it's obviously not ideal.)

> Yes, that's what I'm doing. Of course, that also assumes G: isn't taken.
> Hardcoding things is ugly, but since I was controlling the environment (my
> own hand-tailored CONFIG.SYS), it didn't matter.

Why not set LASTDRIVE=Z and use drive Z: ? That might fail as well since the letter Z: might actually be taken by FAT drives but then just blame the user.

> > Yes, that's what I'm doing. Of course, that also assumes G: isn't taken.
> > Hardcoding things is ugly, but since I was controlling the environment
> (my
> > own hand-tailored CONFIG.SYS), it didn't matter.
>
> Why not set LASTDRIVE=Z and use drive Z: ? That might fail as well since
> the letter Z: might actually be taken by FAT drives but then just blame
> the user.

Of course I could do that, but it wastes a little bit of RAM for each drive allocated, and 99% of people (or 100% ??) never use that many drives and would rather have more free memory. IIRC, I'm using "LASTDRIVE=P" (should be enough for anyone, heh).

P.S. I've had four Wolfenstein 3D shareware mods unpacked on this P4 since March 2008! (I don't use this computer much anymore, instead use my laptop.) I always meant to tell people here about 'em, but I never got around to it. I just played them a bit to see if they had any "illegal" graphics, and only the Pac & Clowns one did (barely). Others (Barneystein, Hallowein [sic], Xmas) seem to be 100% okay for German consumption.

P.S. There are actually several Barney mods, but the one I tested (by "PC-CRAP") has Beavis and Butthead as enemies, MTV logos, dead kermits on the floor, piglets in cages, etc. Barney is the guy on the wall, stain-glass, etc.

> > Sorry, I just uploaded to Rapidshare for quickness. It does not require
> > "premium access" (which I also don't have), just click "Free User".
> Did try that but didn't seem to work... oh well thank you for moving it
> :)

I tried it too (earlier) after you reported the problem. Either it was busy or it "ran out" of slots (only 10, which seems low, but anyways ...).

> > http://rugxulo.googlepages.com/wolf8086.zip
> 3rd time lucky after discovering the above link is to an html page
> first....

I just now tried to use WGET from this P4, and it didn't work. But things like that used to work all the time until the "auto-migrated" everything from Google Pages to Google Sites (approx. three weeks ago). So it's their issue, and something I'm not normally aware of.

EDIT: Tried fiddling, can't succeed, they must be purposely blocking such things (so no "leeching"? meh). Anyways, I just added yet another update on my (long / badly organized) main page (Sep. 15 -> Wolfenstein 3D/8086), hopefully that is more obvious than just a random mention on this forum. (At least clicking on that link seems to work!)

> > separate "wolf8086.exe" to it, which you obviously would want).
> Cheers less hassle with compilers etc.

The other day (for fun) I halfway tried to see how hard it would be to build with Turbo C++ 1.01 and ArrowASM 2.00d, but I got somewhat frustrated and gave up. Ideally, it would compile with TC++ (closed source but 8086 friendly) or OpenWatcom 16-bit (386 host only but open source) too, but neither's possible just yet.

> > all Wolf3d ports, not Mike's fault)!!
> Thanks Mike / Rugxulo appreciate this interesting build upon John et al's
> work.

Mike did all the work, I'm just collecting it and posting it publicly (among other notes and random stuff) since I like the game (and Doom, Quake, etc).

P.S. Chrome doesn't seem to handle HTML5 video (unlike FireFox which works).

> Yes. BTW, never heard back from Atila re: Mpxplay, guess he never got my
> e-mail. If you know of a better way to contact him .... But it's not urgent.

See SF project page

> Touchpad, and I guess the BIOS may be buggy as I had issues with CuteMouse

Still, it probably acts like PS/2 or USB device ...

> It just had some issues, and I didn't investigate further.

The 0th thing to test if BIOS is slow or buggy at all, if NOT, no driver is needed

> > > The DJGPP compile of APEGPLAY seems to accept the "Angry Kid" video
> > from where ???
> The one from a while back that Khusraw compiled. Search the forum

No. Where did you get the video ? BTW, this APEGPLAY should get updated, it uses IIRC inefficient and buggy LibTheora 1.0b2.

> P.S. Chrome doesn't seem to handle HTML5 video (unlike FireFox which works).

1. Find "Chrome" icon
2. Find "Recycle Bin" icon
3. Drug&Drop "Chrome" icon into "Recycle Bin" icon
4. Confirm "YES" to any question asking whether you want to fully remove the "Chrome"

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Heh, you're lucky I'm really bored and up late tonight.

> > Yes. BTW, never heard back from Atila re: Mpxplay, guess he never got my
>
> > e-mail. If you know of a better way to contact him .... But it's not
> urgent.
>
> See SF project page

Hmmm, okay, I never could figure out his myriad of websites.

> > Touchpad, and I guess the BIOS may be buggy as I had issues with
> CuteMouse
>
> Still, it probably acts like PS/2 or USB device ...

It does act like PS/2, but IIRC it just hangs / crashes or similar. I'd have to try again (ugh).

> > > > The DJGPP compile of APEGPLAY seems to accept the "Angry Kid" video
> > > from where ???
> > The one from a while back that Khusraw compiled. Search the forum
>
> No. Where did you get the video ? BTW, this APEGPLAY should get updated,
> it uses IIRC inefficient and buggy LibTheora 1.0b2.

E.g., it says "Download this video" and points to this file (39 MB!!!):
http://tinyvid.tv/file/2g0zu7wft1qb1.ogg

P.S.
APEG thread #1
APEG thread #2

> > P.S. Chrome doesn't seem to handle HTML5 video (unlike FireFox which
> works).
>
> 1. Find "Chrome" icon
> 2. Find "Recycle Bin" icon
> 3. Drug&Drop "Chrome" icon into "Recycle Bin" icon
> 4. Confirm "YES" to any question asking whether you want to fully remove
> the "Chrome"

Well, I tried Chrome again later, and it seemed to work. And yet now Firefox is having issues. Meh. (Yes, I know, you ardently hate Windows, blah blah.)

> I just now tried to use WGET from this P4, and it didn't work. But things
> like that used to work all the time until the "auto-migrated" everything
> from Google Pages to Google Sites (approx. three weeks ago).
> So it's their issue, and something I'm not normally aware of.

Well having quickly looked at this. I can see that Google aren't actively blocking WGET via either Googlesites or Googlepages robots.txt's files. However.... what they have clearly done recently is migrate Google Sites to their new method of content load balancing, which basically involves their custom Linux servers sending browsers lots of HTTP 302's redirects to session based content thus the traditional simple usage of WGET et al can get easily broken for several reasons such as needing to follow the URL's which are unique to that session. With WGET you can see this easily if you remember to use the -v (lowercase v) to ensure you see verbose output.

In addition for added fun, another reason for WGET getting broken is if you are using WGET under a modern Windows box... if you are then be aware of the important nasty watch out with later versions of Windows which is the need to escape certain characters such as & with a ^, e.g. ^& in the command-line instead of just &.

& is a particular pain under modern Windows shells as it is used to separate command-lines, however as you may know already it is also exactly the same character used to separate parameters on web URL's... doh! Thus what this means is if you need to directly feed a URL to a program like WGET containing for example, a & character then the & character (and others) MUST be escaped first otherwise those characters will get interpreted by the Windows shell... in the case of & in particular that gets interpreted as telling Windows (every time it sees it) that you would like to run another totally separate command-line, so not only is it "removed" from the original command-line, but the command-line is truncated at that point before the rest of the command-line text is then interpreted as another command-line until it reaches another & where upon... and so it goes on until you either run out of &'s or text for command-line(s!)... and guess what? Google's use a lot of &'s for URL parameters in their newer URL's.... enjoy!

> The other day (for fun) I halfway tried to see how hard it would be to
> build with Turbo C++ 1.01 and ArrowASM 2.00d, but I got somewhat
> frustrated and gave up. Ideally, it would compile with TC++ (closed source
> but 8086 friendly) or OpenWatcom 16-bit (386 host only but open source)
> too, but neither's possible just yet.
Perhaps Fabrice Bellard's TCC?

> Mike did all the work, I'm just collecting it and posting it publicly
Yeah I realize but that in itself is a lot of work. More than most realize.

> (among other notes and random stuff) since I like the game (and Doom,
> Quake, etc).
Likewise. I still like Wolf though as it was there first ;)

> Both SDL.DLL and SDL_MIXER.DLL (which I renamed / hacked to SDL_MIX.DLL,
> not sure if totally necessary) are inside the WOLF4SDL archive.

Just use any kind of DOS LFN tsr utils before loading HX in cases when desired program need some files with LFN.

> However, you must "set SDL_AUDIODRIVER=dummy" since both "dsound"
> (default) and "waveout" don't work (or at least only work on SB-compatibles,
> e.g. not on my P4's EMU10k1) and hence won't let the game even start.

Wrong. SBlive!/Audigy in SB emulation works in HX just flawlessly, even better than native AWE64 Gold! I use HX+DOSBox in pure DOS often and prefer SBLive!'s SB emulation in comparison with real ISA SB soundcard. Tested HX + SBLive! + Wolf4SDL - both digital & fm sources works just great in game.

> Wrong. SBlive!/Audigy in SB emulation works in HX just flawlessly, even
> better than native AWE64 Gold! I use HX+DOSBox in pure DOS often and
> prefer SBLive!'s SB emulation in comparison with real ISA SB soundcard

Unfortunately SBlive emulation driver does't work on newer mobos/chipsets se be happy it works for you but pre prepared you will loose it when upgrade...

---
DOS gives me freedom to unlimited HW access.

> > Both SDL.DLL and SDL_MIXER.DLL (which I renamed / hacked to SDL_MIX.DLL,
> > not sure if totally necessary) are inside the WOLF4SDL archive.
>
> Just use any kind of DOS LFN tsr utils before loading HX in cases when
> desired program need some files with LFN.

I haven't tested, but I'm not sure even that is necessary. Seems normal DOS API truncates to SFNs anyways when trying to open files, so it should probably work anyways even without DOSLFN. (e.g. DJGPP Make will accept "gnumakef" in lieu of "GNUmakefile"). However, DOSBox itself doesn't truncate correctly (although it's way too slow to be usable here, so it's moot), hence why I originally modified it.

> > However, you must "set SDL_AUDIODRIVER=dummy" since both
> "dsound"
> > (default) and "waveout" don't work (or at least only work on
> SB-compatibles,
> > e.g. not on my P4's EMU10k1) and hence won't let the game even start.
>
> Wrong. SBlive!/Audigy in SB emulation works in HX just flawlessly, even
> better than native AWE64 Gold! I use HX+DOSBox in pure DOS often and
> prefer SBLive!'s SB emulation in comparison with real ISA SB soundcard.
> Tested HX + SBLive! + Wolf4SDL - both digital & fm sources works just
> great in game.

I only tested once on my old AWE64 machine, but I don't think I tested with sound enabled. The main problem (bug?) is that it won't even play the game if sound isn't available. Also, for some reason, it crashes upon exit, so if you type "wolf4sdl --help", you'll get a help screen but have to reboot (ugh). No comments from Japheth, so I dunno what to say. Luckily, most people have fast machines so it's only a two-minute reboot.

BTW, I really really need to test Wolf4GW native, and since that supports PC speaker and SB/Adlib, it's probably better for non-SB computers. (Bonus: UPX'd and using D3X, it's even smaller than MSVCRT paq8f'd, so I can easily fit it on the same floppy! And no proprietary crap needed! But the whole point of this HX exercise was just to test things, heh.)

P.S. DOS386, I tested my touchpad mouse yesterday (CuteMouse 2.1b4) on this laptop, works fine in Wolf4SDL (I guess ... can't really move forward, only rotate around, right button is strafe, left is shoot). I forget the details now, but a year or so ago there was some app that using a mouse (CuteMouse) was crashing for me in FreeDOS here. Also OctaOS didn't detect my mouse correctly, so that was annoying. It's most likely the BIOS' PS/2 emulation bug or whatever, but at least here it works fine.

> BTW, I really really need to test Wolf4GW native, and since that supports
> PC speaker and SB/Adlib, it's probably better for non-SB computers.
> (Bonus: UPX'd and using D3X, it's even smaller than MSVCRT paq8f'd, so I
> can easily fit it on the same floppy! And no proprietary crap needed! But
> the whole point of this HX exercise was just to test things, heh.)

Wolf4GW works fine, PC speaker works fine. The third-party WOLFSPK4.EXE tool is closed source, but luckily all it does (!) is change one byte in the CONFIG.WL1 file : offset 0x1D2 \0 -> \1. And that enables the undocumented PC speaker / WAV combo, which is better than plain PC speaker (enemy voice sound effects!) but pretty damn loud, esp. doors opening/closing (esp. on my laptop where PC speaker is emulated via normal speakers, ignoring headphones too). Actually, DOSBox isn't nearly as loud. Anyways, my guess is that either the loudness or some performance slowdown is why they didn't support this option officially in the config screen.

> P.S. DOS386, I tested my touchpad mouse yesterday (CuteMouse 2.1b4) on
> this laptop, works fine in Wolf4SDL (I guess ... can't really move
> forward, only rotate around, right button is strafe, left is shoot). I
> forget the details now, but a year or so ago there was some app that using
> a mouse (CuteMouse) was crashing for me in FreeDOS here. Also OctaOS didn't
> detect my mouse correctly, so that was annoying. It's most likely the BIOS'
> PS/2 emulation bug or whatever, but at least here it works fine.

Mouse does move forward/backwards in DOSBox, so it's something on my end. BTW, Wolf4GW (using D3X) just hangs if I enable CuteMouse in pure FreeDOS. I should try with a few other extenders to see if D3X is the cause or not. But I also heavily suspect my buggy BIOS (argh).

RayeR wrote:
> Unfortunately SBlive emulation driver does't work on newer mobos/chipsets
> se be happy it works for you but pre prepared you will loose it when
> upgrade...

Rugxulo have noted about their P4...
> (or at least only work on SB-compatibles, e.g. not on my P4's EMU10k1)
But does not have noted exactly their chipset. At least on intel 8xx series SBLive! emulation works just fine.


image file : WOLFXMAS.IMG  no label
KERNEL.SYS                  45161  08.01.109  04:18p
COMMAND.COM                 66932  08.29.106  01:38a
XMGR.SYS                     4006  11.27.109  09:00a
CONFIG.SYS                    299  12.11.109  09:16p
AUTOEXEC.BAT                 1740  12.14.109  04:33p
MSVCRT.TXT                    590  12.14.109  07:35a
CTMOUSE.EXE                  5089  12.03.107  05:08a
RDISK.COM                    1536  11.27.109  09:00a
FINDDISK.COM                  512  09.25.109  08:19a
SBMIX.EXE                    4234  02.09.105  00:00a
7ZDEC.EXE                   46884  09.22.109  00:39a
HXGUI.P8F                   25338  12.14.109  07:22a
HXRT.7Z                    116035  12.14.109  07:40a
PAQ8F.EXE                   56320  12.14.109  07:24a
WOLF4SDL.P8F               533465  12.14.109  07:10a
WOLFXMAS.P8F               406327  12.14.109  07:31a
WOLF4GW.EXE                111783  12.13.109  05:31p
1426251 bytes in 17 files, 28160 bytes free


Basically, I split up the .p8f files (for faster unpacking, e.g. only 19 mins. now for unpacking Wolf4GW on my P166, heh), esp. if MSVCRT.DLL isn't found, hence it defaults to Wolf4GW (but delete that .EXE and put MSVCRT.P8F and it will automatically use Wolf4SDL instead). Also, for optimum compatibility (Win32 / Win64), I made paq8f a Win32 PE .EXE and just use DOS 7zdec (on DOS only) to unpack HXRT to use it later. (DJGPP-compiled paq8f won't work on Win64.) Also, for safety, sound is disabled on Wolf4SDL, but if you're sure it will work for you, feel free to change SDL_AUDIODRIVER before trying it else try CONFIG.PC2 (loud!!).

P.S. Now German friendly! No illegal images! Merry Christmas!

Now, does anybody actually want it??? (Doubtful.)

EDIT: Well, it's only 10 downloads allowed, but heck, I don't know of a better place! :-/

Your file has been saved and can now be downloaded 10 times. It will be deleted after 90 days without download.

1. Download Link: Click here to download file
http://rapidshare.com/files/320960585/wolfxmas.zip.html
MD5: A7DCEEE3715F77EC0007D20F6B82E49F

2. Download Link:
http://rapidshare.com/files/320963756/wolfxsrc.zip.html
MD5: FC65350193C117D7E88E22598286310F

The source archive (10 MB) is a bunch of .ZIP and .tar.bz2 files, so I assume DJGPP 2.04's DJTAR would be the best for people on SFNs (or LFNs, even) as it lets you rename if necessary.

> Rugxulo have noted about their P4...
> > (or at least only work on SB-compatibles, e.g. not on my P4's EMU10k1)
> But does not have noted exactly their chipset. At least on intel 8xx
> series SBLive! emulation works just fine.

Yes, old 8xx is OK (in my case it worked last on BX440) but I didn't saw any PC with 9xx anf Pxx/Gxx that would work. I don't know about how in AMD/nForce world but I doubt it works on recent (say 3 years) mobos. So take it in mind. We would need some new AC97 SB emulator but it's a very hard job...

---
DOS gives me freedom to unlimited HW access.

> > Both SDL.DLL and SDL_MIXER.DLL (which I renamed / hacked to

> Just use any kind of DOS LFN tsr utils before loading HX in cases when
> desired program need some files with LFN.

Very worst choice. Other options:

1. Just truncate
2. Rename and adjust some INI files (works for BOCHS)
3. Use UI21DEB (works for GIFSICLE, WGET, OPTIPNG PNG>PNG and 7-ZIP archive updating)

> BTW, Wolf4GW (using D3X) just hangs if I enable CuteMouse in pure FreeDOS.
> I should try with a few other extenders

DOS/32A

> to see if D3X is the cause or not. But I also heavily suspect my buggy BIOS (argh).

D3X has BUG's, and DPMI "mouse callbacks" are an inherently faulty and dangerous design anyway. So testing mouse support should start with FreeDOS EDIT (oops also buggy), or DN (real mode), not 4GW nor HXSDL.

D3X is great, but one has to be aware of its bugs (ARF, ...).

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

> > > Both SDL.DLL and SDL_MIXER.DLL (which I renamed / hacked to
>
> > Just use any kind of DOS LFN tsr utils before loading HX in cases when
> > desired program need some files with LFN.
>
> Very worst choice. Other options:
>
> 1. Just truncate
> 2. Rename and adjust some INI files (works for BOCHS)
> 3. Use
> UI21DEB
> (works for GIFSICLE, WGET, OPTIPNG PNG>PNG and 7-ZIP archive updating)

Also DOSLFN would waste more space than I have (or was willing to allow). And it's really not needed here and would be overkill (one lonely file).

> > BTW, Wolf4GW (using D3X) just hangs if I enable CuteMouse in pure
> FreeDOS.
> > I should try with a few other extenders
>
> DOS/32A

I think I'll try WDOSX first. If that doesn't work, I'll try DOS/32A. But I'm not getting my hopes up.

> > to see if D3X is the cause or not. But I also heavily suspect my buggy
> BIOS (argh).
>
> D3X has BUG's, and DPMI "mouse callbacks" are an inherently faulty and
> dangerous design anyway. So testing mouse support should start with
> FreeDOS EDIT (oops also buggy), or DN (real mode), not 4GW nor HXSDL.
>
> D3X is great, but one has to be aware of its bugs (ARF, ...).

Well, you don't really even need the mouse, and personally I'm not a fan of it anyways (esp. not for games).

D3X is mostly good because it's easy to rebuild and supports both DJGPP and OpenWatcom. Too bad it's not "free" enough for DJ himself to mirror.

> > > BTW, Wolf4GW (using D3X) just hangs if I enable CuteMouse in pure
> > FreeDOS.
> > > I should try with a few other extenders
> >
> > DOS/32A
>
> I think I'll try WDOSX first. If that doesn't work, I'll try DOS/32A. But
> I'm not getting my hopes up.

Nope, neither worked on this laptop. So it must be the BIOS, I assume. However, I did play for a bit on the P4's real (optical) mouse, and it worked well (left = shoot, right = strafe, middle = open). The only annoyance is constantly picking up the mouse to move forward. It's a very funny mod (ahem, replacement for knife == hilarious when you run out of ammo!)

BTW, I didn't yet have a suitable conversion of my FASTPAQ2.s to NASM (OBJ-friendly) for OpenWatcom (since I usually prefer GCC), so my paq8f compile on the Wolfxmas disk is NOASM only (no MMX or SSE2 enabled). Not a huge deal, esp. since all my machines either don't support such or are already "fast enough." Still, if I were to more publicly announce this disk, I would replace it (already fixed/recompiled paq8f locally). Also, -oxs vs. -ox seems only very very slightly slower and 2k smaller. (I also kept relocs for ultimate compatibility.) Just FYI.

> D3X is mostly good because it's easy to rebuild and supports both DJGPP
> and OpenWatcom. Too bad it's not "free" enough for DJ himself to mirror.

The obsession by "standards" ... in this case CWSDPMI - neither needed nor able to run inside NTVDM, heh

> It does act like PS/2, but IIRC it just hangs / crashes or similar. I'd have to try
> Nope, neither worked on this laptop. So it must be the BIOS, I assume

CTMOUSE 2.04 shouldn't use the BIOS, so BIOS should have no chance to break anything, if this "mouse" is PS/2 at all

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

> > It does act like PS/2, but IIRC it just hangs / crashes or similar. I'd
> have to try
> > Nope, neither worked on this laptop. So it must be the BIOS, I assume
>
>
> CTMOUSE 2.04 shouldn't use the BIOS, so BIOS should have no chance to
> break anything, if this "mouse" is PS/2 at all

Must not be. "Invalid opcode" or "Error: no device found" is all 2.0a4 says. Hence I'd have to buy a USB mouse (assuming even that would work!), but I don't require it for my DOS uses, so I won't.

> > > > Both SDL.DLL and SDL_MIXER.DLL (which I renamed / hacked to
> >

Ack, I think I may have omitted some crucial sources form my WOLFXSRC.ZIP file. (Silly me for thinking SDL contained SDL mixer).

http://www.libsdl.org/projects/SDL_mixer/
http://www.libsdl.org/projects/SDL_mixer/release/SDL_mixer-1.2.11.tar.gz
http://www.libsdl.org/projects/SDL_mixer/release/SDL_mixer-devel-1.2.11-VC.zip

> BTW, Wolf4GW (using D3X) just hangs if I enable CuteMouse in pure
> FreeDOS.
>
> I think I'll try WDOSX first. If that doesn't work, I'll try DOS/32A. But
> I'm not getting my hopes up.

Seems VirtualBox (or maybe only when using fast hardware virtualization extensions??) doesn't like D3X, but WDOSX works okay (although it's a little less than smooth, slight framerate drop, presumably because 16-bit support isn't fully fleshed out in VirtualBox). Wolf4SDL works much smoother, but it frequently seems to get keys stuck (e.g. you start turning around in a circle over and over ...) which can be manually corrected with movement but is still annoying. BTW, as Japheth has previously mentioned, no SB sound in VirtualBox.

Long story short: DOSBox + Wolf4GW is probably best (lacking real hardware, of course, yes DOS386 I know I know ...).