weisborg

As for shows that should stick around. I liked Journeyman. Bionic woman was alright, but Journeyman had that Quantum Leap ring to it. I can't even watch the new Enterprise because I keep thinking he is going to leap out any second and it will be a different person. This season I've been mostly watching the new Terminator series and Kyle XY...the a little Smallville sprinkled in. The Terminator series is nice in keeping to the storylines of the movies and filling in the gaps.

The last hour of the 1st episode it got good...the 1st hour was kinda boring. Hopefully the episodes to follow will be better, as the first kinda reminded me of Viper...but instead of Dodge it was a 2 hour Ford commercial. I searched forever and found the font...guess what. Font is Ford Ranger. Viper's font was pretty close too. Wonder how many cameos there will be of The Hoff? I don't care too much for him anymore, but he brings more of the Knight image than Ford logos. So was the new kid's mom supposed to be the lady Michael was to marry before he became Michael Knight? I have every season of the original and I could have swore she was blonde. Guess it doesn't matter much since they killed her off as a way to bring The Hoff on scene and giving the kid a reason for "One man to make a difference".

Looks good to me. I always like knowing what's going on. My Windows DVD does all kinds of stuff, so if anything I'd like to modify what settings I can in the app and in the Project file to match where they apply. I think most of those settings I already had. Main thing is as long as I don't lose long filenames with any changes...other than that I'm good as long as it works.

I was getting this warning now and decided to search before making a new thread. My Slipstreamed Windows DVD gives this warning now. It gives it in the calculate mode too, but when looking at the settings after clicking Yes it doesn't appear to have changed anything. Still gives the warning when burning too, so didn't appear to do anything. Is that the bug, or is there more? It would be nice if it told what it is finding wrong and what it is going to change too...what is it looking at anyway?

Why not just make that one file a Readme.txt file saying the disc is only a boot disc? Might as well make use of of the hundreds of MB of wasted disc... Other than that, I'm guessing there must be some type of structure on the disc for it to be recognized as a disc. A bootable disc does need to be an ISO disc, so most likely needs at least the layout of that filetype.

Must have never noticed this thread until someone posted to it again... Open Source is usually a graveyard for applications...especially when they have already started and are being used without it. Once there the author has no control over all the garbage it can become, and he really doesn't make any money. Kinda harsh saying he doesn't make money as it is...he may not be rich, but it looks like he is good enough to keep going no matter what so far. Heck as soon as this next version is out and everything works cool, I myself will be donating. It already does more than Nero in the way of burning. A couple fixes are really all I'm waiting on. The audio CD stuff sounds kinda cool too. If it adds audio extraction from CD to Wav/Mp3 it would be all the "cooler"...if that is a word. The original poster was kinda funny too. Out of everything the app does he thought a log window with a listview and some snap-to code was the best thing??? If he isn't capable of doing that, what exactly would he contribute in Open Source?

Cool, learned something new today...appears F6,8, and 12 do something special. F6 sounds like it should log program activities, but I didn't see it do anything yet. F12 loads another instance of ImgBurn...not sure what that would be for other than maybe burning to 2 drives? What other cool little Easter Eggs are there?

Just covering all bases, not meaning any insults. 64bit is a weird beast. I have slipstream DVD of it and regular XP and apply regedit /s tweaks during T13 and regular XP applies fine, but 64 bit only applies half of them...what is weird is it applies the HKLM, but not current user. I'd think the HKLM would be an issue since it is the one split. I'm still trying to get them to apply right, even after install. Not sure what its deal is. M$ seems to have dropped the ball on 64bit. It is a shame too because the main reason I got it was to improve gaming and DVD rendering times. So far I haven't seen much improvement, and driver support is still behind.

This may be something out of his control. I was using Winspector to try and see if it was possible to get the handle to the current file text for another thread and while there I decided to play with some of the other windows that were pre created like the option windows, RW Erase Windows, Error prompts, etc. I set a few of them to have a Visible style (which made the normally hidden window visible). Normally this would just show the window as any other window...but I noticed when doing it that something else was taking control too and putting the main ImgBurn window to the foreground on top of all my other windows. C++ Builder appears to use some type of subclassing and an "engine" to render its windows the way it wants. Most I made visible didn't have anything drawn on them yet. It didn't appear to use many actual controls either other than progressbars and some types of image buttons. Everything seemed to be controlled by its "engine" too as some things like Close buttons and such which should function no matter what as they are part of the Default message processing of Windows were unresponsive too since the "engine" didn't see them as real/current windows I guess it ignored messages they sent. So, unless there is some way of telling it not to auto focus like it does it will keep doing it. It could be something to do with text wrote to log/window in a different way on when verify is checked or not causing the focus. Maybe in one case, the window draws text during the msgbox showing and in another it may finish updating the window before the msgbox is displayed, so doesn't steal focus...

From what I briefly read of the movie, it sounded like it came to theaters in Sept 2007, but advertising didn't get around until Oct-Dec. Someone in marketing goofed.

That should be the correct flag. Now, are you specifying that everywhere a flag is needed? The docs say WOW64 isn't smart enough to remember it between calls, so if you open subkeys, etc below the key opened with the flag you must specify it there too, otherwise it opens the 32bit side. This applies to Creating, Opening, and Deleting too.

Happens to me a lot when burning lots of small files. Never does too much though...I even have it sit sometimes waiting for buffers to recover and HDD to get caught up and it still verifies and looks fine. Years ago this made many coasters, but Buffer Underun Protection as most drives have now ended that. I bumped my buffer up to 40MB in the options and have it less often, but it still happens. Things to help with this is making sure the drive is defragged and ditch all the onboard stuff like sound, ethernet, etc as they use CPU cycles. Get a good sound card, ethernet card, and a modem if you dialup that isn't onboard or a "software" modem. Then downloading and such won't effect you. Having what you are working with on a different drive and not just a different partition than what you are burning helps too.

Funny filename too...Isn't Dragon Wars still in theaters? Sounds like an idiot with a camera strapped on his head watched it for ya, then has the nerve to call it "DVDRip". Since LUK had first hand experience with the joys Macrovision, etc. You are in the wrong forum. Try the Cheap Kids Trying to Copy Movies and Can't Find the Power Button forum. Edit: Looks like it actually came out yesterday. Must not have been very good since the first advertisings of it I've seen have been lately. Must have went straight to DVD and if in theaters it flopped. Perhaps you should have shown your support for your movie and went and watched it...

I saw this option too, but didn't use it yet. Is there a list anywhere as to what players support this or is it those made after a certain year, etc? And, the option is just in a general area, so does this apply only to video or does it help speed up data discs too when they cross the layer break?

I have WinXP 64bit and mine does the same thing. I'll look tonight and see if there is a way around it. What does your call look like that sets the keys in Imgburn? Does it use API (Like RegCreateKey, RegSetValue, etc) or a built-in command C++ Builder has? There may be a new registry API for 64bit. M$ is always good about having perfectly good API calls then adding an "Ex" on the end to make it do something special. Then they like having reserved params for future use too that never get used. If I find a way to make it write to those keys I'll send you the code or DLL to get the job done. It is most likely a protection thing since 32bit explorer extensions don't work...which kinda sucks since I had some awesome property tab extensions...but as noted this works when manually done and isn't an extension so it should be allowed.

Still couldn't get access to the file text like I wanted...a verbose option like I mentioned logging files to the log would be a nice feature and help in debugging burn issues. I did do a 2X test burn of the one I thought was going in wrong and it does go on like post #15 above. Sorry for the false alarm. The DVD is huge. There is a folder for just about every letter of the alphabet...some more than one, and each folder has 1-7 levels, so it flys all over the place, but does do it in the by level somewhat recursive fashion like you showed. I guess for some reason I was thinking it would do it one branch at a time in alpha when I was watching it before kind of like a full recursive, but from your example it looks like it is recursive by level instead of by branch. Thanks for the explanation above.

Nope, no Optimise option is on. Since it has a bug I've been waiting for "Christmas" as the other thread called it...for the version to come out with it fixed to use it. Thanks for the explanation. I guess I'll run through a bunch of Test Modes and see in more detail what is happening. Some type of video looks like my only option to grab what the file order is while burning, unless you can add some type of verbose flag to make the log show every file burning? I looked at the application with Winspector to see if I can grab the handle of the label/edit box to grab the text where the file names show and the application doesn't use a standard layout. Is that made with a Delphi compiler or something? Usually those and .NET apps are the only ones that give me issues. The forms are all Top Level tfrm... classes and for some reason don't appear to be children of the main ImgBurn window like they are all their own parent window. TfrmMain which is the window that has the file information section is just a bunch of panels and the only real controls are the 3 progress bars. Everything else is just drawn graphically, so no control to pull the filename text from. I guess that makes it more secure, and all the forms being preloaded make them work quicker...at the expense of a longer load time. Why they appear as their own window is confusing though. At least they all start with Tfrm so they are all together.

I know he was talking about AVI. He also mentioned playing them in a player though. Clarifying your previous post was what I was trying to do...so, is the data burned in alpha order just like the dir info? I know I've seen it happen at least 3-5 times like I mentioned too, while burning it shows the current files being burned in the Information section. I have a slipstreamed Windows DVD with $OEM$ folder containing both my versions of Office I can select which to install during setup, etc and see it jumping all over the place from one of the office folders back to the root folders then back to the office folder. I have another DVD containing Drivers and software that I recently put my Xara files on too that gave issues with the Optimise Files problem. It seems to work ok until it gets to the Xara Xone files which are a bunch of HTML and HLP type files and their images, etc. (So lots of files) Then it goes nuts again and Jumps to various folders then back to the Xara folders again. The way you described it the files should burn with increasing levels, but it jumps all over the place and to previous levels. I guess I could make a video of it...although I'm not sure how clear it would be. I'd do better to make an app that grabs the text of the label/edit box showing the files on a timer and when different logs it to file, so it would catch it more accurate than video. I'll see what I could throw together. You mentioned DVD Video being burned different too. Is there an FAQ or something that describes how all the different burns/filesystems/disc types write files and how they write file dir info vs. file data?

I'm still confused, by "actual files" are you meaning the data or the Dir information? Are you saying I was wrong, or right, but it wasn't important? I guess to rephrase, is the file data burned in the same order as the Dir Information/Alphabetical? I was always under the impression that DVD Players read in a Block/Sector format, so the file data needed to be in the proper order. Some early discs even used this as a mild copy protection...I think my Steve Martin SNL did this where it would do something like: ' Example, not actual filenames \VTS1.VOB \VTS2.VOB \VTS3.VOB \A.VOB Say where A wasn't a part of any IFO files, etc and not used by the disc, but since the Dir info and File data were stored in this order it never saw the file reading by block/sector. But, copying the files would sort it and put it in front of the other files and make the disc unplayable or perhaps play a video saying it was copied, etc. I'd think it would be important that the files are listed in the same order that they are wrote to disc. In watching it burn though it is showing the files go on like: Folder1\File1 Folder1\File2 Folder1\File3 Folder2\File1 Folder2\File2 Folder2\File3 Folder1\File4 Folder1\File5 Folder3\File1 etc... So, is that the order that data is wrote then? That wouldn't agree with the dir info then you said was Alpha sorted by level. Wouldn't data order be import in his case and with other DVD players, etc?

I'm not seeing this...especially if they are burning in the order that shows in the Information area while burning. I have some files I burn to DVD which are pretty large, so the current file burning goes slow enough that I see it burning out of order. Many times it will burn some in one folder, then some in another, then back to the first folder again. Are you sure you aren't looking at the current code for the next version when you say this? I know there was the Samsung DVD Player thing I just read about and the reason ended up being ISO related...since DVDs read like a stream, having ISO files out of order would cause problems. The Optimise Files feature I had reported also ended up being an order issue. The Dir Entries and LBA stuff may be wrote in order, but from what I'm seeing, the actual file data isn't...

Yeah, tooltips would be the best way to go, that way the interface isn't cluttered. FWIW, I love how accurate ImgBurn is. Most apps use M$ rounding and as noted it isn't accurate. The only improvement I see in that area is if you calculate it shouldn't have to do it again when burning. It would take a little extra work though to add a watch on the root of all the folders added or all files to see if they changed though which may not be worth it. Most apps don't even give the option to calculate though, so they don't have to deal with it and you don't know till the last min...so I guess we have them beat.

I know it is needed...although I always thought it was more because the drive's cache needs cleared and without it the verify wouldn't work because it would read from the cache in memory instead of the physical disc. I was guessing DVD is cached differently and maybe had a clear option or was that the disc is larger than RAM, so the cache didn't work the same as CD was why they didn't do it. Without ejecting I've still had discs report as different, so I guess it still works...I was just trying to figure out why they stopped doing it for DVD. Anyway, thanks LUK for putting it in the Log for the filename. I kinda figured it worked the way you describe. Really, if you think about it...a lot of software works that way. It is just a matter of storing the name and allowing just clicking save to save back to the same name behind the scenes. In programming, it is all just reading and writing, there never is any magic connection between app and file other than it having the file open when needed. I usually store the filename in a Global and use it when calling the GetOpenFilename/GetSaveFilename API, then it pre-populates the name with the last file too.

Figured I'd add this here since it has to do with the log window too. Not sure if it is too late for the current build or not, but any chance of getting the Project name that loaded to log? Right now it just confirms that the project loaded, but doesn't give the project name. I often have 3-4 projects I burn after updating files and it is hard to tell which one is currently open. Might even be good to always have it visible in the titlebar or something too. Another thing that is in the log that reminded me of another question was Tray Cycling before verify. I noticed Nero doesn't do this on DVD and only does it on CD. Is there any logic/reasoning behind when the tray needs cycled like RAM, Disc Type, Phase of the Moon, etc. Sometimes it freaks the dog out and he likes to jump at it. One of these days he is going to beat it closed.

Interesting. I just read the majority of the long drawn out thread. Glad I burned all my discs as straight UDF now to keep to specs. Kinda dumb that it read ISO. Perhaps that is why the Book Type mattered since true discs (Not Burned) would be to spec and only have UDF, so it only looked at UDF. I guess like IE it covers all bases and loads things not to spec too and on burned discs it for some reason allows ISO. You'd think it would go with the highest/best format. Doesn't really sound like a bug to me if the proper File System is used in ImgBurn...it did help tweak the ISO file system in the end, but I'd have to agree with the posts saying the player was not to spec since ISO shouldn't have been read by it or used by the person making the image... I've been so distracted with DVD and regular data CDs that I never even noticed the lack of CD Audio. I guess that would round out the product and make it replace Nero. My new car has MP3 CD available, so I haven't made much Audio CDs lately. One thing that would be nice, although I don't know how possible it would be is some speed/burn level control. As I mentioned in another thread, I usually burn all discs at 8x...and sometimes 6x if my HDD is fragmented. Otherwise looking at the "rings" on the disc there are areas that are fainter when the drive switches speeds or ramps up the speed from the 4-8x it gets to fairly quick to 12X+ which takes it until mid disc to get to. Is it possible to send the drive a command to tell it to say..."Get to 12x, then start burning", so it is up to speed and the whole disc is burned at the same rate and no sections at a different rate?

Awesome, glad I could help. I figured it had to be something about the number of dups that would bring it to the surface. This feature will greatly help out my backups and let me fit more on my discs. You have so many things in this package that no one has. You ever think about writing DVD Authoring/Editing Software? We know you can handle DVD video and your burning is looking 10 times as good as the rest. You make a package with it all and you'd put them all out of business. Being one guy with I'm sure much more of a life than ImgBurn and still solving problems faster than the big companies. Great job on everything!