VIPER and 3DS RELEASE 3
23-Dec-93 22:23:39
Sb: #73165-VIPER and 3DS RELEASE 3
Fm: Gus Grubba 70673,1605
To: Ernest Morgenshtern 71052,1721
I had the exact same problem as you describe when using 3D Studio release 2 and
Stacker 3.0. Stacker had corrupted a bunch of files in my hard disk including
3DS.EXE. When I reinstalled from the floppies, the new 3DS.EXE would just
replace the old one but Stacker would corrupt it again, and again, and again. I
could not figure what the heck was going on. I was only able to figure this out
when I installed 3DS in a non compressed partition. When I compared both files,
a single byte was different. I traced the "write" function to find out who was
changing this byte and found a bad instruction in the Stacker code. This byte
happen to be on a (disk) sector boundary and stacker was getting messed up when
transferring from its internal buffers. I know this bug was fixed in Stacker
3.1. I gave up on stacker and bought a 1.2 gig drive. Cheaper when you consider
the headache…