#Hang At Boot
5 messages in this thread
I have been using the AUTOEXEC.BAT & CONFIG.SYS files shown below (without the
lines commented out) for quite some time with an Always 1N-2000 controller.
The CD-ROM performed flawlessly. Recently I added a DAT tape backup (Python
DAT) to the SCSI chain.
LASTDRIVE=F
Files=30
BUFFERS=10
DOS=HIGH
DEVICE=D:\386max\386max.sys pro=d:\386max\386max.pro
rem Device=D:\NAV\NAVTSR.EXE (Not Enough UMB To Load High)
rem DEVICE=D:\CORELDRV\ASPIDRVR.SYS
rem DEVICE=D:\CORELDRV\CUNI_ASP.SYS /ID:2 /HAN:0 /N:1 /D:MSCD000 /C:0
rem DEVICE=D:\PCKWIK\PCKCDROM.SYS /Conventional=Yes /Device=MSCD000
DEVICE=D:\386MAX\386load.sys size=11776 prog=D:\PCKWIK\PCKRAMD.SYS
DEVICE=D:\SB16\DRV\ASP.SYS /P:220
DEVICE=D:\DOS\ANSI.SYS
SHELL=D:\DOS\COMMAND.COM D:\DOS\ /E:512 /p
INSTALL=D:\DOS\SHARE.EXE /L:350
SWITCHES=/W
FCBS=1
BREAK=ON
STACKS=0,0
@ECHO OFF
@SET TEMP=C:\
@SET TMP=C:\
@SET NU=D:\NORTON
@SET SYMANTEC=D:\SYMANTEC
@SET MOUSE=D:\MOUSE
@SET SOUND=D:\SB16
@SET BLASTER=A220 I10 D0 H7 P330 T6
@SET TOOLROOTDIR=D:\MSVC
@SET INCLUDE=D:\MSVC\INCLUDE;D:\MSVC\MFC\INCLUDE
@SET LIB=D:\MSVC\LIB;D:\MSVC\MFC\LIB
@SET INIT=D:\MSVC
@D:\SB16\SBCONFIG.EXE /S
@D:\SB16\SB16SET /M:220 /VOC:220 /CD:220 /FM:220
rem D:\CORELDRV\CORELCDX.COM /L:F /M:4 /D:MSCD000
@VERIFY OFF
@D:\DOS\DOSKEY /INSERT
@D:\MOUSE\MOUSE.EXE
@D:\PCKWIK\SUPER.EXE /ConfigFile=D:\PCKWIK\PCKWIK.INI
@D:\NORTON\IMAGE.EXE C: /NOBACKUP
@D:\NORTON\IMAGE.EXE D: /NOBACKUP
PROMPT $e[1;32m$P$G
PATH D:\DOS;C:\BATFILE
@D:\UTIL\ADD2PATH D:\WINDOWS
@D:\UTIL\ADD2PATH D:\DOS
@D:\UTIL\ADD2PATH D:\UTIL
@D:\UTIL\ADD2PATH D:\NORTON
@D:\UTIL\ADD2PATH D:\NAV
@D:\UTIL\ADD2PATH D:\MSVC\BIN
@D:\UTIL\4GETNOT.EXE /D
CLS
With the tape drive added, the machine hangs at boot with NOTHING commented
out!. Taking out the PCKWIK disc caching allowed the machine to boot in DOS.
However, Windows would hang at boot. Removing ASPIDRV.SYS and it's associated
drivers will allow Windows to boot.
I have done a plain vanilla and have come to the conclusion that adding a tape
drive to the system causes ASPIDRV.SYS to do something that prevents Windows
from booting, or DOS from booting with PC-KWIK loaded. I have even tried a
different manufacturer of SCSI DAT drive, with the same negative results!
As a test, I removed PC-KWIK, booted in DOS with ASPIDRV.SYS, and was able to
run the tape drive from DOS, backing up and verifying perfectly.
The version of ASPIDRV.SYS is unknown, however, the file size is 15,168 and the
date is 11-10-92. DOS, Windows, PC_KWIK and QEMM386 are the latest versions.
DOS 6.0 & 6.2 have the same effect.
Whew! I hope that this is enough data to help you give me an answer as to
where my problem lies.
Thanks. Any speed would be appreciated, in as much as I am effectively down
without the CD-ROM drive.
Barry
Nobody from Corel will be around here until Monday and all next week will
probably be a zoo for them anyway as Comdex rages and they introduce a bunch of
new products including CorelSCSI 2.0.
I've had conflicts with PCKwick in a number of areas and finally dropped it,
but it may not be your problem.
Do you have an ASPI manager from Always or is that it? DAT drives have been
the bane of many SCSI cards of late. Also, do you have CorelSCSI 1.2b? Much DAT
support was built in and modified in that version. If not, you can get 1.2b for
free by requesting it from Customer Service (S4 here) or spring for the 2.0
upgrade in a couple of weeks.
Jack –
My problem turned out to be an outdated ASPI Manager supplied with CorelSCSI
from Always. Always had a brand new one on their BBS, and claim to have
written it FOR Corel. They also claimed that it has not as yet been introduced
by Corel. Me thinks that it is part of 2.0!!
Download 461-1350.ZIP from Always' BBS, UNZIP it, and replace the Corel ASPI
driver. My tape works well and so does my CD-ROM.
I will probably spring for the upgrade, as I fell that the Windows apps in my
version leave a lot to be desired. Not a complaint, just a statement of fact.
I would appreciate any details on 2.0, or reference to an article about it.
Barry
Barry,
Now that I've found this I will drop a line here as well <grin>.
Ok, the ASPI manager for the ALWAYS IN2000 is ASPIDRVR.SYS. Our Generic ASPI
manager for the ADAPTEC 1540 and BUSLOGIC 540 series aof controllers is
ASPIDRV.SYS. Please note the diference. I think that it was probably just a
typo and you are using the proper ASPI manager, but I just wanted to make sure.
There has been a flurry of activity in regards to the ALWAYS's IN2000 ASPI
interface. I would suggest down-loading from their BBS their version 12.8.
Although we distribute these files, they are the property of the controller
manufacturers (except ASPIDRV.SYS).
I hope this helps. You'll notice that if you log into their BBS you'll see a
flashing message that asks you to update to 12.8.
Laszlo
Laszlo –
I have found this out from Always, downloaded their driver, and all works now.
How can I get some information about 2.0? I like the CorelSCSI system, but
frankly, the DAT drive software leaves a lot to be desired. I hope that
improvements have been made.
Barry