Log in

View Full Version : IC7>PDITool>VIDEO_TS>Record Now Max burn error.


Doggiedaddy
3rd May 2003, 23:34
IC7>PDITool>VIDEO_TS>Record Now Max burn error.

Greetings all,
I hope this had not already been said and done. I did a search and found no information on it, long story short as possible. I do not know the exact chain of events that caused the problem to raise its head. I had a major machine failure on one machine and had to do a complete rebuild [figuratively speaking/full clean re-install]. Around the same time I patched IC7 and the only way I could get PDITool to re-install properly was to use the installer provided by schlaufer and WPELLE from doom. PDITool seems to operate as designed compiling the files.
Any way the problem is now when I use PDITool on the IC7 [.pdi] files and creates a VIDEO_TS directory and attempt to burn with RNM, I receive an error every time. Now if I create an ISO with the same [.pdi] files instead, all goes fine burns complete and plays fine no problems. I was just curious if anyone has seen this problem. There is, as I said, a work around but I always burned in data mode in the past and can not seem to put my finger on the fix or cause?
Dd

Noteworthy: The VIDEO_TS procedure was the chosen method I used up until these errors started to occur. Yes I do also use an empty AUDIO_TS folder.
PS: I tried to go back to previous version of IC7 and I still had the problem.
Thanks

Machine in question
AMD 2400 [MSI MoBo and Video card with bells, whistle and raid]
Pioneer DVR-105
IC7 7.0.1.119
PDITool 0.7
RNM 4.5.0.0

I hope different multiURLs are not considered cross posting? LOL only2me

mpucoder
4th May 2003, 01:19
What error do you receive? Is is a particular error message from RNM, or just a DVD that won't play?

I use RNM myself, and on certain OS's you have to enable "allow all uppercase names" for it to work easily. Otherwise you must re-type the folder name in RNM as VIDEO_TS, even though it appears red (meaning it knows it's DVD-Video). You might have done this in the past, and now it's back to default behavior.

Doggiedaddy
4th May 2003, 07:52
mpucoder thanks for the input,
I am still working on the problem and have not yet completely solved it. I do however now think it has to do with the IC7 patch and the fact I am running DLA on the system. I know a lot of people have problems with DLA but until now it has worked flawlessly for me on a number of machines, regardless of IC7 or not. The problem has to revolve around the new version of IC7 patch. After a couple of changes I am now getting a driver conflict error from IC7 asking to change my settings. By the number of replies, this must be an isolated event with a low impact. I will get it fixed probable a DLA/IC7 thing so thanks for the input mpucoder.

Peace Out
Dd:D

fubarduck
6th May 2003, 03:16
I think I had the same problem once. Try doing a GET VTS SECTORS on it with IFOEdit and see if that changes anything. Simple, but worth trying.

fubarduck