Unable to Get LiteOn CD-RW Drive Recognized i n DOS

[Guest]

Archived from groups: alt.comp.periphs.cdr,comp.sys.ibm.pc.hardware.cd-rom,comp.sys.ibm.pc.hardware.storage (More info?)

Am trying to adapt my "CD Rescue" dos backup program to work with a 2nd
computer equipped with a LiteOn CD RW drive instead of the Plextor drive
installed in my #1 computer. Both computers are using win2k operating
system. The CD Rescue program is a DOS based program

The LiteOn drive is model SOHR-5238S

My LiteOn drive is recognized by my BIOS in the #2 computer , but I've been
unable to get it recognized in DOS when using the modified CD Rescue floppy
start up diskette.

I assume the problem is due to my failure to properly modify the
"config.sys" and "autoexec.bat" files on my startup diskette.

The startup disk for the Plextor equipped #1 computer include the following
entries for these respective files:

The autoexec entry is:
A:\MSCDEX.EXE /D😛LEX0001

The config.sys entries are:
Last drive=Z
DEVICE=A:\ASPI8XX.SYS
DEVICE=A:\SYMCD.SYS /D😛LEX001
DOS=UMB
Files=30
buffers=30

Any suggestions as to changes that I should make in these two files to
enable the LiteOn drive to be recognized in DOS would be much appreciated.

 

[BobS]

Archived from groups: alt.comp.periphs.cdr,comp.sys.ibm.pc.hardware.cd-rom,comp.sys.ibm.pc.hardware.storage (More info?)

Charles,

the autoexec.bat and config.sys files you have are too specific, and point
to the plextor drive. win 98 can create a boot disk for you with the generic
oaki.something drivers, or you can go to bootdisk.com and download a generic
boot floppy that will enable your LiteOn CD drive to work with.

Bob


"Charles V" <volkland@jps.REMOVE THIS.net> wrote in message
news:cliAd.742$Cc.414@newsread3.news.pas.earthlink.net...
> Am trying to adapt my "CD Rescue" dos backup program to work with a 2nd
> computer equipped with a LiteOn CD RW drive instead of the Plextor drive
> installed in my #1 computer. Both computers are using win2k operating
> system. The CD Rescue program is a DOS based program
>
> The LiteOn drive is model SOHR-5238S
>
> My LiteOn drive is recognized by my BIOS in the #2 computer , but I've
> been
> unable to get it recognized in DOS when using the modified CD Rescue
> floppy
> start up diskette.
>
> I assume the problem is due to my failure to properly modify the
> "config.sys" and "autoexec.bat" files on my startup diskette.
>
> The startup disk for the Plextor equipped #1 computer include the
> following
> entries for these respective files:
>
> The autoexec entry is:
> A:\MSCDEX.EXE /D😛LEX0001
>
> The config.sys entries are:
> Last drive=Z
> DEVICE=A:\ASPI8XX.SYS
> DEVICE=A:\SYMCD.SYS /D😛LEX001
> DOS=UMB
> Files=30
> buffers=30
>
> Any suggestions as to changes that I should make in these two files to
> enable the LiteOn drive to be recognized in DOS would be much appreciated.
>
>

 

[Guest]

Archived from groups: alt.comp.periphs.cdr,comp.sys.ibm.pc.hardware.cd-rom,comp.sys.ibm.pc.hardware.storage (More info?)

On Tue, 28 Dec 2004 19:19:36 GMT, "Charles V" <volkland@jps.REMOVE
THIS.net> wrote:

>The autoexec entry is:
>A:\MSCDEX.EXE /D😛LEX0001 <=================
>
>The config.sys entries are:
>Last drive=Z
>DEVICE=A:\ASPI8XX.SYS
>DEVICE=A:\SYMCD.SYS /D😛LEX001 <=================
>DOS=UMB
>Files=30
>buffers=30

You have different device names, they should be the same. Note the
extra "0" in PLEX0001 in autoexec.bat.


--
N

 

[Guest]

Archived from groups: alt.comp.periphs.cdr,comp.sys.ibm.pc.hardware.cd-rom,comp.sys.ibm.pc.hardware.storage (More info?)

Thanks Noik,
That was a typo error when I typed my posting. The device names are correct
on the actual floppy ---- the floppy works on my #1 computer that has the
Plexwriter drive. I just need to change the device listings and cd driver
listing to reflect the use of the LiteOn drive (in lieu of the Plexwriter
drive), for use with my #2 computer. I have no info as to what to use as an
identification entry for the LiteOn drive ---- hopefully, someone in the
forum will know the correct identification symbol for the LiteOn model,
noted in my posting.

In my posting, I failed to mention that I have the LiteOn drive connected as
a single drive to the IDE Secondary socket and jumpered as Master/single.

CharlesV


<Noik> wrote in message news:8oi3t0hfdpd7nm1lmrlojs0ntfn0sm9rlk@4ax.com...
> On Tue, 28 Dec 2004 19:19:36 GMT, "Charles V" <volkland@jps.REMOVE
> THIS.net> wrote:
>
> >The autoexec entry is:
> >A:\MSCDEX.EXE /D😛LEX0001 <=================
> >
> >The config.sys entries are:
> >Last drive=Z
> >DEVICE=A:\ASPI8XX.SYS
> >DEVICE=A:\SYMCD.SYS /D😛LEX001 <=================
> >DOS=UMB
> >Files=30
> >buffers=30
>
> You have different device names, they should be the same. Note the
> extra "0" in PLEX0001 in autoexec.bat.
>
>
> --
> N

 

[Nil]

Archived from groups: alt.comp.periphs.cdr,comp.sys.ibm.pc.hardware.cd-rom,comp.sys.ibm.pc.hardware.storage (More info?)

On 28 Dec 2004, "Charles V" <volkland@jps.REMOVE THIS.net> wrote in
news:XvkAd.887$Cc.581@newsread3.news.pas.earthlink.net:

> I have no info as to what to use as an identification
> entry for the LiteOn drive ---- hopefully, someone in the forum
> will know the correct identification symbol for the LiteOn model,
> noted in my posting.

If you mean the string to use where you currently use "PLEX0001", I
thought that was aribitrary, that you could use anything as long as it
agreed in both autoexec.bat and config.sys.

Maybe SYMCD.SYS isn't compatible with the Lite-On?

Maybe you don't have enough low memory to load the driver. Try
installing HIMEM.SYS and EMM386.EXE and loading the CD driver like this
(although I think it will usually load high on its own if it can):

LOADHIGH DEVICE=A:\SYMCD.SYS /D😛LEX0001

 

[Guest]

Archived from groups: alt.comp.periphs.cdr,comp.sys.ibm.pc.hardware.cd-rom,comp.sys.ibm.pc.hardware.storage (More info?)

You neglect to mention the dos messages as you boot. Prior to getting the
command prompt you should get an acknowledgement that dos was able to
recognize and assign a drive letter. If you are not getting that, try using
a generic driver.
Dave Cohen

"Nil" <rednoise@REMOVETHIScomcast.net> wrote in message
news:Xns95CDB94D24570nilch1@204.127.204.17...
> On 28 Dec 2004, "Charles V" <volkland@jps.REMOVE THIS.net> wrote in
> news:XvkAd.887$Cc.581@newsread3.news.pas.earthlink.net:
>
>> I have no info as to what to use as an identification
>> entry for the LiteOn drive ---- hopefully, someone in the forum
>> will know the correct identification symbol for the LiteOn model,
>> noted in my posting.
>
> If you mean the string to use where you currently use "PLEX0001", I
> thought that was aribitrary, that you could use anything as long as it
> agreed in both autoexec.bat and config.sys.
>
> Maybe SYMCD.SYS isn't compatible with the Lite-On?
>
> Maybe you don't have enough low memory to load the driver. Try
> installing HIMEM.SYS and EMM386.EXE and loading the CD driver like this
> (although I think it will usually load high on its own if it can):
>
> LOADHIGH DEVICE=A:\SYMCD.SYS /D😛LEX0001

 

[Guest]

Archived from groups: alt.comp.periphs.cdr,comp.sys.ibm.pc.hardware.cd-rom,comp.sys.ibm.pc.hardware.storage (More info?)

Thanks BobS for your response.

I've checked out bootdisk.com ---- but am not sure which of the multiple
bootdisk options to use as a win2k startup disk. I have downloaded the
WinImage file that appeared to be suggested for use on win2k. However, I
cannot find the procedure for generating the single bootdisk that was
referenced under the paragraph 3, copied below:
"3. The W2K Pro disks are zipped images from the MS CD. Best bet is to
download them, upzip them to a new folder where you also put makeboot.exe
and makebt32.exe into and then run one of the makeboot utils depending on if
you're in dos or windows to create the diskset. Or, one can use Winimage to
just create a single bootdisk. "

I'm on unfamiliar ground here ---- can you give me some further guidance?

CharlesV

 

[Guest]

Archived from groups: alt.comp.periphs.cdr,comp.sys.ibm.pc.hardware.cd-rom,comp.sys.ibm.pc.hardware.storage (More info?)

My last attempted edit of a startup disk for the #2 computer included the
following:

config.sys

LASTDRIVE=Z
DEVICE=A:\SBIDE.SYS
DEVICE=A:\cdrom.SYS/D:MSCD001

files=30
buffers=30


autoexec

ECHO OFF
A:\MSCDEX.EXE /D:MSCD001



On this disk, I also included the driver file "cdrom.sys" which is listed as
the LiteOn driver in the win2k Control Panel under Systems/hardware/device
manager.

I used the location entry as "DEVICE=A:\SBIDE.SYS" , based on a suggestion
covering instances where the IDE Secondary was used as the interface ----
not sure that this was a proper entry, however.

When using this disk, the DOS sequence stalled out at config.sys ----- prior
to reaching the point of recognizing the CD drive.

CharlesV

 

[BobS]

Archived from groups: alt.comp.periphs.cdr,comp.sys.ibm.pc.hardware.cd-rom,comp.sys.ibm.pc.hardware.storage (More info?)

David,

if you download the DOS 6.22 boot disk file, and make a boot floppy from it,
you should be able to boot with the floppy; when it boots up, choose the CD
support item. It has been a really long time since I did it, but I remember
that it did work fine. After it finishes booting to the DOS A: prompt, You
can run the file you want from your recovery CD. You mentioned that your
Recovery program runs from a DOS prompt, so this is the reason I went this
way with you.

Also, as I remember, the CD drive letter when you boot up with the Bootdisk
floppy is letter R. I could be wrong, but I believe that is is R.

You are running Win2000, but if your recovery program "sees" the NTFS files
on your hard drive or other Image source, it should work OK. You never
mentioned your recovery program, so I do not even know if I am familiar with
it or not.

Best regards,

Bob
"Charles V" <volkland@jps.REMOVE THIS.net> wrote in message
news:0UlAd.955$Cc.15@newsread3.news.pas.earthlink.net...
> Thanks BobS for your response.
>
> I've checked out bootdisk.com ---- but am not sure which of the multiple
> bootdisk options to use as a win2k startup disk. I have downloaded the
> WinImage file that appeared to be suggested for use on win2k. However, I
> cannot find the procedure for generating the single bootdisk that was
> referenced under the paragraph 3, copied below:
> "3. The W2K Pro disks are zipped images from the MS CD. Best bet is to
> download them, upzip them to a new folder where you also put makeboot.exe
> and makebt32.exe into and then run one of the makeboot utils depending on
> if
> you're in dos or windows to create the diskset. Or, one can use Winimage
> to
> just create a single bootdisk. "
>
> I'm on unfamiliar ground here ---- can you give me some further guidance?
>
> CharlesV
>
>