CD-RW failure to initialize
yorkie
Bear with the longish post but I've tried to include as much
as possible.
I'm attempting to backup the system (Warp 4, FP13) to
upgrade to v4.51.
Plan A is thwarted by the fact that the system will not
operate the
CD-Writer correctly. The system is as follows:-
SCSI HA 1 - Adaptec AHA-2944UW - BIOS enabled
SCSI HA 2 - Advansys ABP-20 - Narrow, BIOS not enabled
SCSI HDD x2 - on HA 1
SCSI Teac 532s CD-R - on HA 2, LUN 3
SCSI Ricoh MP7060S CD-RW - on HA 2, LUN 4
Intel 10/100 NIC - unconfigured
Aureal 2 sound card - unconfigured, no driver loaded
After Warp has booted-up the Writer has it's green LED on
all the
time when no CD is present (the CD-R does not). This makes
me
believe that it is a hardware problem but I am unsure as it
might
be the default for a Ricoh drive (i.e. the light is
constant). The
red LED always stays on all of time (when a CD is present),
never
less than five minutes, usually always on. The properties
notebook
of the CD-R will appear on selection but not for the CD-RW
(SYS0039 The ?: device is not ready).
When the system was built the CD drives operated as they
should
but they were then on an Adaptec AHA-1522 card. I had not
burnt
a CD for some months and it was only when I needed to
back-up
for the update that I noticed the problem. I've swapped the
Writer
for various others (all SCSI) but the issue persists and
I've also
swapped the Adaptec HA for the Advansys, again the result is
the
same. Cables ditto. Maybe a motherboard problem?
The only thing that might have some bearing is when going
into
Selective Install the CD-Rom Device Support section shows an
entry of "Other". I would have thought it should have been
something like "SCSI II".
Config.sys (part of) is:-
REM MODIFIED BY CONFIGSORT V2.1 ON 16/04/06 AT 11:35:13
REM *** INSTALLABLE FILE SYSTEMS ***
IFS=G:\OS2\HPFS.IFS /CACHE:64 /LAZY:OFF /CRECL:4
/AUTOCHECK:GHIJ
IFS=G:\OS2\BOOT\CDFS.IFS /Q /C:8 /M:32 /W
REM IFS=G:\IBMLAN\NETPROG\NETWKSTA.200 /I:G:\IBMLAN /N
REM *** BASE DEVICE DRIVERS ***
BASEDEV=IBMKBD.SYS
BASEDEV=TIMER0.SYS
BASEDEV=PRINT01.SYS
BASEDEV=CHKDSK.SYS
BASEDEV=IBM1FLPY.ADD
REM BASEDEV=IBM2FLPY.ADD
BASEDEV=XDFLOPPY.FLT
BASEDEV=AIC7870.ADD
REM BASEDEV=AHA152X.ADD /V
BASEDEV=ASC.ADD /V /A:0 /!DM:3 !SM:3 /!DM:4 /!SM:4 /I-
BASEDEV=OS2DASD.DMD
BASEDEV=OS2ASPI.DMD /ALL /SHARE (tried all the combinations
BASEDEV=OS2SCSI.DMD /SHARE - except the one that
works)
REM *** DEVICE DRIVERS ***
DEVICE=G:\OS2\BOOT\TESTCFG.SYS
DEVICE=G:\OS2\BOOT\DOS.SYS
DEVICE=G:\OS2\BOOT\PMDD.SYS
rem DEVICE=G:\OS2\BOOT\OS2CDROM.DMD /V
DEVICE=G:\OS2\BOOT\JJSCDROM.DMD /VP (tried this in
desperation)
DEVICE=G:\OS2\BOOT\POINTDD.SYS
DEVICE=G:\OS2\BOOT\MOUSE.SYS
DEVICE=G:\OS2\BOOT\COM.SYS
DEVICE=G:\OS2\BOOT\ASPIROUT.SYS /V
DEVICE=G:\OS2\MDOS\VEMM.SYS
DEVICE=G:\OS2\MDOS\VXMS.SYS /UMB
DEVICE=G:\OS2\MDOS\VDPMI.SYS
DEVICE=G:\OS2\MDOS\VDPX.SYS
DEVICE=G:\OS2\MDOS\VCDROM.SYS
DEVICE=G:\OS2\MDOS\VMOUSE.SYS
DEVICE=G:\OS2\MDOS\VCOM.SYS
DEVICE=G:\OS2\MDOS\VMGAX64.SYS
DEVICE=G:\OS2\MDOS\VVGA.SYS
DEVICE=G:\MGA\OS2\KMGAX64.SYS
DEVICE=G:\MMOS2\SSMDD.SYS
DEVICE=G:\MMOS2\R0STUB.SYS
DEVICE=G:\MMOS2\MIDI.SYS
DEVICE=G:\MMOS2\VCSHDD.SYS
DEVICE=G:\MPTN\PROTOCOL\SOCKETS.SYS
DEVICE=G:\MPTN\PROTOCOL\AFOS2.SYS
DEVICE=G:\MPTN\PROTOCOL\AFINET.SYS
DEVICE=G:\MPTN\BIN\VDOSTCP.VDD
RUN=G:\MPTN\BIN\CNTRL.EXE
RUN=G:\MPTN\BIN\VDOSCTL.EXE
DEVICE=G:\IBMLAN\NETPROG\RDRHELP.200
DEVICE=G:\IBMLAN\NETPROG\VNETAPI.OS2
DEVICE=H:\FaxWorks\Fmd.sys L
Here is how the BIOS boot initialisatiom looks:-
Onboard USB Controller = IRQ 15
Slot 2 - SCSI = IRQ 5
Slot 3 - Multimedia Device = IRQ 9
AGP VGA = IRQ 9
Slot 4 - Ethernet = IRQ 10
Slot 5 - SCSI = IRQ 10
The system reckons:-
RMVIEW: Physical view
IRQ Level = 0 PCI Pin = NONE Flg = EXCLUSIVE
TIMER_CH_0
IRQ Level = 1 PCI Pin = NONE Flg = EXCLUSIVE KBD_0
Keyboard Controller
IRQ Level = 2 PCI Pin = NONE Flg = EXCLUSIVE PIC_1
IRQ Level = 3 PCI Pin = NONE Flg = MULTIPLEXED
SERIAL_1 Serial Controller
IRQ Level = 4 PCI Pin = NONE Flg = MULTIPLEXED
SERIAL_0 Serial Controller
IRQ Level = 5 PCI Pin = NONE Flg = SHARED
AIC7870_0 Adaptec AIC7870
IRQ Level = 6 PCI Pin = NONE Flg = MULTIPLEXED
FLOPPY_0 Floppy Controller
IRQ Level = 8 PCI Pin = NONE Flg = EXCLUSIVE RTC
IRQ Level = 12 PCI Pin = NONE Flg = EXCLUSIVE AUX_0
PS/2 Auxiliary Device Controller
Hmmm.... IRQ 9 not listed, though I've no driver installed
nor has sound been configured.
IRQ 10 not listed - this should be the secondary SCSI HA
(BIOS not enabled).
Also the NIC but that also is not configured until I'm
on cable.
RMVIEW: Logical view
Logical Device: LDEV Logical Device Tree
Flg: 0000 Class: ROOT Handle: 00000000
Logical Device: DASD
Flg: 0000 Class: DASD Handle: 00000000
Logical Device: DSKT_0 Diskette Drive
Flg: 0000 Class: DASD Handle: 0XFC5F08E0
System Name = A: Logical DASD Volume
System Flags = 0000
System Name = B: Logical DASD Volume
System Flags = 0000
Logical Device: CDROM
Flg: 0000 Class: CDROM Handle: 00000000
Logical Device: CDROM_0 CD-ROM / CD-RW / DVDs Drive
Flg: 0000 Class: CDROM Handle: 00000000
System Name = M: Logical CD-ROM Volume
System Flags = 0000
Logical Device: CDROM_1 CD-ROM / CD-RW / DVDs Drive
Flg: 0000 Class: CDROM Handle: 00000000
System Name = N: Logical CD-ROM Volume
System Flags = 0000
SERIAL, PARALLEL and TAPE snipped for brevity.
RMVIEW: Driver view
Driver: RESOURCE.SYS - IBM Resource Manager
Vendor: IBM OS/2 Version: 1.1 Date (MDY): 9/17/1994
Flag: STATIC Type-Subtype: SERVICE
Driver: IBMKBD.SYS - IBM Keyboard Device Dependent Driver
Vendor: IBM - OS/2 Version: 1.1 Date (MDY): 8/7/1998
Flag: STATIC Type-Subtype: OS2 - CHAR
Adapter: KBD_0 Keyboard Controller
Device Type: INPUT-KBD Bus/Width: PLANAR 8 BIT
I/O = 0X0060 Len = 1 Flg = SHARED Addr Lines = 16
I/O = 0X0064 Len = 1 Flg = SHARED Addr Lines = 16
IRQ Level = 1 PCI Pin = NONE Flg = EXCLUSIVE
Device: KBD_X Unknown Keyboard Device IO
Hmmmm.... I'll have to look into the keyoard setup
Driver: IBM1FLPY.ADD - IBM Family 1 Floppy Driver
Vendor: IBM OS/2 Version: 1.1 Date (MDY): 9/17/1994
Flag: STATIC Type-Subtype: ADDDM - ADD
Adapter: FLOPPY_0 Floppy Controller
Device Type: MS-FLPY Bus/Width: ISA 8 BIT
IRQ Level = 6 PCI Pin = NONE Flg = MULTIPLEXED
I/O = 0X03F0 Len = 6 Flg = MULTIPLEXED Addr Lines = 16
I/O = 0X03F7 Len = 1 Flg = MULTIPLEXED Addr Lines = 16
DMA Channel = 2 Flg = MULTIPLEXED
Device: DSKT_0 1.44MB Diskette Drive REMOVABLE DISK
Driver: AIC7870.ADD - Adaptec AIC7870 SCSI Adapter Driver
Vendor: IBM - OS/2 Version: 1.1 Date (MDY): 9/6/1994
Flag: STATIC Type-Subtype: ADDDM - ADD
Adapter: AIC7870_0 Adaptec AIC7870
Device Type: MS-SCSI Bus/Width: PCI 32 BIT
I/O = 0XDC00 Len = 16 Flg = EXCLUSIVE Addr Lines = 16
IRQ Level = 5 PCI Pin = NONE Flg = SHARED
Device: DISK_(8,0) IBM OEM DFHSS4E 5454
DISK
Device: DISK_(9,0) IBM OEM DFHSS4E 4343
DISK
Driver: OS2DASD.DMD - OS2DASD OS/2 DASD Device Manager
Vendor: IBM Version: 1.1 Date (MDY): 9/13/1994
Flag: STATIC Type-Subtype: ADDDM - DM
Logical Device: DSKT_0 Diskette Drive
Flg: 0000 Class: DASD Handle: 0XFC5F08E0
System Name = A: Logical DASD Volume
System Flags = 0000
System Name = B: Logical DASD Volume
System Flags = 0000
Driver: OS2ASPI.DMD - Non-Resource manager aware base
device driver
Vendor: Unknown Vendor Version: 1.1 Date (MDY): 9/17/1994
Flag: STATIC Type-Subtype: OS2 -
Driver: OS2SCSI.DMD - Non-Resource manager aware base
device driver
Vendor: Unknown Vendor Version: 1.1 Date (MDY): 9/17/1994
Flag: STATIC Type-Subtype: OS2 -
Driver: JJSCDROM.DMD - Modified CD-ROM / CD-RW / DVDs
Device Manager
Vendor: Takayuki 'January June' Suwa Version: 1.1 Date
(MDY): 3/28/2003
Flag: STATIC Type-Subtype: ADDDM - DM
Logical Device: CDROM_0 CD-ROM / CD-RW / DVDs Drive
Flg: 0000 Class: CDROM Handle: 00000000
System Name = M: Logical CD-ROM Volume
System Flags = 0000
Logical Device: CDROM_1 CD-ROM / CD-RW / DVDs Drive
Flg: 0000 Class: CDROM Handle: 00000000
System Name = N: Logical CD-ROM Volume
System Flags = 0000
Driver: ASPIROUT.SYS - ASPI Router Device Driver (V1.1á10)
Vendor: Paul Ratcliffe Version: 1.1 Date (MDY): 10/9/2005
Flag: STATIC Type-Subtype: OS2 - HELPER
Deleted many in the listing which did not appear to have a
bearing on the issue.
Resource.sys, I notice, is dated 17th September 1994 - I
would have thought
that newer stuff would need a more up-to-date aware
sniffer/manager.
Any thoughts?
--
regards,
Kevin
ivan
a USB stick?
ivan
On Sat, 9 Jul 2011 12:52:18 UTC, "yorkie" <ke...@yorkie.dabsolLL.co.uk>
wrote:
john...@nospam.com.au
>Hi All,
>
>
>Bear with the longish post but I've tried to include as much
>as possible.
>
>
>I'm attempting to backup the system (Warp 4, FP13) to
>upgrade to v4.51.
>
>Plan A is thwarted by the fact that the system will not
>operate the
>CD-Writer correctly. The system is as follows:-
>
>Any thoughts?
>
Yes; it is not immediately clear whether you are using CD-R or CD-RW.
Following my own experience, and the advice of others here, I abandonded CD-RW
and now use only CD-R in the same hardware.
yorkie
wrote:
Ivan,
> Why not just zip uo the boot partition (zip -9rS) and then copy it to
> a USB stick?
The USB package is, hopefully, part of the v4.51 upgrade
disk set.
Until I can install this upgrade I don't have access to USB
unless I
zip it up and transfer the zip file to a FAT 16 drive and
save to CDRW
from there. I presume if zipped with paths it will preserve
the long
file names within the zip structure and Win 98 won't
truncate any.
However, that is not getting me to the nub of the problem of
why
the Warp system is not abling the Writer as it once did.
> > snip <<
--
regards,
Kevin
yorkie
wrote:
> In <Tze205IW65d5-p...@81-174-221-213.pth-as14.dial.plus.net>, "yorkie" <ke...@yorkie.dabsolLL.co.uk> writes:
> > snip <<
> > I'm attempting to backup the system (Warp 4, FP13) to
> > upgrade to v4.51.
> >
> > Plan A is thwarted by the fact that the system will not
> > operate the CD-Writer correctly. The system is as follows:-
>
>
> > Any thoughts?
>
>
> Yes; it is not immediately clear whether you are using CD-R or CD-RW.
>
> Following my own experience, and the advice of others here, I abandonded CD-RW
> and now use only CD-R in the same hardware.
I'm not getting to the point where media is an issue (I
think).
When I select the CDRW dirve icon I'm getting a SYS0039
message.
Meaning the drive is not ready (with a CD-R or CD-RW disc
present).
I believe that one of Warp's drivers - probably a .DMD - is
not taking
control of the device correctly. It seems to me that there
might be a
conflict of ownership with the ASPI layer and the DMD.
--
regards,
Kevin
ivan
The zip file should not have problems, even in DOS, as long as its
name follows the 8.3 convention.
As to why the drive isn't being enabled - could it have died? They
don't last for ever.
Another possibility if your motherboard has an IDE header is to use an
IDE CDRW drive. That would need ASPIROUT.SYS and the Dani drivers but
should work and would do what you want.
ivan
--
yorkie
wrote:
Ivan,
> > > Why not just zip uo the boot partition (zip -9rS) and then copy it to
> > > a USB stick?
> >
> > The USB package is, hopefully, part of the v4.51 upgrade
> > disk set.
> > Until I can install this upgrade I don't have access to USB
> > unless I
> > zip it up and transfer the zip file to a FAT 16 drive and
> > save to CDRW
> > from there. I presume if zipped with paths it will preserve
> > the long
> > file names within the zip structure and Win 98 won't
> > truncate any.
> >
> > However, that is not getting me to the nub of the problem of
> > why
> > the Warp system is not abling the Writer as it once did.
> >
> >
> > > > snip <<
> >
>
> The zip file should not have problems, even in DOS, as long as its
> name follows the 8.3 convention.
Yeah, it might have to come to this. I'll have to do a test
burn under
Win 98 to make sure it's not having seeing problems.
> As to why the drive isn't being enabled - could it have died? They
> don't last for ever.
Tried six others, same result.
> Another possibility if your motherboard has an IDE header is to use an
> IDE CDRW drive. That would need ASPIROUT.SYS and the Dani drivers but
> should work and would do what you want.
Yes it certainly does but it is not ulilised as it is an all
SCSI system.
--
regards,
Kevin
ivan
The only problem you might encounter with win 98 is the size of the CD
- I'm not sure it can cope with the 700 MB CDs.
> > As to why the drive isn't being enabled - could it have died? They
> > don't last for ever.
>
> Tried six others, same result.
>
> > Another possibility if your motherboard has an IDE header is to use an
> > IDE CDRW drive. That would need ASPIROUT.SYS and the Dani drivers but
> > should work and would do what you want.
>
> Yes it certainly does but it is not ulilised as it is an all
> SCSI system.
>
My two servers have 4 SCSI hot swap hard drives each yet the CD is
connected to the IDE header and I've never encountered any problems
with that.
ivan
--
yorkie
< snip >
> > > > > Why not just zip uo the boot partition (zip -9rS) and then copy it to
> > > > > a USB stick?
> > > >
> > > > The USB package is, hopefully, part of the v4.51 upgrade
> > > > disk set.
> > > > Until I can install this upgrade I don't have access to USB
> > > > unless I
> > > > zip it up and transfer the zip file to a FAT 16 drive and
> > > > save to CDRW
> > > > from there. I presume if zipped with paths it will preserve
> > > > the long
> > > > file names within the zip structure and Win 98 won't
> > > > truncate any.
> > > >
> > > > However, that is not getting me to the nub of the problem of
> > > > why
> > > > the Warp system is not abling the Writer as it once did.
> > > >
> > > >
> > > > > > snip <<
> > > >
> > >
> > > The zip file should not have problems, even in DOS, as long as its
> > > name follows the 8.3 convention.
> >
> > Yeah, it might have to come to this. I'll have to do a test
> > burn under> Win 98 to make sure it's not having seeing problems.
> >
>
> The only problem you might encounter with win 98 is the size of the CD
> - I'm not sure it can cope with the 700 MB CDs.
Thanks for that heads up ....... I'll use a 650MB CD.
> > > As to why the drive isn't being enabled - could it have died? They
> > > don't last for ever.
> >
> > Tried six others, same result.
> >
> > > Another possibility if your motherboard has an IDE header is to use an
> > > IDE CDRW drive. That would need ASPIROUT.SYS and the Dani drivers but
> > > should work and would do what you want.
> >
> > Yes it certainly does but it is not ulilised as it is an all
> > SCSI system.
> >
>
> My two servers have 4 SCSI hot swap hard drives each yet the CD is
> connected to the IDE header and I've never encountered any problems
> with that.
Are you saying that you have a SCSI CD-drive on the header
or an IDE?
--
regards,
Kevin
ivan
Sorry, I wasn't as clear as I should have been. We gave up on SCSI
for everything except the hot swap HDs years ago as we couldn't find
any any advantages, in fact price was a distinct disadvantage.
ivan
--
Doug Bissett
<ke...@yorkie.dabsolLL.co.uk> wrote:
> > The only problem you might encounter with win 98 is the size of the CD
> > - I'm not sure it can cope with the 700 MB CDs.
>
> Thanks for that heads up ....... I'll use a 650MB CD.
Well, this appears to be wrong. I just tested my Win98 system (IBM
ThinkPad A22e), and it can use 700MB CDs, with no problem. It can also
use DVDs, so I would doubt if there is a limit, unless the drive
itself can't handle the size for some reason. I didn't test writing to
the CD/DVD.
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
ivan
<dougb007!SP...@telus.net> wrote:
> On Sat, 30 Jul 2011 20:19:49 UTC, "yorkie"
> <ke...@yorkie.dabsolLL.co.uk> wrote:
>
> > > The only problem you might encounter with win 98 is the size of the CD
> > > - I'm not sure it can cope with the 700 MB CDs.
> >
> > Thanks for that heads up ....... I'll use a 650MB CD.
>
> Well, this appears to be wrong. I just tested my Win98 system (IBM
> ThinkPad A22e), and it can use 700MB CDs, with no problem. It can also
> use DVDs, so I would doubt if there is a limit, unless the drive
> itself can't handle the size for some reason. I didn't test writing to
> the CD/DVD.
>
Doug, my statement was not so muvh about reading but more abour
writing CDs. The writing is also very much about the drive as well.
A friend has three computers with win 98 on them and there is no way
he can burn anything over 650MB even if he uses 700MB CDs.
ivan
--
Doug Bissett
Interesting. I must try to find time to test that. Of course, it may
depend on the specific drive, and software, that is being used. I
don't even remember if I have CD writing software installed in Win98.
Doug Bissett
<dougb007!SP...@telus.net> wrote:
> On Mon, 1 Aug 2011 09:22:16 UTC, "ivan" <iva...@free.fr> wrote:
>
> > On Sun, 31 Jul 2011 14:56:23 UTC, "Doug Bissett"
> > <dougb007!SP...@telus.net> wrote:
> >
> > > On Sat, 30 Jul 2011 20:19:49 UTC, "yorkie"
> > > <ke...@yorkie.dabsolLL.co.uk> wrote:
> > >
> > > > > The only problem you might encounter with win 98 is the size of the CD
> > > > > - I'm not sure it can cope with the 700 MB CDs.
> > > >
> > > > Thanks for that heads up ....... I'll use a 650MB CD.
> > >
> > > Well, this appears to be wrong. I just tested my Win98 system (IBM
> > > ThinkPad A22e), and it can use 700MB CDs, with no problem. It can also
> > > use DVDs, so I would doubt if there is a limit, unless the drive
> > > itself can't handle the size for some reason. I didn't test writing to
> > > the CD/DVD.
> > >
> > Doug, my statement was not so muvh about reading but more abour
> > writing CDs. The writing is also very much about the drive as well.
> > A friend has three computers with win 98 on them and there is no way
> > he can burn anything over 650MB even if he uses 700MB CDs.
> >
> > ivan
>
> Interesting. I must try to find time to test that. Of course, it may
> depend on the specific drive, and software, that is being used. I
> don't even remember if I have CD writing software installed in Win98.
I didn't have any writing software installed in Win98. I use DVDDAO in
eCS, with no problems, or limits. I found ImgBurn, and installed it
(not bad for a windows program). I don't have enough data on that
machine to fill a 700 MB CD, but I was able to write a little over 200
MB to a 700 MB disk. I did notice something about 650 MB, but it
flashed by so fast, that I don't know what it really said.
The bottom line is, that even if Win98 has some limits, eCS does not.
It has been many years since I used warp4, but I can't see why it
would have a limit. I used IDE drives, and the Dani driver, in those
days. I notice that the OP has SCSI drives, so there may be something
that needs to be updated in the SCSI system.
I am not sure that this helps much, but I don't think that a limit in
Win98 has anything, at all, to do with warp4.
Dave Yeo
> The bottom line is, that even if Win98 has some limits, eCS does not.
> It has been many years since I used warp4, but I can't see why it
> would have a limit. I used IDE drives, and the Dani driver, in those
> days. I notice that the OP has SCSI drives, so there may be something
> that needs to be updated in the SCSI system.
>
> I am not sure that this helps much, but I don't think that a limit in
> Win98 has anything, at all, to do with warp4.
Warp v4.5 (v4+fp15) + DVDDAO handles 700 MB CDR fine, at least with a
relatively new DVD burner
Dave
Dave