Got an Epox NForce2 board? Nero locking you up? I have THE solution! (really)

[mechBgon]

Well obviously the software is gagging at the sight of a Michael Jackson song on your playlist

Ok, just kidding... but I don't know what else to suggest aside from reinstalling Service Pack 3 perhaps. There is a 5.5.10.7b patch at ahead.de but I expect you have that already. Well, and you appear not to have cacheing enabled for the files, too.

 

[IPLaw]

Thanks for your replies! I'll have to work on it some more tomorrow. If there is no solution, its back to VIA!

 

[IPLaw]

Update to my problem:

When I selected PIO mode for the CDR channel, the drive is correctly detected and runs perfectly (albeit at 100% cpu usage).
When I select DMA mode for the CDR channel, the drive read and write speed, as well as the internal buffer size, is incorrectly detected, and will not burn a CD. I tried chaning channels, IDE cabels, BIOS settings (tried PIO, DMA, PCI latency, etc), to no avail. Seems it may be a bios related issue (either my abit bios, tdk bios, or the combination). The CDR works perfectly, in DMA mode, on other W2K systems using the sis 735 and via kt400 chipsets. Strange!

 

[Oric]

Originally posted by: IPLaw
Update to my problem:

When I selected PIO mode for the CDR channel, the drive is correctly detected and runs perfectly (albeit at 100% cpu usage).
When I select DMA mode for the CDR channel, the drive read and write speed, as well as the internal buffer size, is incorrectly detected, and will not burn a CD. I tried chaning channels, IDE cabels, BIOS settings (tried PIO, DMA, PCI latency, etc), to no avail. Seems it may be a bios related issue (either my abit bios, tdk bios, or the combination). The CDR works perfectly, in DMA mode, on other W2K systems using the sis 735 and via kt400 chipsets. Strange!

I have A7N8X Deluxe and a Philips CDRW48P Cd Writer (IDE) ... I can not burn disks ... The binaries are corrupted. I have updated Nero to latest version .. I will try to disable Auto Insert Notification as the last move because I have tried all combinations of master/slave/bios/driver etc and I have made approx 30 coaster CD so far ...

 

[IPLaw]

Oric

Does your drive have some type of burnproof technology? While I can burn in PIO mode, Nero shows that the internal buffer constantly drops down to zero, such that if my TDK did not have burnproof (it does), I am sure every disk would be coaster. What OS are you using, and what's your CPU usage while your burn? High CPU usage is a good sign that you are stuck in PIO mode. If your drive is in PIO mode, make sure that DMA is enabled in the system properties.

 

[Oric]

Originally posted by: IPLaw
Oric

Does your drive have some type of burnproof technology? While I can burn in PIO mode, Nero shows that the internal buffer constantly drops down to zero, such that if my TDK did not have burnproof (it does), I am sure every disk would be coaster. What OS are you using, and what's your CPU usage while your burn? High CPU usage is a good sign that you are stuck in PIO mode. If your drive is in PIO mode, make sure that DMA is enabled in the system properties.

I can burn CDs in PIO mode because the drive HAS burnproof technology.

If I switch to DMA mode I can still burn disks but Nero can not verify them, if burn a MPEG file and try to watch that on media player I see "artifacts" meaning parts of the files are corrupted. -> They are coasters

If I try to back up other data they are corrupted -> coasters ...

HOW I will use this drive in DMA mode is a question I am seeking an answer to ..

 

[IPLaw]

Sounds like we have the same problem. Are you using W2K?

 

[Oric]

I use Win XP SP1 with Asus 1.16 (Equivalent to NVidia 2.03 driver pack) drivers

IBM UATA 100 Primary Master
Pioneer DVD 116 Primary Slave
Philips CDRW4816P Secondary Master
Athlon XP2000+
256 MB PC2700 RAM

 

[IPLaw]

As a quick fix, I am going to install my CDR on a separate Promise IDE controller card. I've run CDR's and HDD's off of the card before in DMA mode, so hopefully it will provide a temporary fix. They are available for about $35 from newegg.

 

[mechBgon]

Have you tried swapping the CDR between Master and Slave? Some people have used this to resolve DMA/PIO problems, could be worth a try.

 

[microAmp]

Good to see you get it fixed. It should also be a note to all, when ever doing a fresh format, ALWAYS get the latest patches & drivers for everything you install. I made a good habit out of that.

 

[IPLaw]

Fixed!!!

There is an undocumented and unused jumper on the back of my TDK that forces the drive into DMA mode (I had to search like heck to find it). Under the system settings, the drive now either operates in PIO or UDMA instead of PIO or DMA mode before. Nero and EZCD work perfectly - the drive properties are read correctly, and Nero burns with 2% CPU usage now. I hope it stays this way!

 

[Oric]

IPLaw,

Where is that jumper ? I have a Philips so I doubt I have the exact duplicate solution that you found ...

Anyway, disabling auto insert notifaction did not solve my pronlem. I am still stuck at PIO mode, switching to DMA still produces coasters for me ...

 

[IPLaw]

It was a single 2-pin jumper on the back left of the drive. It seems that the problem affects more than a few people. Also, make sure you have the latest firmware for your drive.

I've used just about every VIA board and experienced every VIA related problem. I never had such a basic malfunction on a VIA board as I did here.

 

[Oric]

I found a post in CD Freaks forum (The post was in last november), a guy with the same model Philips drive seems to have the exact problem when he switched to SP1. (Well me 2 !) He solved his problem by jumpering his drive to cable select instead of master !!!

I will try this soution tonite. I hope it works !

 

[IPLaw]

Let us know how it works!

 

[MichaelD]

IPLAW, congratulations!!! You've found another fix for this board/software combo. I'm gonna PM Andy and see what he says about putting this is in the FAQ.

 

[ScrapSilicon]

Originally posted by: MichaelD
IPLAW, congratulations!!! You've found another fix for this board/software combo. I'm gonna PM Andy and see what he says about putting this is in the FAQ.

how is the following mobo/software related ..?

Originally posted by: IPLaw
Fixed!!!

There is an undocumented and unused jumper on the back of my TDK that forces the drive into DMA mode (I had to search like heck to find it). Under the system settings, the drive now either operates in PIO or UDMA instead of PIO or DMA mode before. Nero and EZCD work perfectly - the drive properties are read correctly, and Nero burns with 2% CPU usage now. I hope it stays this way!

 

[MichaelD]

Originally posted by: ScrapSilicon

Originally posted by: MichaelD
IPLAW, congratulations!!! You've found another fix for this board/software combo. I'm gonna PM Andy and see what he says about putting this is in the FAQ.

how is the following mobo/software related ..?

Originally posted by: IPLaw
Fixed!!!

There is an undocumented and unused jumper on the back of my TDK that forces the drive into DMA mode (I had to search like heck to find it). Under the system settings, the drive now either operates in PIO or UDMA instead of PIO or DMA mode before. Nero and EZCD work perfectly - the drive properties are read correctly, and Nero burns with 2% CPU usage now. I hope it stays this way!

Well, let's see here. A motherboard is a piece of hardware and Nero is a piece of software. In this case, when attempting to use them together, it is a hardware/software related issue.

Is that simple enough for you, or do you need flash cards?

 

[PrinceXizor]

Call me a noob, but isn't your reference to "TDK" a reference to your burner....so how is adjusting a jumper on your burner a mb/sw issue?

 

[Electric Amish]

Hmm... Just burned some stuff on my 8RDA and Lite-on burner the other day with no problems. Using the NERO that came with my Lite-on

amish

 

[IPLaw]

PrinceXizor:
Just about every mobo related forum on the net has postings concerning burner / nforce2 problems. Some of these are solved by the newest nforce2 drivers, some not. Some are solved by using newer versions of nero, some older versions, and some not. Some refuse to work in DMA mode, some not. Some crash, some produce coasters. In many cases, the burners being used are verified to work on non-nforce boards. Similar issues arise under W98, W2k, and WXP. If someone can tell me the root of the issue; i.e. whether it is a driver, board, OS, burner firmware problem, chipset, etc or any combinations thereof, please tell us. I don't claim to fully understand the root of the issue - all I know is what worked in my situation, and what has worked for others.

That being said, considering the experiences of others, burners are apparently not able to properly communicate with, or function with, nforce2 boards running different MS operating systems. Given this fact, it seems likely that the problem is low level, possibly a board bios or OS level (perhaps IDE) driver issue, when used in combination with burners from different manufactuers.

Then again, I am frequently wrong. All I know is that my solution works for me and might be of help to others.

 

[ScrapSilicon]

Originally posted by: MichaelD

Originally posted by: ScrapSilicon

Originally posted by: MichaelD
IPLAW, congratulations!!! You've found another fix for this board/software combo. I'm gonna PM Andy and see what he says about putting this is in the FAQ.

how is the following mobo/software related ..?

Originally posted by: IPLaw
Fixed!!!

There is an undocumented and unused jumper on the back of my TDK that forces the drive into DMA mode (I had to search like heck to find it). Under the system settings, the drive now either operates in PIO or UDMA instead of PIO or DMA mode before. Nero and EZCD work perfectly - the drive properties are read correctly, and Nero burns with 2% CPU usage now. I hope it stays this way!

Well, let's see here. A motherboard is a piece of hardware and Nero is a piece of software. In this case, when attempting to use them together, it is a hardware/software related issue.

Is that simple enough for you, or do you need flash cards?

you said it now to strictly and succinctly point it out to anyone reading...jumper on the back of my TDK is not a motherboard and software issue...unless TDK's making said motherboard that the jumper is being moved on to enable UDMA on the TDK burner in his scenario

 

[IPLaw]

ScrapSilicon:

That's what makes problem solving threads great - valuable user input

 

[ScrapSilicon]

Originally posted by: IPLaw
PrinceXizor:
Just about every mobo related forum on the net has postings concerning burner / nforce2 problems. Some of these are solved by the newest nforce2 drivers, some not. Some are solved by using newer versions of nero, some older versions, and some not. Some refuse to work in DMA mode, some not. Some crash, some produce coasters. In many cases, the burners being used are verified to work on non-nforce boards. Similar issues arise under W98, W2k, and WXP. If someone can tell me the root of the issue; i.e. whether it is a driver, board, OS, burner firmware problem, chipset, etc or any combinations thereof, please tell us. I don't claim to fully understand the root of the issue - all I know is what worked in my situation, and what has worked for others.

That being said, considering the experiences of others, burners are apparently not able to properly communicate with, or function with, nforce2 boards running different MS operating systems. Given this fact, it seems likely that the problem is low level, possibly a board bios or OS level (perhaps IDE) driver issue, when used in combination with burners from different manufactuers.

Then again, I am frequently wrong. All I know is that my solution works for me and might be of help to others.

Originally posted by: IPLaw
ScrapSilicon:

That's what makes problem solving threads great - valuable user input

Agreed ..did not know TDK had a UDMA jumper on that CDRW ...