LIGHTNING UK!
-
Posts
30,458 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by LIGHTNING UK!
-
-
Not all players need the LB flag. It's the playing through the LB that causes a problem, I not so sure if 'jumping' (FF / Rewind) over it would do.
PgcEdit insert the LB flag.
PgcEdit just uses the mkisofs file from ImgTool Classic, that's all.
ImgTool Classic itself is never used / called up.
PgcEdit can be told to load ImgBurn and start burning the ISO file. The LB position you select in PgcEdit is passed via a command line parameter to ImgBurn.
Neither of those programs create an MDS file.
-
-
Regarding the burn error, get some different discs that use a different dye.
-
Ok, I'm actually going to add an option to make ImgBurn the default app for the files you've chosen to associate it with.
If it's default, it'll then use my custom made icon.
-
No, both layers don't HAVE to be burnt, it is possible not to burn layer 1 if you only have enough data for layer 0.
You're advised to burn equal amounts to each layer in order to get the best readability. But for testing purposes, who cares about that! lol
-
Nothing can!
The MDS file shouldn't really contain the file path data anyway... please say DVD Dec didn't do that!
Oh, you can of course FORCE it (or ImgBurn) to add path data (within the 'Create DVD MDS File' bit), but that's a different story.
-
My guess is you changed media, moved onto another spindle, updated the drives firmware... something like that.
These errors come from your drive not liking the media very much.
Copy and paste the log you burning so we can see what's going on.
-
Oops, yeah sorry, I'd added a warning to the manual check of the layer break - via Tools -> ISO -> Display IFO Layer Break Information, but I'd left the real burning routine to just revert back to the old method of searching the vob for a nice (ish) place.
I've now added one to the actual burning bit too.
-
Like I said, this is window's doing.
You have to remember you've viewing in thumbnail mode, maybe that's having an effect on things.
My exe has icons in 16x16, 32x32 and 48x48. Windows is just choosing to use the 16x16 one, sticking it within it's own document icon (that's probably 32x32) and then stretching it to 48x48.
If it used the 32x32 one and put it in a 48x48 document icon, it would look ok.
Without forcing a specific icon upon everyone (by making mine default all the time), I can't specify a nicer icon for windows to use.
Forcing mine to be default is not an option at this time.
If you want to do it manaully, I can provide an ICO file and tell you how to do it.
-
Maybe we'll get LFC to do a test.
Have him burn JUST layer 1 and scan it, then burn another disc filling up both layers and scan it.
Then we'll compare the two!
I don't think I've really ever seen a DL burn where only the first layer has been burnt, I suspect most of the scan you've seen are the same chewy - therefore it's probably DL media in general that's not so good as SL media, rather than the scan being bad because the laser has damaged Layer 0 when burning Layer 1.
-
lol try running that by babelfish or google translate
-
I don't think the network is the problem here. Copying files over my lan gives me about 40 - 45mb/s.
I think reading 4 different images off your raid set is just too much random accessing to give you anything higher than ~20mb/s
-
Glad to hear things are looking up
-
lol so that's 4x over a network!
making about 22mb/s if you're doing 4 of them at once.
I don't think that's too bad at all.
-
Seriously, get onto them and tell them that then!
They can't be huge apps or the companies would have already taken care of this issue. And being small, the developers are more likely to listen to the end user.
I've made 2 companies aware of this problem in their apps and they've since fixed it. But I guess we're not using the same programs
-
I dunno but you can't instantly blame the drivers.
There's obviously no real speed issue or it would never have reached 12x in the first place.
People blame Nvidia and Intel drivers way too much.
Who do you think made the first ones that ship with XP or whatever?! Microsoft aren't going to have done it, it's not their place to.
Yes ok, their first few releases may have not been so good but XP has been around for years now and I doubt the drivers still really have problems. Just because they were bad 3 years ago doesn't mean they'll still be bad today.
I run Intels latest chipset + ide/sata drivers (have done forever!) and don't have any problems. Same goes for my AMD machine that's running the Nvidia NForce 4 drivers. That said, it doesn't seem to have installed the PATA side of the 'enhanced' drivers. Those are still registering as standard.
The graph is handy because it can help show the pattern. It could be a perfect stepdown, maybe shamus's G05s aren't up to much, who knows. The WOPC on the pioneer is also pretty aggressive and checks discs more frequently than any other drive I've seen.
-
ctrl+alt+del, task manager -> File -> New Task (run) -> 'explorer.exe' -> ok.
If tray icons don't come back, go moan to the people that make those apps and have them listen to the right messages to capture the fact that explorer has just started and the system tray has just been created.
i.e.
WM_TASKBARCREATED = RegisterWindowMessage("TaskbarCreated");
Then listen for WM_TASKBARCREATED being passed to the application. When it is, recreate the systemtray icon.
-
They just focus the beam onto the different layers.
When burning the second one, it just passes through the first without really having any impact on it.
-
Windows makes that icon, not me.
It just takes the main app icon and sticks it inside a document type image.
I can't really think of a decent one for images so it'll probably stay as-is.
-
lol that's a very open ended question chewy!
It's kinda hard to tell what you were asking for exactly!
If you're on about the SCSI ID address (the [x:x:x] one), yeah, just add some more controllers into your machine!
As for the speed thing, no, that doesn't indicate anything to do with drivers.
You've got a max of 12 and average of 4. To me it looks like it stepped up and stepped down again. Without seeing the write speed graph, it's hard to say - but that's what the graph is there for. That time is about right for a 4x burn though.
-
Tell me what it says in the status bar when you put this disc in. (Also, if you can, copy + paste the info from the panel on the right if it contains more than 2 lines)
If the status bar says 'media not present', the drive isn't initialising the disc properly. There is nothing I can do about that. Eject + relaod it.
Your drive is really a LiteOn, so just use that tab instead for changing the booktype. You should only need to do it once if you use the EEPROM settings.
-
Incidentally, you're the only one on planet earth who even responed to my questions. Thanks for that.
Well I'm the only one who'd know the answer
Going back to your questions....
ImgBurn doesn't create ISO files. It can't read anything. If another program was used that creates proper MDS files, yes the layerbreak position will be retained.
If you reauthor a disc and it's done by a program that's not layerbreak aware (i.e. DVDShrink), you'll be lucky if the ISO it creates will be compliant for DL burning.
The odds of it just happening to start a new cell on a LBA that's a multiple of 16 are pretty slim.
ImgBurn cannot move the files within the ISO so if they're not right in the first place, you're stuck.
In such situations, you're better off writing a video_ts folder and using PgcEdit to create the image.
PgcEdit will ensure the image DOES have a cell that can be flagged as the layerbreak one and it WILL start on a sector (LBA) that's a multiple of 16.
-
No you don't.
-
lol, how can you call my logs strange?!
They're the most straight forward things in the world compared to all the shite Nero outputs!
BIN Files
in ImgBurn Support
Posted
Burning a bin file is ok if it's just a simple image. ImgBurn is clever enough to work out the format of the image and select the appropriate burning methods.
If the bin contains multiple tracks, sessions etc, ImgBurn cannot possibly know this and so it's all just burnt as 1 big session/track.
I couldn't possibly say if it would always work for images you have no cue file for.