Liteon 5224S - Not enough butter in my fridge for all this toast!!!!!

I have been having a problem burning CDs for a few weeks now. I have tried
several different burning utilities and burning several different types of
CD formats. Usually when I boot my system up I can burn ONE CD fine, and
every CD I try after that will fail. I wouldn't mind rebooting after every
CD but sometimes that doesn't work. I have made some recent upgrades to my
system and I don't really know if they had anything to do with it or not.
Anyways here is my system info and the log report I get when trying to
record.


System Information -

-CD/DVD-ROM-
Liteon 52246S with latest Firmware (Master and Only device on Secondary IDE)
AXV CD/DVD-ROM Scsi CdRom Device (Virtual Device)

-Disk Drives-
Maxtor 92732U8 (Windows reports ~25.4 GB, NTFS and FAT32 partitions)
Western Digital WD400BB-00AUA1 (Windows reports ~37.2 GB, Single NTFS)
Both Drives are on Primary IDE channel

-Video-
GeForce2 GTS Pro 32MB AGP

-Recent Upgrades-
ASUS P4C800-E Deluxe
Intel P4C 2.8GHz 800FSB
Antec TruPower TruBlue 480Watt PSU
Generic 256MB DDR Ram
Lian-Li PC6010 Aluminum Case
Coolermaster rounded/sheilded IDE and FDD cables
Coolermaster Aluminum CD-ROM Bezel

-Operating System-
Windows XP, service packs and updates as needed
Latest ASPI from Adaptec

Alcohol Burning Util Error Log -

22:00:25 Processor info: Intel(R) Pentium(R) 4 CPU 2.80GHz x 2 (2940MHz)
22:00:25 Memory Available to Windows: 260,844 KB
22:00:25 Memory Buffer size: 80 MB
Recording Options: Use Overburning technology
22:00:26 Image file loading:
E:\INCOMING\NBPRO\alt.binaries.comp\09.15.03.Pxxxx xs.Of.The.Cxxxxxxn.DVDSCR.
SVCD-TCF\tcf-potcb.cue
22:00:26 Source Info: Session: 1, Track: 2, Length: 701.6 MB / 079:49:59
22:00:30 (F LITE-ON LTR-52246S (1:0): Recording Method/Speed
22:00:30 Recording - DAO / SAO - 32X (4800 KB/Sec)
22:00:30 (F LITE-ON LTR-52246S (1:0): BURN-Free activated
22:03:36 (F LITE-ON LTR-52246S (1:0) - [Write PREGAP area ERROR]: -150 - 0
S:KEY - 06/28/00 - "Not Ready To Ready Change, Medium May Have Changed"
22:03:36 (F LITE-ON LTR-52246S (1:0): Recording failed!
22:03:36 Error message: [06/28/00] - Not Ready To Ready Change, Medium May
Have Changed
22:03:36 (F LITE-ON LTR-52246S (1:0): Recording failed!
22:03:36 Image file loading aborted!
22:03:39 Something is wrong with the recording procedure!
Please check the log file and report any errors to Technical Support.

End Log -

I have tried DAO, TAO, caching, no-caching, audio, several image formats in
many diff programs.

Any Ideas? System runs pretty clean with 23 processes in task manager. One
thing I notice though, the "commit charge" section of task manager will
continually rise until I reboot. After bootup, commit charge is roughy
122MB/771MB but as time goes with all the same stuff running it will climb.
I haven't watched it a whole lot, but I've seen it as high as 180MB/771MB
with the same amount of processes.

TIA - uncooked

Sounds like a loose wire. Pull case apart and check.

"uncooked meat prior to state vector collapse" wrote in
message news:1kQcb.24181$Ms2.17167@fed1read03...
I have been having a problem burning CDs for a few weeks now. I have tried
several different burning utilities and burning several different types of
CD formats. Usually when I boot my system up I can burn ONE CD fine, and
every CD I try after that will fail. I wouldn't mind rebooting after every
CD but sometimes that doesn't work. I have made some recent upgrades to my
system and I don't really know if they had anything to do with it or not.
Anyways here is my system info and the log report I get when trying to
record.


System Information -

-CD/DVD-ROM-
Liteon 52246S with latest Firmware (Master and Only device on Secondary
IDE)
AXV CD/DVD-ROM Scsi CdRom Device (Virtual Device)

-Disk Drives-
Maxtor 92732U8 (Windows reports ~25.4 GB, NTFS and FAT32 partitions)
Western Digital WD400BB-00AUA1 (Windows reports ~37.2 GB, Single NTFS)
Both Drives are on Primary IDE channel

-Video-
GeForce2 GTS Pro 32MB AGP

-Recent Upgrades-
ASUS P4C800-E Deluxe
Intel P4C 2.8GHz 800FSB
Antec TruPower TruBlue 480Watt PSU
Generic 256MB DDR Ram
Lian-Li PC6010 Aluminum Case
Coolermaster rounded/sheilded IDE and FDD cables
Coolermaster Aluminum CD-ROM Bezel

-Operating System-
Windows XP, service packs and updates as needed
Latest ASPI from Adaptec

Alcohol Burning Util Error Log -

22:00:25 Processor info: Intel(R) Pentium(R) 4 CPU 2.80GHz x 2 (2940MHz)
22:00:25 Memory Available to Windows: 260,844 KB
22:00:25 Memory Buffer size: 80 MB
Recording Options: Use Overburning technology
22:00:26 Image file loading:

E:\INCOMING\NBPRO\alt.binaries.comp\09.15.03.Pxxxx xs.Of.The.Cxxxxxxn.DVDSCR.
SVCD-TCF\tcf-potcb.cue
22:00:26 Source Info: Session: 1, Track: 2, Length: 701.6 MB / 079:49:59
22:00:30 (F LITE-ON LTR-52246S (1:0): Recording Method/Speed
22:00:30 Recording - DAO / SAO - 32X (4800 KB/Sec)
22:00:30 (F LITE-ON LTR-52246S (1:0): BURN-Free activated
22:03:36 (F LITE-ON LTR-52246S (1:0) - [Write PREGAP area ERROR]: -150 -
0
S:KEY - 06/28/00 - "Not Ready To Ready Change, Medium May Have
Changed"
22:03:36 (F LITE-ON LTR-52246S (1:0): Recording failed!
22:03:36 Error message: [06/28/00] - Not Ready To Ready Change, Medium
May
Have Changed
22:03:36 (F LITE-ON LTR-52246S (1:0): Recording failed!
22:03:36 Image file loading aborted!
22:03:39 Something is wrong with the recording procedure!
Please check the log file and report any errors to Technical Support.

End Log -

I have tried DAO, TAO, caching, no-caching, audio, several image formats
in
many diff programs.

Any Ideas? System runs pretty clean with 23 processes in task manager. One
thing I notice though, the "commit charge" section of task manager will
continually rise until I reboot. After bootup, commit charge is roughy
122MB/771MB but as time goes with all the same stuff running it will
climb.
I haven't watched it a whole lot, but I've seen it as high as 180MB/771MB
with the same amount of processes.

TIA - uncooked

"uncooked meat prior to state vector collapse" wrote in
message news:1kQcb.24181$Ms2.17167@fed1read03...
I have been having a problem burning CDs for a few weeks now. I have tried
several different burning utilities and burning several different types of
CD formats. Usually when I boot my system up I can burn ONE CD fine, and
every CD I try after that will fail. I wouldn't mind rebooting after every
CD but sometimes that doesn't work. I have made some recent upgrades to my
system and I don't really know if they had anything to do with it or not.
Anyways here is my system info and the log report I get when trying to
record.


System Information -

-CD/DVD-ROM-
Liteon 52246S with latest Firmware (Master and Only device on Secondary
IDE)
AXV CD/DVD-ROM Scsi CdRom Device (Virtual Device)

-Disk Drives-
Maxtor 92732U8 (Windows reports ~25.4 GB, NTFS and FAT32 partitions)
Western Digital WD400BB-00AUA1 (Windows reports ~37.2 GB, Single NTFS)
Both Drives are on Primary IDE channel

-Video-
GeForce2 GTS Pro 32MB AGP

-Recent Upgrades-
ASUS P4C800-E Deluxe
Intel P4C 2.8GHz 800FSB
Antec TruPower TruBlue 480Watt PSU
Generic 256MB DDR Ram
Lian-Li PC6010 Aluminum Case
Coolermaster rounded/sheilded IDE and FDD cables
Coolermaster Aluminum CD-ROM Bezel

-Operating System-
Windows XP, service packs and updates as needed
Latest ASPI from Adaptec

Alcohol Burning Util Error Log -

22:00:25 Processor info: Intel(R) Pentium(R) 4 CPU 2.80GHz x 2 (2940MHz)
22:00:25 Memory Available to Windows: 260,844 KB
22:00:25 Memory Buffer size: 80 MB
Recording Options: Use Overburning technology
22:00:26 Image file loading:

E:\INCOMING\NBPRO\alt.binaries.comp\09.15.03.Pxxxx xs.Of.The.Cxxxxxxn.DVDSCR.
SVCD-TCF\tcf-potcb.cue
22:00:26 Source Info: Session: 1, Track: 2, Length: 701.6 MB / 079:49:59
22:00:30 (F LITE-ON LTR-52246S (1:0): Recording Method/Speed
22:00:30 Recording - DAO / SAO - 32X (4800 KB/Sec)
22:00:30 (F LITE-ON LTR-52246S (1:0): BURN-Free activated
22:03:36 (F LITE-ON LTR-52246S (1:0) - [Write PREGAP area ERROR]: -150 -
0
S:KEY - 06/28/00 - "Not Ready To Ready Change, Medium May Have
Changed"
22:03:36 (F LITE-ON LTR-52246S (1:0): Recording failed!
22:03:36 Error message: [06/28/00] - Not Ready To Ready Change, Medium
May
Have Changed
22:03:36 (F LITE-ON LTR-52246S (1:0): Recording failed!
22:03:36 Image file loading aborted!
22:03:39 Something is wrong with the recording procedure!
Please check the log file and report any errors to Technical Support.

End Log -

I have tried DAO, TAO, caching, no-caching, audio, several image formats
in
many diff programs.

Any Ideas? System runs pretty clean with 23 processes in task manager. One
thing I notice though, the "commit charge" section of task manager will
continually rise until I reboot. After bootup, commit charge is roughy
122MB/771MB but as time goes with all the same stuff running it will
climb.
I haven't watched it a whole lot, but I've seen it as high as 180MB/771MB
with the same amount of processes.

TIA - uncooked




i had identical problems on a completely different system with win2k &
pioneer 105 - the solution, as i found the long/hard way & sum1 else
mentioned he'd been told by plextor, do not use aspi with alcohol 120% - use
the built in spti. this is the newer way to do it with ms oses from 2k
onwards, ie reinstall win & do not install aspi

"Dr Ratt" wrote in message
.. .

"uncooked meat prior to state vector collapse" wrote in
message news:1kQcb.24181$Ms2.17167@fed1read03...
I have been having a problem burning CDs for a few weeks now. I have
tried
several different burning utilities and burning several different types
of
CD formats. Usually when I boot my system up I can burn ONE CD fine, and
every CD I try after that will fail. I wouldn't mind rebooting after
every
CD but sometimes that doesn't work. I have made some recent upgrades to
my
system and I don't really know if they had anything to do with it or
not.
Anyways here is my system info and the log report I get when trying to
record.




i had identical problems on a completely different system with win2k &
pioneer 105 - the solution, as i found the long/hard way & sum1 else
mentioned he'd been told by plextor, do not use aspi with alcohol 120% -
use
the built in spti. this is the newer way to do it with ms oses from 2k
onwards, ie reinstall win & do not install aspi



Just to be clear here, you were able to burn some CDs but most times it
failed? And same results using different burning programs? Thanks for the
advice, luckily I keep a spare partition for things like this so I'll give
it a try. And as Tj suggested I have checked my cables and replaced them
just incase they were bad.

Checked your drive's DMA settings...?

Also; the only ASPI you want is v 4.6; not the 4.7

Try a Feurio install so the system checker module has a look at your
setup; it runs auto on install. I don't know if it supports your drive
(probably) but I expect it will still do the look over. Free
unrestricted demo at:

www.feurio.com


Tim K

"uncooked meat prior to state vector collapse" wrote in
message news:gu7db.27834$Ms2.19100@fed1read03...

"Dr Ratt" wrote in message
.. .

"uncooked meat prior to state vector collapse" wrote
in
message news:1kQcb.24181$Ms2.17167@fed1read03...
I have been having a problem burning CDs for a few weeks now. I
have
tried
several different burning utilities and burning several different
types
of
CD formats. Usually when I boot my system up I can burn ONE CD
fine, and
every CD I try after that will fail. I wouldn't mind rebooting
after
every
CD but sometimes that doesn't work. I have made some recent
upgrades to
my
system and I don't really know if they had anything to do with it
or
not.
Anyways here is my system info and the log report I get when
trying to
record.




i had identical problems on a completely different system with win2k
&
pioneer 105 - the solution, as i found the long/hard way & sum1 else
mentioned he'd been told by plextor, do not use aspi with alcohol
120% -
use
the built in spti. this is the newer way to do it with ms oses from
2k
onwards, ie reinstall win & do not install aspi



Just to be clear here, you were able to burn some CDs but most times
it
failed? And same results using different burning programs? Thanks for
the
advice, luckily I keep a spare partition for things like this so I'll
give
it a try. And as Tj suggested I have checked my cables and replaced
them
just incase they were bad.

"Tim Kroesen" wrote in message
...

Checked your drive's DMA settings...?

Primary IDE (HDD's) Mode 4 and Mode 5 currently
Secondary IDE (CDR/W) Mode 2


Also; the only ASPI you want is v 4.6; not the 4.7


Thanks, I'll keep that in mind. I ran ASPICHK and deleted the two files it
listed, as was recommended by way of google on removing ASPI drivers, and it
has *apparently* worked for now. I have burned 4 different image files
successfully since removing those files and using Alcohol with no coasters.
Now my problem is that my 52x CD-R speed will only burn at 12x w/burn-proof
enabled, and takes up to 5 minutes to start putting files on the media after
starting the burn process. So my true speed after factoring the long wait at
the beginning is ~8x-9x. I have had this problem before and dont remember
what I did to fix it, but sometimes when I fix it, I can burn at up-to 32x
and higher. I'm curious if the small 256MB system memory chip is playing a
part in this. I just cant afford the memory I really want so I got something
to get me running in the meantime. grrrr.

Try a Feurio install so the system checker module has a look at your
setup; it runs auto on install. I don't know if it supports your drive
(probably) but I expect it will still do the look over. Free
unrestricted demo at:

www.feurio.com

Thanks for the link. I ran it and first thing it said it wanted to turn off
autorun, which I agreed to. The system diagnosis looks ok, I guess... Lot of
unknown drivers and the rest were OK or OFF. Of the unknown drivers I
noticed Padus has an ASPI shell driver installed. I turned it off and I
guess that means I can't use DiscJuggler anymore, but no worries there.


Tim K

uncooked meat prior to state vector collapse

"uncooked meat prior to state vector collapse" wrote in
message news:1L9db.27855$Ms2.20937@fed1read03...

"Tim Kroesen" wrote in message
...

Checked your drive's DMA settings...?

Primary IDE (HDD's) Mode 4 and Mode 5 currently
Secondary IDE (CDR/W) Mode 2



Check in Device Manager to see if "DMA" is enabled/disabled. If disabled
then enable and reboot to see if it will help.


--
callsignviper

The truth is out there. You just have to look in the right places and ask
the right questions.

"callsignviper" wrote in message
. net...

"uncooked meat prior to state vector collapse" wrote in
message news:1L9db.27855$Ms2.20937@fed1read03...

"Tim Kroesen" wrote in message
...

Checked your drive's DMA settings...?

Primary IDE (HDD's) Mode 4 and Mode 5 currently
Secondary IDE (CDR/W) Mode 2



Check in Device Manager to see if "DMA" is enabled/disabled. If disabled
then enable and reboot to see if it will help.

Yes it was enabled. Thanks guys for your advice, the problem was never
solved, but I learned plenty by reading the group and visiting some web
resources. I managed to fix the problem on my own by purchasing a Lite-On
52327S. Not a single problem and I'm burning discs faster than I can mark
the last one with a sharpie (sloppy labeling system). Thanks again.

Had exactly the same problems with my Samsung SW-252B, XP Home and Nero and
WOCD:

My solution after a long way of "investigation":

Deinstall Intel Application Accelerator 2.3
Install Standard IDE-ATA Drivers for Windows XP instead of the Intel Chipset
Drivers


"uncooked meat prior to state vector collapse" schrieb im
Newsbeitrag news:1kQcb.24181$Ms2.17167@fed1read03...
I have been having a problem burning CDs for a few weeks now. I have tried
several different burning utilities and burning several different types of
CD formats. Usually when I boot my system up I can burn ONE CD fine, and
every CD I try after that will fail. I wouldn't mind rebooting after every
CD but sometimes that doesn't work. I have made some recent upgrades to my
system and I don't really know if they had anything to do with it or not.
Anyways here is my system info and the log report I get when trying to
record.