eraz0r

Oh yeah, the format they are being converted to .vob files. in the Video_TS file I see. Well, I'd suspect that there are some compatibility issues between the burned discs and the standalone player used for playing them. Some models don't like the discs booktyped anything but DVD-ROM, for instance. Have you tried to play the disc on your computer? on another standalone?

If you have just one VOB file, it doesn't mean that you have a DVD-compliant disc. VOB contains the data (audio, video streams) + you'll need *.ifo/*.bup files which form the 'correct' structure of a DVD disc. When your converting software is done with whatever it's doing you should see something like this in the output folder: Z:\VIDEO_TS>dir /B VIDEO_TS.BUP VIDEO_TS.IFO VTS_01_0.BUP VTS_01_0.IFO VTS_01_0.VOB VTS_01_1.VOB VTS_02_0.BUP VTS_02_0.IFO VTS_02_1.VOB VTS_02_2.VOB VTS_02_3.VOB VTS_02_4.VOB VTS_02_5.VOB VTS_02_6.VOB VTS_03_0.BUP VTS_03_0.IFO VTS_03_1.VOB VTS_04_0.BUP VTS_04_0.IFO VTS_04_1.VOB VTS_04_2.VOB VTS_05_0.BUP VTS_05_0.IFO VTS_05_1.VOB VTS_06_0.BUP VTS_06_0.IFO VTS_06_1.VOB VTS_07_0.BUP VTS_07_0.IFO VTS_07_1.VOB The above files represent the properly mastered DVD disc (the amount of files in your case may of course be different). One more thing, you don't have to create an ISO image from the files on hard drive. Instead you can burn them directly to a DVD+-R/+-RW media using the Build mode.

Ah, I don't think the first option is doable for him. Check the log: 11:36:22 Image Size: 9,260,728,320 bytes I 11:36:22 Image Sectors: 4,521,840 The image won't fit into DVD9.

Be sure to disable ANY antivirus protection when flashing the drive. If that's not helping, then you may have some 'filters' installed in your system, which might obstruct the normal flash process.

What are the source files? You have converted them into what? Is it a proper DVD format? Could you also post a log from your burn session?

I don't get it. How were you able to burn almost a 9GB image onto a DVD? Was it with re-authoring or not?

It has nothing to do with the ImgBurn. I replied to the guy with the same problem in another thread. Here is the link: http://forum.imgburn.com/index.php?showtop...ost&p=92085 In two words: you have virus/malware. Check my link in the post above, you'll find more info/solution there.

Thanks!! Your tech support and replies are perfect!

Just FYI, your image even exceeds the DVD-9 (aka dual layer disc) size, so the only way to burn it without re-authoring/modifying would be to use a Blu-ray media (since you have a Blu-ray drive in your system anyway). If you still want to go with the compression method, then you should try some re-authoring software, e.g. CloneDVD2. However, there is a plenty of similar apps available, google for them, see what fits your needs best.

That's an excellent news indeed! Question: Can I fix it somehow (maybe temporarily?) on my local machine (e.g. via a certain registry key) or should I wait for the next version which will fix it for me? Thank you.

Look, I just realized, could it be because of the localized Windows version (namely russian) being used on my machine? However, I have all the regional settings set to English anyway. I'm not a programmer myself, so don't know a lot about all those System API calls and stuff.

Yep. Completely agree with you on that. Just wondering, have you been able to figure out where the catch is? Once again, many thanks for your instant replies!

Not at all. I'm merely curious. Many of us (myself included) have been learning from Lightning_UK for a long time. Around 7 years for me, I think. I've found that it's best to have the latest of everything just incase any problem encountered has already been fixed by an update or upgrade. OK, I got your point. Thanks for letting me know. I'll get my hands on the SP3 stuff really soon

Aha, I see now as well and the status bar font is the font which corresponds to ToolTip setting or vice versa That's why when I change it in one place I'm able to see the changes in ImgBurn's look. I've got no clue why it's failing on my machine. There haven't been any changes to the settings/installed apps on it for months, I mean it's a pretty clean install of WinXP + a dozen of apps I need, that's it.

I have almost all the updates that were released prior the SP3, so I didn't install it when it became available. I don't think it has something to do with the issue I described. Do you?

Thanks a lot for your detailed reply, very much appreciated. Segoe UI font is not available on XP by default, I just added it manually. As about the code changes you made, there is still something that has been changed, because I have 2 desktops both running XP Pro w/SP2 but different versions of ImgBurn: 1) XP Pro w/SP2 ENG + ImgBurn 2.4.2.0 2) XP Pro w/SP2 RUS + ImgBurn 2.4.4.0 and if I make any changes to the ToolTip font settings on the first machine it doesn't affect the way ImgBurn's GUI look like, i.e. main window, settings window, driver order load window, etc. Of course the tooltip pop-ups within ImgBurn do reflect the changes. I mean, that the main program GUI font is still Microsoft Sans Serif, which I believe is the default Windows GUI font on XP, at least I have all standard dialog boxes, windows, etc. displayed with it. Now, if I do the same on the second machine, ImgBurn picks up the font I set for the ToolTip and uses it as the default one. Everything else on both machines is the same in regards to the Display Properties-->Appearance settings, so it's not me messing up with the font parameters I turned the debug mode on, and here is my log: W 15:28:49 Program 'Debug Mode' has been Enabled! D 15:28:49 Font - DefaultFontName: Tahoma D 15:28:49 Font - lfFaceName: Segoe UI D 15:28:49 Font - GUI: Segoe UI D 15:28:49 Font on 'frmSplashScreen' changed from 'Tahoma' to 'Segoe UI'. D 15:28:49 Font on 'frmMain' changed from 'Tahoma' to 'Segoe UI'. D 15:28:49 Font on 'frmLog' changed from 'Tahoma' to 'Segoe UI'. D 15:28:49 Font on 'frmBurnNextDisc' changed from 'Tahoma' to 'Segoe UI'. D 15:28:49 Font on 'frmPrepareImage' changed from 'Tahoma' to 'Segoe UI'. D 15:28:49 Font on 'frmBuildImageTree' changed from 'Tahoma' to 'Segoe UI'. D 15:28:49 Font on 'frmReplaceFile' changed from 'Tahoma' to 'Segoe UI'. D 15:28:49 Font on 'frmBurnQueue' changed from 'Tahoma' to 'Segoe UI'. D 15:28:49 Font on 'frmDropZone' changed from 'Tahoma' to 'Segoe UI'. I 15:28:49 ImgBurn Version 2.4.4.0 started! I 15:28:49 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) However, please note that it says "lfFaceName: Segoe UI" and not 'lfMessageFont' as you wrote above and according to your log information. I changed the font once again for ToolTip and here is how ImgBurn reports about it now: W 16:08:45 Program 'Debug Mode' has been Enabled! D 16:08:45 Font - DefaultFontName: Tahoma D 16:08:45 Font - lfFaceName: Courier New D 16:08:45 Font - GUI: Courier New D 16:08:45 Font on 'frmSplashScreen' changed from 'Tahoma' to 'Courier New'. D 16:08:45 Font on 'frmMain' changed from 'Tahoma' to 'Courier New'. D 16:08:45 Font on 'frmLog' changed from 'Tahoma' to 'Courier New'. D 16:08:45 Font on 'frmBurnNextDisc' changed from 'Tahoma' to 'Courier New'. D 16:08:45 Font on 'frmPrepareImage' changed from 'Tahoma' to 'Courier New'. D 16:08:45 Font on 'frmBuildImageTree' changed from 'Tahoma' to 'Courier New'. D 16:08:45 Font on 'frmReplaceFile' changed from 'Tahoma' to 'Courier New'. D 16:08:45 Font on 'frmBurnQueue' changed from 'Tahoma' to 'Courier New'. D 16:08:45 Font on 'frmDropZone' changed from 'Tahoma' to 'Courier New'. I 16:08:45 ImgBurn Version 2.4.4.0 started! I 16:08:45 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2) Please let me know if any other info is required.

That's right. I checked other Google results on this "too many secrets" error, in most cases people got rid of it by running malware scanners/rootkit revealers and cleaning the system up. Just give it a try and let us know if it helps with your problem.

Aha, interesting. Thanks for the input. I still can't see any connection between the ToolTip settings and ImgBurn default GUI font. Is this how it's supposed to be from version 2.4.4.0 on? BTW, what is the program GUI font on Vista?

Can be a virus/malware issue as well. Other users reported this error in Windows Explorer. Check this link for additional info: http://forum.sysinternals.com/forum_posts.asp?TID=15413

What concerns me is the word "probably" in the changelog entry above, as in fact it's NOT MS Sans Serif by default. You can check it for yourself, if you're on WinXP (not sure about other OSes). Change the ToolTip font to something funny & unusual and load ImgBurn to see how it affects its GUI.

Thank you for the follow-up. Yeah, sure thing I can use Microsoft Sans Serif as a tooltip font, but that's not a "right" solution, some sort of a workaround. Moreover I just love Segou UI, I don't really want to change it. And here are the pieces of changelog, that you're talking about: Changed/Fixed: When running Win 9x and the (default) Tahoma font is not available, the substituted GUI font was pretty awful! Now it'll attempt to use the system default (probably 'MS Sans Serif') if that's the case. Fixed: None of the automatic string truncation stuff (making them fit in the available space within the window) was working properly when the font being used was anything but 'Tahoma' (XP default). I blame Borland/CodeGear because changing a control's font doesn't update the canvas's font! I believe the above two items are the reason why ImgBurn now gets default GUI font from someplace else than before.

Since this is my first post here, I'd like to thank the author LUK! and all the beta team members for the excellent software ImgBurn!! It does rule the world of burning applications. Now, my little problem Up to version 2.4.2.0 ImgBurn used the Microsoft Sans Serif as the GUI font, which looks just perfect on LCD-type monitors with ClearType enabled. I've just installed the latest version, and see that this has been changed (also checked the "whatsnew" section on the homepage to confirm my findings). Now ImgBurn uses the font which is selected for 'ToolTip' item (found under Display Properties-->Appearance-->Advanced-->ToolTip Windows settings) as the default GUI font. I have Segou UI font set for the ToolTip item and with this setting all ImgBurn controls & GUI strings look just terrible. I don't get why it now reads font from there, because as I wrote above previous versions didn't. I played with different font settings for different Windows GUI elements, the only one that affects ImgBurn GUI is this ToolTip thing. Is there any way to force ImgBurn use Microsoft Sans Serif or maybe I can change it via some registry settings (I mean for the program)? Many thanks in advance.