Privateer vs. Stacker?

Post problems with getting games installed and running properly here.
Post Reply
guesticleez

Privateer vs. Stacker?

Post by guesticleez »

I'm hoping there's someone here who still remembers the "old ways"... Unlike most of y'all, I've managed to hang onto the old iron dinosaur of a 386 that I ran Privateer on nearly a decade ago. Original SB16 ISA, 4x CD-ROM drive, and 4 whole megs of RAM. Smokin'.

The problem is, she's running Stacker - remember, that utility that nearly doubled your hard disk space in return for some fall-of of performance. If memory serves me correctly, Privateer did not like Stacker much at all - but this was a long time ago, so i may be wrong. I don't remember X-Wing having serious problems with it, but apparently Privateer's JEMM pulls some really funky tricks, so it's all up in the air...

Anyway, most of the data on the 386 is stored within the Stacker file - it shows up as a "false partition" C drive, with the uncompressed stuff as the D drive - mostly just Stacker itself, and enough of DOS to get Stacker booted. So I can't just edit out the calls to Stacker in my boot files, otherwise the rest of my drivers won't load - because they're all hidden in the Stacker file, which requires Stacker running to access it.

I've thought of three solutions. First, I could try installing Privateer to the Stackered C: "partition", thereby placing it in the Stacker file, and run it like any other program I've got on there. (That includes Windows 3.1, if you'll believe it.) Second, I could copy my mouse, CD, and SB16 drivers to the uncompressed D: "partition", install Privateer to that same uncompressed partition, edit out the Stacker calls in my boot files, and turn my 386 into a dedicated Privateer box. Or third, I could try and cruft together a working boot disk, which I'm lazy so I don't want to do that if I can get away with it. :shame:

So, what's my best option here? I'd appreciate any help y'all can hand me on this...
Guest

Post by Guest »

Why not just nuke the partition and start again?

I used doublespace on my 386 SX 16 back in the day on my 80 meg HD and it was nothing but trouble.

I ended up having to wipe the drive clean and start again. there really isnt an easy way to fix up the mess that program makes.
Post Reply