-
Posts
6,588 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Cynthia
-
Perhaps at your avatar...
-
Isn't bitsetting already applied in that burn? No, I use original firmware for my Nec's. So that tab is still collecting dust here. Yes, you need modified firmware for +R SL discs to do the bitsetting.
-
Well, there is very little on the internet about your burner and even less about any firmware update. Sorry.
-
In the preferences in DVD Flick I checkmarked the option "Create ISO" and that seems to trigger the burning with ImgBurn. (I guess you need to have ISO files associated with ImgBurn in the preferences of ImgBurn). Tried to search for firmware for your burner. It seems it's installed in a Compaq or Dell computer. I couldn't find any firmware for that burner. If it's a Compaq/Dell computer - try to see if you have any luck with using their support pages for your specific model of computer.
-
Suggest that you try to play the burned DVD in another stand alone player. It could be that the player is tricky with burned discs. Tried to find some reviews about your player - there are two models that fit your description: http://www.videohelp.com/dvdplayers?DVDnam...ame&hits=50 (Scroll down a bit on that page to find the two models)
-
Yes, the latest log looks ok. Can you play that DVD in your computer? Never tried DVD Flick before - so I tried it and it seems that the latest version just tried to burn the created stuff to ImgBurn by itself.
-
If you are going to burn those DVD files as a compliant DVD to be played on your player - this is your problem: E 13:28:31 Fix VTS Sectors Failed! - Reason: Could not find VIDEO_TS.IFO That file triggers the player to start the play - so without that one - no go. In the folder you got from the creat
-
Yes, my problems with my Pioneer 110D also started with that it couldn't read the disc it just previously had burned. Then after some days - also the burning went wrong. Even if it still can burn and read CDs.
-
That media is rated 8x but your burner can only see it as max 4x. It's a rather old burner so I would suggest that you get a new one - they are cheap today. It's just odd that it happend after you upgraded to the new version. But I also have a Pioneer that I know is broken and it shows the same burning problem as you are facing.
-
Try this. Start ImgBurn. Go to Main Menu -> Help -> ImgBurn Logs That should show you if there are any logs.
-
I've used TDK for a long time and no problems with these. RICOHJPN-R03-04 Supported Write Speeds: 4x; 6x; 8x; 12x; 16x TDK-003-00 Supported Write Speeds: 4x; 6x; 8x; 12x; 16x; 18x
-
Can you post the log from you burning attempt? You will find it here: Main Menu -> Help -> ImgBurn Logs
-
Perhaps an added toolbar/plugin?
-
(Todays first posted post is edited) It works during the "disappearing time" in about 35-40% of the CPU. This computer is an old Intel Q6600 Pentium Core2Quad (2.4GHz).
-
Only shows up in the 'Processes' tab. When that command is issued only an empty play back window shows up. More or less as you had started the .exe on its own. Edit: Did a new test. This time using the function "Open with" and then selecting the preview.exe. It takes ages to get it to start up and play the cell. But it plays it. It will start faster if I change the process priority to highest or realtime. But still takes up to a minute to get it to play/show up.
-
Checked with PgcEdit and there are wrong time maps in my test files. Ran the fix - but the only change was that the LBA was changed but other than that - the window looked the same and the preview took ages to start.
-
This is how the file source shows up in PgcEdit.
-
Do you need the IFO files?
-
I got the same problem here. But the preview window showed up after around 45 seconds after hitting the red cross thing in the upper right corner. Always worked before. I'm on Vista. Edit: It takes around 25 seconds before the preview window shows up. Before it came up faster than Speedy Gonzales. My ISO file is created in ImgBurn. Edit II: One attempt resulted that after 10 minutes I had to kill the process/program. The thing we seems to have in common is that the "Start time" is zero in both ours cases. The ISO is from an episodic DVD. Tried to create the ISO from another program - but that gave me this window when I tried to load the ISO in the option "Main Menu -> IFO Layer Break Info".
-
Hi and welcome to the forum, wrboone! If you open up Windows task manager (control panel -> system) - can you see the burner in there? If it shows up - try to do this: In the device manager - right click on the device and select the "Uninstall" option. Restart the computer.
-
These discs are also sold in Sweden under the name XB/Aone and are pretty cheap. They cost 40% of what a Verbatim DL disc costs. But it's not only the price that is below Verbatim standard - so are also the burning results. They depend very much upon the burner you have. Here is a translated list based on various burnings posted in a swedish forum: The scannings (quality %) are done in a BenQ DW1640 BSRB at 8x speed with Nero CD-DVD Speed. http://www.sweburn.com/forum/viewtopic.php?t=9
-
Hi and welcome to the forum, cheryl! I remember from the past that you had to "finalize" the discs from such a stand alone DVD recorder for certain programs to be able to read them. Could that be the problem? If you insert the disc from the VHS tapes in your PC and try to play them in the PC - does that work?
-
Hi and welcome to the forum, TKG! Your burner don't like the brand of disc you are trying to burn with. Post the log from the latest adventure (if you don't see the log during the burning - hit the "L" key on the keyboard to show it). The latest log are also saved on your hard disk. You can see them/find them in the main menu under "Help" -> "ImgBurn Logs". Post the latest one in a posting window here. It will/could give a clue on why they don't like each other. Edit: I'm slow as usually with the typing and/or I type to much...
-
Hi and welcome to the forum, sono! ImgBurn has never been able to read protected discs. It's also a subject we can't discuss in this forum. Sorry.