Club CDFreaks - Knowledge is Power - View Single Post - PrimoDVD & DRU-500A

Del_Usion · 12-11-2002

Apparently, the PxEngine was interacting badly with one of the other programs that I had running in the tray. I can't be sure if it was FlashFXP, CloneCD Tray, or Daemon tools, but I find it odd that whatever the conflict was that it always killed the write at sector 102016. On a Athlon 1.4 with 512 of ram that shouldn't have been happening in any case unless it was a severe software conflict. Anyway, got it figured out. I'll have to do more testing if I feel ambitious as to which prog might have been causing the problem, but as my version of Daemon Tools hasn't been updated in quite some time I have to wonder if that might be the culprit. One other nifty piece of info I found out while trying to get this running is that the "lite" version of RecordNow that ships with the drive WILL use gi files *if* they've been created in the newer RecordNow format and not the PrimoDVD format. Since the files look identical there are a few quick ways to tell. If you have PrimoDVD and you try loading a gi and it says invalid image, then it's likely a newer version. In RecordNow (lite) when adding files to a data disc and you add a gi if it promts asking about burning the image file it's the new format, if it just loads the file as a file it's an old image (and will only burn that 5k or so file if you try). And lastly, in RecordNow Max if you do an image search all the files of a newer version image will show the filesize of the total image but old image files will only show the total size on the cue gi and the rest will show zero. So, thus concludes my investigation. Like I said, if I get ambitious I may report back the culprit, but don't be surprised if for safety sake I just deal with shutting down everything like it was the old days of cd burning with my 1x on a P200.

12-11-2002	#10 (permalink)
Del_Usion New on Forum Join Date: Jul 2002 Posts: 16	For anyone that still cares.... Apparently, the PxEngine was interacting badly with one of the other programs that I had running in the tray. I can't be sure if it was FlashFXP, CloneCD Tray, or Daemon tools, but I find it odd that whatever the conflict was that it always killed the write at sector 102016. On a Athlon 1.4 with 512 of ram that shouldn't have been happening in any case unless it was a severe software conflict. Anyway, got it figured out. I'll have to do more testing if I feel ambitious as to which prog might have been causing the problem, but as my version of Daemon Tools hasn't been updated in quite some time I have to wonder if that might be the culprit. One other nifty piece of info I found out while trying to get this running is that the "lite" version of RecordNow that ships with the drive WILL use gi files if they've been created in the newer RecordNow format and not the PrimoDVD format. Since the files look identical there are a few quick ways to tell. If you have PrimoDVD and you try loading a gi and it says invalid image, then it's likely a newer version. In RecordNow (lite) when adding files to a data disc and you add a gi if it promts asking about burning the image file it's the new format, if it just loads the file as a file it's an old image (and will only burn that 5k or so file if you try). And lastly, in RecordNow Max if you do an image search all the files of a newer version image will show the filesize of the total image but old image files will only show the total size on the cue gi and the rest will show zero. So, thus concludes my investigation. Like I said, if I get ambitious I may report back the culprit, but don't be surprised if for safety sake I just deal with shutting down everything like it was the old days of cd burning with my 1x on a P200.