Revision history:
2003-03-19 Additions to S7 (help), S18 (debug)
2003-03-03 Initial version
-----------------------------------------------------------------
I have compiled a guide on troubleshooting InCD problems under Windows 98x. (Although I'm running 98SE only, I've had input from users of 98 and ME.)
This guide (given below) may help some users until Ahead updates their FAQs and Help files (hopefully soon).
In most cases recent versions of InCD should work if you use media matched to your burner with recent firmware, and your OS is reasonably clean (without drivers installed by other burning programs that conflict with InCD).
Thus, before blaming InCD itself, you should test other factors carefully, and this may take a long time. If you want help from other forum members, follow the steps below and report as many details as possible. A bad (but frequent) example is where a user reports InCD problems after testing a single disc supplied with a new burner.
Beware that packet writing with InCD is in general less reliable than multisession writing to CD-R discs with Nero. However, I am not trying to scare you away from packet writing. I have been using it for about five years without loosing a single file. For me it is more convenient than multisession writing when just a couple of files change between backups. But its unreliability shouldn't be ignored: I would never delete any important file from my HDD after copying it to an InCD disc.
I intend to update this guide periodically. Hence I'll welcome comments, suggestions and especially reports of success stories. However, please refrain from posting messages such as "It didn't work for me" here; if you need help, start or join another thread. Simply speaking, if several users wanted to troubleshoot their individual problems in the same thread, this would only result in total confusion.
Finally, here is the guide itself.
---Steps for Troubleshooting InCD Problems under Windows 98x---
S1. Upgrade the firmware of your burner to the latest version from your vendor's or original manufacturer's website. Frequently new firmware will enable your burner to accept more media.
S2. Check your vendor's website for recommended CD-RW media. Search the Web (Google) for reviews of your burner and users' experiences with different media at
www.cdfreaks.com ,
www.cdrinfo.com and
www.cdrlabs.com . You may expect problems: 24x re-writers are fairly new and probably not tested much on older media, whereas 24x and even 16x media are hardly available. In particular, Memorex CD-RW discs are not recommended.
S3. To check if your problems are not due to one specific brand of media, try several brands. Thus, depending on your burner, get at least a couple of 4x, 4x-10x, 4x-12x or 24x CD-RW discs from several better known vendors (see S2 above). Note that old 4x re-writers usually won't work with High Speed or Ultra Speed media. Unfortunately InCD no longer allows you to control rewriting speeds.
In particular, if your burner is old, most probably it can't handle High Speed discs, which have "High Speed" included in the Compact Disc ReWritable logo on their covers, and are usually rated at 4x-10x or 4x-12x (but even 1x-10x indicates an HS disc, since the rated speed exceeds 4x). If your burner can only rewrite at 4x, its laser system doesn't meet the requirements of the newer HS technology. Then you should look for CD-RW discs rated at 1x-4x, or older discs rated at 2x. Such discs are gradually disappearing from the market, so in the long run, upgrading your burner may be the only solution.
You can check which speeds are listed for your media in Nero itself (for a blank CD-RW), and in Nero CD Speed and InfoTool. BTW, the latest version of Nero usually installs quite recent versions of CD Speed and InfoTool (see Start | Programs | Ahead Nero | Nero Toolkit), which are highly useful for troubleshooting InCD; the latest versions may be downloaded from
www.cdspeed2000.com .
S4. If you wish to re-use a disc (e.g., because it failed in your experiments, or was formatted by earlier versions of InCD, DirectCD, etc), don't try to save time by using any quick formatting or quick erase options; always do full-erase in Nero | Recorder | EraseReWritable.
Note that each CD-RW disc can handle only a finite number of rewrites. Manufactures may claim 1000 or more, but most users say 100 is a more realistic estimate. Yet there are tests showing that some poor media may become unusable after just 5 rewrites. To check your discs, you may run Nero CD Speed | Extra | CD Quality and Scandisc.
S5. If InCD fails to mount a formatted disc, run CD Speed Scandisc to see if there are bad sectors, especially initial ones.
S6. Before upgrading to the latest version of InCD from
www.ahead.de , remove the previous version via Control Panel | Add/Remove Programs, selecting "Ahead InCD", and reboot. Similarly, remove "InCD EasyWrite Reader" and "InCD UDF Reader" if they are listed, and reboot.
Since recent versions of InCD uninstall cleanly, there is little danger in version switching. Note, however, that InCD 3.37 has the infamous rename bug, and InCD sometimes fails to handle discs formatted with earlier versions (mostly CD-MRW discs, so back them up).
To check if your burner is supported by InCD, see
http://www.ahead.de/en/index.html#c1002822556070
http://www.ahead.de/en/index.html#recorder
(you may choose Products | InCD | Supported Recorders if these links don't work). Since Ahead's documentation may be outdated, even if your burner is not listed, but it works with Nero, it will probably work with InCD as well.
S7. Download the InCD manual from Ahead's site (Products | InCD | Documentation); although outdated, it gives general ideas about InCD. (In particular, the final format OK message has disappeared in recent versions, which give only the InCD mounted message.)
The help in InCD versions downloaded from Ahead's site frequently doesn't work, because the setup program fails to put the help file InCD_Us.chm into the InCD directory C:\Program Files\Ahead\InCD. There are three ways to get InCD_Us.chm:
S7.1. If you have a fairly recent Nero installation disc, you may find it on the CD (e.g., in the directory \Nero\InCD).
S7.2. Run the InCD installation program (e.g., InCD35220b.exe) until it asks you: Reboot | Finish? At this stage, open Windows Explorer and navigate to your TEMP directory; on my box this is
C:\TMP
Its subdirectory RarSFX0 should contain InCD_Us.chm; copy this file to C:\Program Files\Ahead\InCD before giving a final click to the InCD setup program (which will remove RarSFx0).
S7.3. You may create a scratch directory C:\InCD and unpack the InCD installation program (e.g., InCD35220b.exe) to C:\InCD via, e.g., WinRar from
www.rarlab.com or Total Commander from
www.ghisler.com (using Files | Unpack Specific Files...); then look in C:\InCD.
S7.4. To get some (again outdated) info, use Windows Explorer to call up C:\Program Files\Ahead\InCD\InCD.hlp and click Index, or anything else that's clickable (doesn't work in normal way).
S8. Before formatting with InCD, make sure there are no "heavy" programs running in the background. Also before writing to InCD formatted discs, it may be wise to disable virus scanners, etc.
There are differences between standard CD-RW (UDF 1.50) and CD-MRW (Mt. Rainier) formatting. (To verify whether your burner supports CD-MRW, see if Nero InfoTool | Drive has a checkmark for Mount Rainier, or right-click on the InCD icon and select InCD Property Sheet | InCD Page Settings to see whether the option "Format disc to CD-MRW" exists.) For instance, on a CD-RW 80min/700MB 10x disc, for a standard CD-RW (non-MRW) formatting, physical format takes about 8 min and logical format takes about 3 min (i.e., 11 min in total). In contrast, initial CD-MRW formatting takes about 30 sec (the disc is usable at this stage), whereas background formatting takes about 9 min (without influencing copy speeds); in both stages, ejecting the disc takes several seconds (this is for Lite-On LTR48125W). As for space, InCD reports 50KB used, 572MB free for CD-RW, whereas CD-MRW has 539MB free.
Concerning readability of InCD discs in CD-ROM or DVD-ROM drives, XP with SP1 can read standard UDF 1.50 discs natively, whereas both standard and CD-MRW discs are readable under 98x, W2K and XP after installing Ahead's EasyWriteReader (download the latest version by selecting InCD | Utilities). This is independent of whether InCD is installed, but the reader should be MultiRead compliant (as are most drives used nowadays).
Here is how you may format a CD-RW disc in InCD.
A. Choose the standard CD-RW format or the CD-MRW (Mt. Rainier) format.
Right-click the InCD icon in the taskbar notification area near the clock, and select Properties. When the InCD Property Sheet pops up, select InCD Page Settings, and either check or uncheck the option "Format disc to CD-MRW" (if this option is missing, either your burner doesn't support CD-MRW, or InCD isn't installed properly). I leave the other two options (messages and Safe mode) unchecked. Close the sheet.
Alternatively, to call up the InCD Property Sheet, right-click your burner's icon in My Computer or Windows Explorer.
B. Insert a blank CD-RW disc into your writer. When the InCD Disc Information pops up, you may cancel it (nothing useful there). Right-click the taskbar InCD icon and select Format. When the InCD Wizard starts running, press Next, then select a drive if you have more than one, and click Next. If you wish to change the formatting options, click on Properties to access InCD Page Settings; otherwise click Next. Choose the Volume Label (no spaces!) and click Finish. Formatting proceeds in two stages, and displays progress information (which is not always consistent). Finally, you'll see the InCD message "The disc was mounted in InCD UDF file format", as indicated by the green N-W arrow on the InCD icon.
Note that some earlier versions of InCD eject a disc after formatting.
The InCD icon should stay green while the disc is used (for copying, etc). When the disc is ejected, the InCD icon has a red S-E arrow (indicating there is no medium or InCD-formatted medium in the drive).
As for using a previously formatted disc, on my box with Autorun on, after the disc is inserted, the arrow on the InCD icon flips from red S-E to green N-W after about 20 seconds, the InCD mounted message pops up, and Explorer shows the disc contents, unless I keep pressing the Shift key after closing the tray.
The third possibility is that the icon is a yellow circle with an exclamation mark and a red S-E arrow, which means that no InCD-supported CD-RW drive could be found. (This may occur if an external drive is not turned on.)
Finally, a big WARNING: Always Eject from the InCD icon or Explorer; using the recorder's eject button may spoil the disc! Ejecting via the button may seem to work, but if InCD doesn't finish properly, data will be lost (possibly later because some structural information is corrupted).
BTW, if you want to keep an InCD disc in your drive for a longer period, you should first eject it after doing backups so that a proper TOC gets written; otherwise you could loose data if your system crashes!
S9. If your burner supports CD-MRW (Mt. Rainier) formatting, experiment with it separately from the standard CD-RW (UDF 1.50) formatting. It may happen that your combination of burner/media/software will work only with one of these formats.
S10. Sometimes InCD works only with Autorun off (as reported by Nero InfoTool | Configuration). For 98x systems, Autorun means Autoinsert Notification, and you can use Control Panel | Device Manager to set it to "off" for your burner (well, I have it on, as well as DMA on). Note that some burning programs may require that Autoinsert Notification be on (or off), and they might even change its status without telling you. The "proper" setting of Autorun for InCD may depend on the burner, its firmware, IDE bus, etc. Until Ahead clarifies this issue, one has to experiment.
S11. Expect trouble if, before installing InCD, you ran other packet writers (e.g., Roxio's DirectCD), UDF readers (again Roxio's UDF Reader) or burning plugins installed "silently" by other programs (e.g., Windows Media Player, WinAmp, RealPlayer, etc). Such applications typically install drivers conflicting with InCD, which are not removed even if you remove the application itself. Still you should first try to remove such applications or their burning plugins via Control Panel | Add/Remove Programs before doing manual cleanups described below (e.g., for WMP 7.x, you may be asked first whether you want to remove WMP; answer Yes, and then select only the Adaptec plugin for removal).
S11.1. Since I've never installed such software, I can't identify all possible culprits. To this end, note that on my 98SE box with Nero 5.5.10.0, InCD 3.51.91 and the latest EasyWriteReader from Ahead's site, my C:\Windows\System\IOSUBSYS directory listed as follows:
APIX VXD 29,497 04-23-99 10:22p APIX.VXD
ATAPCHNG VXD 11,311 04-23-99 10:22p ATAPCHNG.VXD
BIGMEM DRV 9,952 04-23-99 10:22p BIGMEM.DRV
BSUDF VXD 260,803 12-12-02 5:52p bsudf.vxd
BSUDFRDR VXD 114,367 01-05-03 1:53a bsudfrdr.vxd
CDFS VXD 59,133 04-23-99 10:22p CDFS.VXD
CDRBSVSD VXD 14,105 10-28-02 3:53p CDRBSVSD.vxd
CDTSD VXD 13,884 04-23-99 10:22p CDTSD.VXD
CDVSD VXD 32,419 04-23-99 10:22p CDVSD.VXD
DISKTSD VXD 18,889 11-17-99 5:36p DISKTSD.VXD
DISKVSD VXD 10,194 04-23-99 10:22p DISKVSD.VXD
DRVSPACX VXD 57,642 04-23-99 10:22p DRVSPACX.VXD
ESDI_506 PDR 24,406 04-23-99 10:22p ESDI_506.PDR
HSFLOP PDR 25,741 04-23-99 10:22p HSFLOP.PDR
INCDRM VXD 23,715 01-05-03 1:53a incdrm.VXD
NECATAPI VXD 9,926 04-23-99 10:22p NECATAPI.VXD
NEROCD95 VXD 39,882 03-11-02 11:55a nerocd95.vxd
NTMAPHLP PDR 9,849 10-12-99 2:56p NTMAPHLP.PDR
RMM PDR 13,242 04-23-99 10:22p RMM.PDR
SCSI1HLP VXD 19,270 04-23-99 10:22p SCSI1HLP.VXD
SCSIPORT PDR 23,650 04-23-99 10:22p SCSIPORT.PDR
TORISAN3 VXD 11,067 04-23-99 10:22p TORISAN3.VXD
VOLTRACK VXD 18,491 04-23-99 10:22p VOLTRACK.VXD
The 04-23-99 files are original 98SE, DISKTSD.VXD and NTMAPHLP.PDR come from the MS 1394 supplement (needed by my external FireWire enclosure), NEROCD95.VXD is due to Nero, BSUDF.VXD and CDRBSVSD.VXD come from InCD 3.51.91, whereas BSUDFRDR.VXD and INCDRM.VXD come from EasyWriteReader. (Upgrading to Nero 5.5.10.7b and InCD 3.52.00b only changed BSUDF.VXD to 274,120 01-15-03 6:06p, whereas upgrading to Nero 5.5.10.15a and InCD 3.52.20b changed BSUDF.VXD to 131,268 02-12-03 5:22a.)
To obtain a comparable listing, in an MS-DOS Prompt window, type
dir C:\Windows\System\Iosubsys >C:\iosubsys.txt
and Enter to get the listing in the file C:\iosubsys.txt. Similarly, you may look for suspicious .dll files by typing
dir C:\Windows\System\cd*.dll >C:\syscddll.txt
If you see suspicious vxd or dll files on your box, you may try renaming their .vxd extensions to .vx_ and .dll to .dl_; however, before rebooting, you may also need to remove the registry settings for these files.
S11.2. IMPORTANT: Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs; see the Microsoft Knowledge Base article 256986 "Description of the Microsoft Windows Registry":
http://support.microsoft.com/default.as ... -US;256986
S11.3. For example, after incomplete removals of Roxio's Easy CD Creator, DirectCD, UDF Reader or the Adaptec/Roxio burning plugin of Windows Media Player (WMP) 7.0, 7.1 or 9.0, you may still have the following files in C:\Windows\System\Iosubsys:
Acbhlpr.vxd, Cdr4vsd.vxd, Cdralvsd.vxd, Cdrpwd.vxd,
Cdudf.vxd, Cdudfrw.vxd, UdfReadr.vxd
and in C:\Windows\System:
Cdr4dll.dll, Cdral.dll, Cdrtc.dll
After renaming these files (.vxd to .vx_, .dll to .dl_), to clean the registry, either remove the registry keys involving such files (search for abchlpr, cdr4vsd, etc), or use RegCleaner from
http://www.vtoy.fi/jv16/shtml/regcleaner.shtml
Similarly, the driver Iomega.vxd installed by WMP or Norton Utilities in C:\Windows\System\Iosubsys may cause problems, so you may rename it and clean its registry entries as indicated above.
Further, several users reported problems with the IOSUBSYS drivers Drvwppqt.vxd and Drvwq117.vxd, which come from MS/Seagate Backup (parallel-port type), but may also be installed for SCSI devices. Hence you may try renaming these drivers as well, unless they are required by your devices, such as a scanner adapter, etc. Finally, you may also rename the IOSUBSYS driver Scsi1hlp.vxd to Scsi1hlp.vx_, although this is unnecessary in most cases.
S11.4. For other (better) ways of removing the Adaptec plugin, and preventing it from being (re)installed by WMP, see
http://www.nwlink.com/~zachd/pss/pss.html
http://www.cdrlabs.com/phpBB/viewtopic.php?t=7494
In particular, to uninstall the Adaptec plugin of WMP 7.x, run
rundll32 advpack.dll,LaunchINFSection %windir%\inf\adaptec.inf,Uninstall
whereas for WMP 9.x you may run
rundll32 advpack.dll,LaunchINFSection %windir%\inf\roxio.inf,Uninstall
If you want to block WMP 7.1 or later from ever installing the Adaptec/Roxio plugin, you should run the adaptecblock.reg file, which contains the following four lines
REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MediaPlayer\Setup]
"AdaptecBlock"="1"
This will either create the AdaptecBlock keyword in the registry if it is missing (e.g., after a clean Windows installation), or change its value to 1 if it is already there.
Concerning WMP 9.0, the MS information in
http://www.microsoft.com/windows/window ... eadme.aspx
says that WMP can be removed via Control Panel | Add/Remove Programs in 98SE, or System Restore in ME, and that Roxio CD Burning is available under 98SE and ME, but it doesn't mention unistalling the burning plugin alone. (Hence I will wait until other users report their experiences with WMP 9.0 before installing it on my boxes.)
S11.5. You may also ask Ahead's tech support for Nero CleanTool
http://www.cdrlabs.com/phpBB/viewtopic. ... 3897#43897
which may obviate the need for manual removal of conflicting drivers.
S11.6. Here is some brief info on other burning plugins.
Apparently no version of WinAmp installs any burning plugins by default, so typically users download them and install separately. The most popular ones include the Veritas CD Recording Plug-in, QuickBurn MP3, and Burning CD plugin, but there are many others which might conflict with Nero/InCD.
RealPlayer is now called RealOne Player. For the free RealOne Player v1, one can buy Roxio CD Creator Plus, whereas in the commercial version of RealOne Player v2, CD burning is automatically available if you are a RealOne SuperPass member or a RealOne Player Plus user. You may expect conflicts with Nero/InCD, since Roxio CD Creator Plus is not compatible with RealOne Player v2.
I don't know if MusicMatch JukeBox conflicts with InCD under Win98x (but there are incompatibility reports under W2K, so you may need to uninstall it via Add/Remove Programs).
S11.8. There may be conflicts between InCD and drivers for some storage devices, such as older models of Iomega Zip drives, in which case you should uninstall such drivers (also see S11.3).
S12. Check what Nero InfoTool says about your ASPI layers (both System and Nero). Nero and InCD don't need special ASPI. You may be in trouble if other burning programs required installation of special ASPI layers. Many users reported problems with the latest Adaptec's ASPI (4.7x), and frequently they had to to revert to version 4.6 by using ForceASPI from
http://aspi.radified.com
http://www.afterdawn.com/software/cdr_s ... rcaspi.cfm
According to Nero InfoTool, the System ASPI on my 98SE box is
WNASPI32.DLL 1.0.0.0 April 23, 1999
APIX.VXD 4.00.952 April 23, 1999
WINASPI.DLL 1.00 April 23, 1999
so this is original ASPI of 98SE; further, Nero ASPI is not installed (otherwise you may have neroapix.vxd).
Old versions of EasyCD Creator and DirectCD installed aspienum.vxd in C:\WINDOWS\SYSTEM, replaced apix.vxd in C:\WINDOWS\SYSTEM\IOSUBSYS, and winaspi.dll and wnaspi32.dll in C:\WINDOWS\SYSTEM. Instead of retrieving the original 98x ASPI layer, it may be easier to use ForceASPI (you may also change the extensions of aspienum.vxd and apix.vxd to .vx_ and clean the registry before running ForceASPI).
S13. If your burner is connected to a RAID channel, try shifting it to an ordinary IDE channel. If your burner is connected through a USB Hub or extension cable, try connecting it directly to one of the USB ports on your computer.
S14. Check if you have the latest BIOS and chipset drivers for your motherboard by visiting its manufacturer's site. Note, however, that sometimes the latest drivers may conflict with InCD. For instance, instead of using Nvidia IDE drivers, you may need to revert to the standard Windows drivers.
Sometimes you may need to clean up ghosts for controllers (IDE, SCSI, USB, FireWire, Parallel Ports) and your burning devices in Device Manager. To this end, boot your system into Safe Mode. If Device Manager shows more than one entry for your burner (or other devices), remove all entries for the burner; when you reboot into normal mode the burner will be properly redetected. If you are unfamiliar with Safe Mode, see the MS KB article Q156126:
http://support.microsoft.com/default.as ... us;Q156126
S15. If you are running Intel's Applications Accelerator, you may uninstall it temporarily to get a cleaner testing environment. Note that IAA may prevent Windows and Nero InfoTool from reporting correct information about your drives.
S16. If your system freezes every few seconds, check if switching Autorun helps (see S10). Several users reported that their InCD slowdowns disappear when they leave a disc in their burner (so that InCD doesn't poll the burner to discover a fresh disc). Just remember not to leave an InCD disc in your drive, since it could be destroyed when Windows hangs and you have to power down your box.
There are also reports about system freezes when InCD is used with certain network cards. This may not be due to InCD. For instance, users of some 3Com NICs frequently deactivate the option of "Software cable detect", because otherwise the NIC polling may cause system freezes every few seconds.
S17. If none of the preceding fixes work, you may ask for help by starting a new thread. Please provide as much information as possible, since frequently details that look irrelevant at first sight turn out to be crucial for diagnosing a problem. Of course, you should describe precisely your problem and the error messages you get from InCD and Windows (if any) and whether your problem arose after any recent changes to hardware or software.
You should list the troubleshooting steps performed so far, and their results; if some step was skipped, explain why (e.g., not applicable, or you didn't know how to execute it).
Your post should also answer the following querries. (If you don't know how to handle a querry, mention it, so that other users may help.)
Q1. The model and firmware version of your burner, and how it is connected (internal IDE channel, USB (1.1 or 2.0) or FireWire (IEEE 1394), external interface (PCI or PC Card) if any). If you also have a CD-ROM or DVD-ROM drive, specify its model.
Q2. Hardware info for your box: motherboard and chipset for desktops, manufacturer and model for laptops.
Q3. Version of Windows service packs installed, if any.
Q4. Versions of Nero/InCD and other burning programs or plugins, and whether Nero works correctly with your CD-RW media (otherwise there is little point in dealing with InCD before other problems are fixed).
Q5. Brands and quantity of CD-RW discs used; if re-used, were they fully erased before reformatting?
Q6. Format version (UDF 1.50 or CD-MRW) and whether it proceeded as in Step S8.
Q7. What does Nero InfoTool | Configuration say about Autorun for your burner? Are the symptoms for your problem the same for Autorun set to on and to off (cf. S10)?
Q8. What does Nero InfoTool say about ASPI (both System and Nero)?
Q9. If other burning programs or plugins had been removed, was InCD reinstalled after the registry had been cleaned either manually or via programs such as RegCleaner?
Q10. The results of the dir commands described in S11.1.
Q11. A suitable extract from Nero InfoTool report (click the diskette button to save it to a file). To save space, you may give only the Driver Information section, skipping all Microsoft drivers and those nonrelated to CD burning (e.g., modem, scanner, etc.; if unsure about a driver, don't omit it). An example from my box follows:
Driver Information
------------------
Driver : bsudf
Description : UDF File System Driver
Version : 3.5.22.0
Company : B.H.A Co.,ltd.
Driver : bsudfrdr
Description : UDF Reader File System Driver
Version : 3.25
Company : B.H.A Co.,ltd.
Driver : CDRBSVSD
Description : CDR device specific driver for Windows95
Version : 5.0.1
Company : B.H.A Corporation
Driver : incdrm
Description : remapper
Version : Version 1.0.0.7
Company : Ahead Software AG
Driver : nerocd95
Description : Nero CD driver for Windows 95/98/ME
Version : 4.5.0.14
Company : ahead software gmbh
Q12. Once Nero is run, the file NeroHistory.log in C:\Program Files\Ahead\Nero lists useful system information. Since this file can be rather long, you may concentrate on its last session. Thus you may extract the initial information section (which ends with "Wizard: Off or On") and the final "Existing drivers" section from the Nero log file and post it. An example from my box follows:
Windows 98 4.10
WinAspi: File 'Wnaspi32.dll': Ver=1, 0, 0, 0, size=36864 bytes, created 4/23/99 10:22:00 PM
Nero Version: 5.5.10.15
Recorder: <LITE-ON LTR-48125W> Version: VS0B - HA 1 TA 0 - 5.5.10.15
Adapter driver: <NTMAPHLP> HA 1
Drive buffer : 2048kB
Bus Type : default (0) -> ATAPI, detected: ATAPI
CD-ROM: <TOSHIBA DVD-ROM SD-C2102>Version: 1729 - HA 0 TA 0 - 5.5.10.15
Adapter driver: <ESDI_506> HA 0
Bus Type : default (0) -> ATAPI, detected: ATAPI
TOSHIBA DVD-ROM SD-C2102 (Target 0, E:): Autoinsert Off, DMA On, Disconnect On, SyncDataXfer Off
LITE-ON LTR-48125W (Target 0, F:): Autoinsert On, DMA ?, Disconnect On, SyncDataXfer Off
Existing drivers:
File 'IoSubSys\SCSI1HLP.VXD': Ver=4.10.1998, size=19270 bytes, created 4/23/99 10:22:00 PM
File 'IoSubsys\NEROCD95.VXD': Ver=4.5.0.14, size=39882 bytes, created 3/11/02 11:55:38 AM
File 'IoSubsys\CDFS.VXD': Ver=4.10.1998, size=59133 bytes, created 4/23/99 10:22:00 PM
File 'IoSubsys\ESDI_506.PDR': Ver=4.10.2222, size=24406 bytes, created 4/23/99 10:22:00 PM
File '..\System32\Drivers\1394bus.sys': Ver=4.10.2224, size=38016 bytes, created 10/11/99 4:57:18 PM
File '..\System32\Drivers\Ohci1394.sys': Ver=4.10.2224, size=36256 bytes, created 11/5/99 5:37:56 PM
File '..\System32\Drivers\Ntmap.sys': Ver=4.10.2226, size=8704 bytes, created 3/27/00 1:40:58 PM
File 'IoSubsys\Ntmaphlp.pdr': Ver=4.10.2223, size=9849 bytes, created 10/12/99 2:56:42 PM
File '..\System32\Drivers\Sbp2port.sys': Ver=4.10.2225, size=35696 bytes, created 3/27/00 1:57:12 PM
File '..\System\Vmm32\Ios.vxd': Ver=4.10.2223, size=69594 bytes, created 10/12/99 3:02:40 PM
File 'IoSubsys\Disktsd.vxd': Ver=4.10.2223, size=18889 bytes, created 11/17/99 5:36:48 PM
File 'IoSubsys\BSUDF.VXD': Ver=3.5.22.0, size=131268 bytes, created 2/12/03 5:22:00 AM
File 'IoSubsys\CDRBSVSD.VXD': Ver=5.0.1, size=14105 bytes, created 10/28/02 3:53:02 PM
File 'IoSubsys\NTMAPHLP.PDR': Ver=4.10.2223, size=9849 bytes, created 10/12/99 2:56:42 PM (Adapter driver for rec)
