MGadAllah Posted October 23, 2006 Author Share Posted October 23, 2006 can you post this file? Link to comment Share on other sites More sharing options...
Takeshi Posted October 23, 2006 Share Posted October 23, 2006 (edited) ImgBurn_2.1.0.0.exe /S works just fine for me in ROE. No messages.As for burning the ISO with non-Eng characters, that might be a useful workaround. nLite supports unicode when creating the ISO. But I meant burning directly from files. The two processes aren't the same.LUK said ImgBurn does not support unicode. Edited October 23, 2006 by Takeshi Link to comment Share on other sites More sharing options...
bledd Posted October 23, 2006 Share Posted October 23, 2006 there's no real need to install imgburn, i prefer just dragging the image files in manuallyi keep my img.exe in system32 folder, so "start run img" will open it.. and it doesn't take file assosiations then , runs fine standalonehttp://infrarecorder.sourceforge.net/^that looks dead smart, thanks for info Link to comment Share on other sites More sharing options...
mazin Posted October 23, 2006 Share Posted October 23, 2006 (edited) @ mgadallahBoth files are here:$OEM$\CDLMROEX\ImgBurn\ImgBurn.exe (downloaded EXE renamed)$OEM$\CDLMROEX\ImgBurn\ImgBurn.jsYou don't have to use this JS file unless you get those messages. Otherwise, just use /S.var WshShell = WScript.CreateObject ("WScript.Shell");var path = WScript.ScriptFullName;//getting the path to this scriptvar CDROM = path.substring(0,2);//extracting DriveLetter: from the pathWshShell.RUN (CDROM + "\\$OEM$\\CDLMROEX\\ImgBurn\\ImgBurn.exe /S");//running exeWScript.Sleep(2000);//time to unpack installer.WshShell.AppActivate("ImgBurn");//name of running WindowWScript.Sleep(1000);WshShell.SendKeys ("i");//set answer to ignore (first message)WScript.Sleep(3000);WshShell.AppActivate("ImgBurn");//name of running Window (not the full name)WshShell.SendKeys ("Y");//set answer to yes (second message)I managed to uninstall then re-install ImgBurn in the hope of capturing the two messages.Unfortunately, I got the first message only. (now, eh!)If I remember correctly, the second message is about "Do you want to keep your current settings? Yes/No".Well, BTW, I use these tweaks in my CleanUp.cmd:del "%UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch\ImgBurn.lnk" >NULmove "%UserProfile%\Start Menu\Programs\ImgBurn" "%AllUsersProfile%\Start Menu\Programs\ImgBurn" >NUL@ TakeshiI have CDIMAGE and CDBURN already in my System32 (via $OEM$).I think this is why ImgBurn thinks it's already installed! I'm just guessing.Ah, then I was just lucky with nLite!Thank you for the info about unicode names. I should take care of this.@ bleddThank you for the tip. (haven't read it before posting!)Have you just renamed "C:\Program Files\ImgBurn\ImgBurn.exe" to img.exe and moved it to System32?If so, don't I need any more files from installation? Edited October 24, 2006 by mazin Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now