Solved

ASPI2DOS.SYS ASPI8DOS.SYS ERRORS

Posted on 1998-12-10
1
186 Views
Last Modified: 2013-12-16
I apologize for asking this question, as I know something similiar has been answered before, but I have gone through nearly 1000 postings, and cannot find the previous resolution to this problem.  I have formatted and installed Windows 95 into my workstation.  I used the Windows 98 bootdisk so that I could load CD Rom drivers, because my Windows 95 bootdisk never seemed to do that so I could install the appropriate drivers.  I have now got Windows running, however, whenever I boot, and press ESC, I can see these two errors.  I have recently found the diskette for P5/P6 IDE drivers, and have loaded that, however, I continue to get the same errors.  I was hoping that was the diskette with the appropriate files to get rid of this problem.  

I do not have a previous DOS OS installed, Windows 95 was loaded with 98 bootdisk and so, I don't know why I need any *DOS.SYS drivers.  Who knows, I figure this has to do with the ATAPI driver (either CD or IDE hard drive)....any help very much appreciated!
0
Comment
Question by:Indi
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 4

Accepted Solution

by:
swwelsh earned 50 total points
ID: 1760161
aspi2dos.sys and aspi8dos.sys are real mode drivers for SCSI cdroms or other SCSI devices. Your win98 bootdisk probably loads them in case you have a SCSI cdrom. Check your config.sys and autoexec.bat files in c:\ to see if these drivers are trying to load at bootup. Type  rem in front of the lines that refer to these drivers to remark out the line (windows will then ignore them), or better yet, rename the config.sys file to config.bak and autoexec.bat to autoexec.bak. You should not need these files once win95 is installed, and they will slow down the boot process. If you need to boot the system with cdrom drivers at some future date, just rename the config.bak and autoexec.bak to their original names and then windows will read them and load the cd drivers.
0

Featured Post

Creating Instructional Tutorials  

For Any Use & On Any Platform

Contextual Guidance at the moment of need helps your employees/users adopt software o& achieve even the most complex tasks instantly. Boost knowledge retention, software adoption & employee engagement with easy solution.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Determining the an SCCM package name from the Package ID
In this post we will be converting StringData saved within a text file into a hash table. This can be further used in a PowerShell script for replacing settings that are dynamic in nature from environment to environment.
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question