sparafucille Posted July 14, 2013 Share Posted July 14, 2013 Greetings OS: Win7+SP1 ImgBurn Ver.: 2.5.8 2 problems 1) In Build mode when I click the layout editor it appears minimized. what can I do so that it appears as a new window already "restored"? 2) when the layout editor is restored and I click the main ImgBurn window I can't see it as the layout editor acts as "always on top". what can I do to prevent it (be able to jump bewtween the two windows). In win XP I didn't have both problems. Last question: 3) Is there a way of saving the settings so that I can transfer settings from win XP to Win 7? thanks Link to comment Share on other sites More sharing options...
dbminter Posted July 14, 2013 Share Posted July 14, 2013 I can't answer the first two questions, but, I can answer the last question. You will need to open the Microsoft Registry Editor. Under Computer, expand the tree for HKEY_CURRENT USER. Expand the tree for Software that will appear under HKEY_CURRENT_USER. Find the ImgBurn entry under Software. Right click on ImgBurn and choose Export. Save the file to wherever you wish. To import these saved settings, just double click on the .REG file you just saved and the settings will be imported. Do not import the Registry keys while ImgBurn is opened. Otherwise, the settings may be changed when the software is closed. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted July 15, 2013 Share Posted July 15, 2013 1. I don't know why that would be happening. The program should be saving the current state of the window and restoring it. 2. It doesn't work like that by default so you must have enabled the 'Stay on top' option. Look on page 2 of the 'Build' tab settings and uncheck the 'Disc Layout Editor Window - Stay on top' option. 3. As dbminter said, but I wouldn't recommend using it between OS's. Some options have different default values depending on the OS and general machine specs. Link to comment Share on other sites More sharing options...
sparafucille Posted July 15, 2013 Author Share Posted July 15, 2013 thank you dbminter. as admin said done it in windows 7 so that it'll serve me in the future. admin, I'm with ver. 2.5.8.0 and in the settings, build tab, page 2 the stay on top checkbox is unchecked. but now I notice that if I click the layout editor on imgburn main windows the layout editor dissappears and I see the burn icon again the question is will it burn with the layout editor not in sight? I'll have to try. many thanks Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted July 15, 2013 Share Posted July 15, 2013 Yes, you can open and close the DLE window as much as you want. What's displayed in it will be what gets burnt to the disc - it doesn't need to be open for that to be the case. Link to comment Share on other sites More sharing options...
sparafucille Posted July 16, 2013 Author Share Posted July 16, 2013 thanks again admin but you must admit that it is a temporary solution. Can't imagine why the same version in XP behaved normally. btw, I compared the settings tab by tab (using a kvm) and found 1 difference concerning playing CD/DVD automatically which is a system option. I'll check it off in the device manager. Is there a chance of things getting better by removing, cleaning and reinstalling 2.5.8? going back to previous version? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted July 16, 2013 Share Posted July 16, 2013 I don't understand what you're having a problem with. I'm running Windows 7 and don't have either of the problems you mentioned in your first post. Link to comment Share on other sites More sharing options...
sparafucille Posted July 16, 2013 Author Share Posted July 16, 2013 I didn't have this problem either in XP. this is new to me. the problem is that once the layout editor pops up in front of the main windows I cannot click the main window and see it, like I should. can removing imgburn completely (including cleaning the registtry) and reinstalling be helpfull? thanks Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted July 16, 2013 Share Posted July 16, 2013 Maybe, give it a try. You don't need to 'clean' the registry, the uninstaller wipes out the registry keys that ImgBurn reads its settings from. Link to comment Share on other sites More sharing options...
sparafucille Posted July 17, 2013 Author Share Posted July 17, 2013 report: removed imgburn, cleaned the folder, checked the registry and there were only indirect reference to imgburn (by other programs that use burning) so I left them, reinstalled 2.5.8.0 and got the same phenomenon. I give up. My windows 7 is quite new, installed a little over a week ago. maybe I should go back to some previous version. It is one of the very rare and few times that I didn't solve the problem with the help of a forum. meanwhile I'll do what you suggested, admin: after dragging files to burn I'll click the layout editor on main window so that it dissappears and click the burn icon and hope for the best. many thanks! Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted July 17, 2013 Share Posted July 17, 2013 Oh hang on, I know what's going on here... In XP, the program has a 'hidden' window as the actual main/parent window rather than the main 'ImgBurn' window (as you see it). In Vista+, the main 'ImgBurn' window (as you see it) is the main/parent window (this is a requirement for the fancy new taskbar added in the later OS's). All 'child' windows seem to stay on top of the main/parent window in the z-order. That's why in Windows 7 you can't get the DLE window to drop below the main 'ImgBurn' window in the z-order. So click the big 'Show Disc Layout Editor' button on the main 'ImgBurn' window to open the DLE window, create your disc structure and then just close the DLE window again via the red X in the top right corner and go about your business in the main 'ImgBurn' window. Sorry, I was thinking more about 'modal' windows (where you physically can't click on anything other than the foreground one) rather than a z-order issue (which I guess I'm used to now). There's actually a 'quality control' post about it for my development environment (other people didn't like the z-order issue either) but CodeGear marked it down as 'by design' and did nothing to work around / fix it. http://qc.embarcadero.com/wc/qcmain.aspx?d=45606 Link to comment Share on other sites More sharing options...
Recommended Posts