acoolidg@wpi.WPI.EDU (Aaron P Coolidge) (03/27/91)
Help! I just got a WD7000 SCSI controler. Now, my win3 will not run
in 386 enhanced mode- it gets to the banner, and then i get the "C:\"
prompt back!
I had been running windows in 386enh for almost 6 months with my old
controler/drive, so I don't believe it's the machine.
I have put the following lines in the [386enh] section of SYSTEM.INI:
VirtualHDIRQ=false
emmexclude=ce00-cfff
And it still doesn't work. The card's bios is mapped to ce00-cfff, confirmed
in the manual and quarterdeck's manifest.
Does anyone have a WD7000 and is running win3 in 386enh? If so, what
did you have to do?
SYSTEM SPECS:
16MHz 386sx
4MB RAM
V7 1024i
Adlib
2 ser /1 par/ 1 game
running ms-dos 3.31 (NEC)
using himem.sys
loading only logitech's mouse driver as a TSR.
NOT USING THE WESTERN DIGITAL TSRS!!!!
The SCSI is fdisked & formatted with dos.
WD7000 BIOS rev. 3.34
Any help would be appreciated!!!!
--
Aaron Coolidge
acoolidg@wpi.wpi.edu bitnet:sorry, use a gateway.
"I'm always in control of my car. Well, at least 70% of the time." antonio@qualcom.qualcomm.com (Franklin Antonio) (04/04/91)
In article <1991Mar27.013413.5732@wpi.WPI.EDU> acoolidg@wpi.WPI.EDU (Aaron P Coolidge) writes: > Help! I just got a WD7000 SCSI controler. Now, my win3 will not run >in 386 enhanced mode- it gets to the banner, and then i get the "C:\" >prompt back! I run a WD7000 SCSI controller, and use Win in 386enh mode all the time. > > I have put the following lines in the [386enh] section of SYSTEM.INI: > >VirtualHDIRQ=false >emmexclude=ce00-cfff That's exactly what I did. I spelled it VirtualHDIrq tho, like the doc said. (I don't know whether these things are case sensitive tho.) I believe that you should not need the VirtualHDIrq=FALSE statement, because you don't load SSTBIO.SYS. Without SSTBIO, this controller emulates the standard AT controller. I should point out tho, that I have never run Windows without SSTBIO loaded. > 16MHz 386sx > 4MB RAM > V7 1024i Close. I'm a 386dx, 8MB ram, Paradise 1024. > > running ms-dos 3.31 (NEC) > using himem.sys > loading only logitech's mouse driver as a TSR. MSDOS 4.00 here, oh.. be real sure that you have the version of HIMEM.SYS that shipped with Windows, or a newer version. There's a claim in the windows manuals that you MUST run smartdrv if you have a SCSI controller. I have never run smartdrv, mostly because of the horror stories from folks who's disks have been eaten. I don't know exactly why the MUST run smartdrv statement is in the manual. They don't say WHY. I heard a rumor that i only get away with it because i don't have a permanent swap file. You didn't mention whether you run a permanent swap file. > > NOT USING THE WESTERN DIGITAL TSRS!!!! > The SCSI is fdisked & formatted with dos. You should consider using SSTBIO. It makes the disk run A LOT faster. > > WD7000 BIOS rev. 3.34 I am now running BIOS 3.36 and drivers 3.36. These versions implement virtual device services (VDS), so that the VirtualHDIrq=FALSE is no longer required. (in fact i've taken it out) They claim, although i haven't tried it, that with VDS, Windows can talk directly to the WD7000 bios, and get the speed advantages, etc, without using SSTBIO. I load SSTBIO and SSTDRIVE because i want the speed advantages under DOS as well as windows, and because i have 2 partitions.
sarnold@bgsuvax.UUCP (G. Steve Arnold) (04/07/91)
From article <1991Mar27.013413.5732@wpi.WPI.EDU>, by acoolidg@wpi.WPI.EDU (Aaron P Coolidge): > > Help! I just got a WD7000 SCSI controler. Now, my win3 will not run > in 386 enhanced mode- it gets to the banner, and then i get the "C:\" > prompt back! > I had been running windows in 386enh for almost 6 months with my old > controler/drive, so I don't believe it's the machine. > I don't know how moch stock you want to put in my response, as I don't have a lot of experience with hardware yet, but I had a similar problem with windows when (during a recent hard drive cleaning up and compacting session) I deleted all of the extranneous (sp?) .FON (windows) fonts that I had not been using since I got ATM (wonderful!). Anyway, Apparently I managed to delete the 'system' font, or whatever it is that windows 3 uses as a default to the screen. The point is that apparently windows started to boot, and got to where it was supposed to load all of the cool environment stuff (BMP's, etc..) and saw that it couldn't find the system font (having been deleted). Unable to utilize all of windows enhanced features, windows simply dumps you back to the dos prompt. The solution? I had just made a hard drive backup, so I simply restored the necessary files. However I understand that booting up in real mode and running setup to change whatever system drivers or parameters you need to is really the way to go. Hope this helps... Steve. (sarnold@andy.bgsu.edu)