Article View: comp.os.ms-windows.setup
Article #1166SuperStor 2.0 Installation experiences
From: SASTPH
Date: Fri, 22 Jan 1993 13:31
Date: Fri, 22 Jan 1993 13:31
42 lines
2520 bytes
2520 bytes
After getting a lot of very good advice from this newgroup, I set about installing SuperStor 2.0 on my Gateway 2000 386DX with an 80Mb IDE hard drive. I'm running MS-DOS 5.0, 386MAX, and Windows 3.1. (Incidently, this post contains NO Windows-specific questions, but this newsgroup is only one on which I can find SuperStor users.) The installation did not go well. When SSTOR finished PREPARING my hard disk and I re-booted, DOS told me it couldn't find COMMAND.COM. I had to get out my DOS 5.0 installation disks and copy EXPAND.EXE to my C: drive, and then use EXPAND.EXE to get EDLIN off the installation disks. Then I used EDLIN to change the SHELL statement in my CONFIG.SYS to point to a copy of COMMAND.COM on the uncompressed drive. I could then boot (almost) normally. It was then I discovered that for some reason there were NO files in my C:\DOS directory (C: being the compressed drive). Evidently SuperStor forgot to copy them when it compressed everything. Since I installed DOS 5.0 using the "vanilla" installation procedures, I'm at a lost to understand why SuperStor would have trouble with this. Anyway, I restored my C:\DOS directory from the backup I made prior to installing SuperStor and continued. Next I thought I'd re-run 386MAX's MAXIMIZE to get the SuperStor driver loaded high. Of course, 386MAX.SYS has to be loaded before SSTORDRV.SYS, so 386MAX.SYS (and many other 386MAX files) have to reside on the uncompressed portion of my disk. However, this portion is presented as the D: drive to MAXIMIZE, and I haven't been able to convince MAXIMIZE that it shouldn't use C: in filenames. I guess I'll be talking to the 386MAX people today. So, I edited my CONFIG.SYS to change the C:'s that MAXIMIZE put in to D:'s and re-booted. Imagine my surprise when 386MAX.SYS started reporting that it couldn't find any of the things it was supposed to load! Further, imagine my anguish when my AUTOEXEC.BAT finished and DOS gave me the message "File Allocation Table Bad". Now, any attempt to run a program just causes my machine to hang. Any advice? Thanks for listening, and thanks in advance for any help you can give.
Technical Details
Message-ID:
<93022.083118SASTPH@vm.sas.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!gatech!concert!sas!mozart.unx.sas.com!vm.sas.com!sastphShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!gatech!concert!sas!mozart.unx.sas.com!vm.sas.com!sastph Organization: SAS Institute Inc. Date: Fri, 22 Jan 1993 08:31:18 EST From: <SASTPH@vm.sas.com> Message-ID: <93022.083118SASTPH@vm.sas.com> Newsgroups: comp.os.ms-windows.setup Subject: SuperStor 2.0 Installation experiences Lines: 42