Re: Wolf3D trouble...it's me...

[Rubywand <rubywand@swbell.net>]

Dave Althoff writes ...
> 
> I downloaded Wolf3d last night (Thanks, Sheppy!).  I also downloaded GUPP from
> Nathan's FTP site (thanks, Nathan!).  Additional thanks to Nathan for
> making that available via FTP since even though I've followed all the
> hints I could find for configuring Lynx2.7 it still insists on downloading
> BXY files as ASCII...
> 
> Anyway, that aside...I'm having problems.  It must be me, since everyone
> else is enjoying Wolf so much.  Here's what I did. ....
>

 
> a)  Downloaded, then unshrunk into my games directory, which happens to be
>     on an HFS partition.
> b)  Installed GUPP.
>     Note that I don't have Heirarchic, and therefore based on what I have
>     read, The Bug probably wouldn't bite me anyway.  Not a big deal, since
>     The Bug only bites on quit...and besides, I downloaded the patcher to
>     fix it.
> c)  Rebooted and tried to run Wolf3D.
> 
> I got the "updating desktop file" dialog and thermometer.  Then the screen
> shifted to 320 mode.  Then the screen went black.  Then...well...nothing
> ....


     First, read Neal Parker's Post about how he and a friend managed to
fry an entire box of memory IC's. After that, any problems you have
getting Wolf-3D running will seem trivial.

     Before you blame Wolf, you may want to check the size of your
WOLF3D10.SHK file. Mine shows up as 1,679,498 bytes on a ProDOS
partition. It seems to unShrink to the standard Wolf-3D correctly. The
size of the Wolfenstein3D file shows as 683,708. 

     If your file sizes match the above, and there has been no version
change, then it seems likely that you have the right stuff.

     If you have any screen savers installed or are loading an unusual
INIT, try getting them out of the way. Otherwise; a pure guess would be
a conflict with your Video Overlay Card and/or any special VOC driver.

     A last ditch fix is to patch Wolf-3D. The following patch is
_Experimental_. I've been using it without any problems but Eric says
that it introduces another bug. Basically, >>> WARNING <<< this patch
could eat your lunch:


>>

The experimental fix involves changing four bytes in the
Wolfenstein.3D file:

Since you need to scan Wolfenstein.3D in order to find the bytes and
since this file contains a resource fork, things are easier if you first
move Wolfenstein.3D to RAM disk (/RAM5) or to an empty diskette.

Using BlockWarden, ZAP, or some other block editing utility, search for
the (hexadecimal) bytes  A2 01 0A 22 00 00 E1. You should find them
somewhere in the first 15 or so blocks. I found them in Block $000F (15)
starting at offset location $0DC. Enter EDIT mode and change 22 00 00 E1
to 68 68 68 68 (i.e. A2 01 0A 22 00 00 E1  becomes  A2 01 0A 68 68 68
68).  Save the file. Rename the changed file to W3D, move it to your
Wolfenstein 3D folder and double-click to give it a try.


     What the patch does is eliminate the SetTSPtr CALL. The stack PULLs
(68's) are to remove PUSHed CALL parameters. Since this CALL seems to be
used mainly or entirely to display a message telling you that your
Desktop file is being updated when you first start the game, eliminating
it should not affect game play, except, of course, that Wolfenstein 3D
should no longer bomb upon exit. 

     Again, the patch is _experimental_. The original Wolfenstein 3D
file is left alone 'just in case'. If you discover a problem with the
patch, be sure to post an alert.

<<

     Whatever, good luck with getting Wolf-3D up and running.

Rubywand