Legolash2o Posted May 16, 2011 Author Share Posted May 16, 2011 (edited) I still have a problem when I put the "change the setup backround" installing sto erros. "Corrupt autorun" etc.x:\Sources\SPWIZIMG.DLL is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact ......."The file autorun.dll could not be loaded or is corrupt. Setup cannot continue. Error code is (0xE0000 100)Tested Virtualbox.Can you please upload a unmodified 'x:\Sources\SPWIZIMG.DLL' to an external site please.I can't use Restorator as it's trial software. Also don't try the tweak with Windows 8 until it's working on Windows 7. The tweaks seem to be working for everyone else. Edited May 16, 2011 by Legolash2o Quote Link to comment Share on other sites More sharing options...
Kelsenellenelvian Posted May 16, 2011 Share Posted May 16, 2011 Why is the rebuild time so much slower now? Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted May 16, 2011 Author Share Posted May 16, 2011 Which rebuild button did you use, WIM Manager? How many images are in the wim you want to rebuild? Quote Link to comment Share on other sites More sharing options...
Kelsenellenelvian Posted May 16, 2011 Share Posted May 16, 2011 10+ images but the time between versions is a really looong time (Wim manager)it isn't the time of the proccess it is the time between each version. Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted May 16, 2011 Author Share Posted May 16, 2011 (edited) Go to W7T Options and uncheck Verify Images and Check Images. Then save.Although disabling 'Check Images' should speed up rebuilding on its own EDIT: Looks like i found a but when disabling 'Check Images', ill fix it now.EDIT: Fixed, will be in v5 which i will release soon. Edited May 16, 2011 by Legolash2o Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted May 16, 2011 Author Share Posted May 16, 2011 (edited) v1.0.2-5F released.You should notice an improve on the startup speed on this version, some new Tools Manager icons, they have been re-arranged in alphabetical order. Also their is now an option for 'Quicker Merging' which radically speeds up the Create AIO Disk tool and 'Merge Image' in WIM Manager however the wim may be bigger because it does not rebuild the original wim before adding the new one.*FIX: Could not disable 'Check Images' option*Updated splash screen*W7T now starts faster*Improved speed on 'Checking for Updates'*Items re-arranged in alphabetical order on Tools Manager Edited May 16, 2011 by Legolash2o Quote Link to comment Share on other sites More sharing options...
hornet512 Posted May 16, 2011 Share Posted May 16, 2011 Finland is ice hockey champion 2011! :thumbsup_anim:ice hockey world championships 2011 - FINLANDgood for you :prop: please walk around Esplanade Park for me I miss it. Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted May 16, 2011 Author Share Posted May 16, 2011 v1.0.2-6F released. Just some GUI changes to the Tools Manager (main screen). Disabled buttons now say why they are disabled. Quote Link to comment Share on other sites More sharing options...
Sorin Posted May 16, 2011 Share Posted May 16, 2011 just a stupid question ... the .inf drivers i get integrated into windows , goes into boot.wim ? Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted May 16, 2011 Author Share Posted May 16, 2011 Depends on the type of driver, I don't knowte types of the top of my head but display, audio, Ethernet don't go into te boot.WIM but drivers for SYSTEM/SATA/SCSI/HDC do. Why you ask? Quote Link to comment Share on other sites More sharing options...
Sorin Posted May 16, 2011 Share Posted May 16, 2011 (edited) just want to know Lego , that's all . i was interested to know if the masstorage drivers goes into boot.wim ..that's all..and the dispaly, audio, ethernet and all other drivers goes into install.wim ...correct?! Edited May 16, 2011 by Sorin Quote Link to comment Share on other sites More sharing options...
Kelsenellenelvian Posted May 16, 2011 Share Posted May 16, 2011 Yes massstorage drivers go into boot.wim Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted May 16, 2011 Author Share Posted May 16, 2011 Yeah correct, mass storage drivers go into both boot and install.wim Quote Link to comment Share on other sites More sharing options...
Sorin Posted May 16, 2011 Share Posted May 16, 2011 but the dispaly, audio, ethernet and all other drivers goes only into install.wim ...correct?! Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted May 16, 2011 Author Share Posted May 16, 2011 Yeah. Quote Link to comment Share on other sites More sharing options...
Sorin Posted May 16, 2011 Share Posted May 16, 2011 (edited) Thank you for answering... i've only asked because i created a setup to run after windows is installed .. the setup contains all the driverpacks . Edited May 16, 2011 by Sorin Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted May 16, 2011 Author Share Posted May 16, 2011 Ok im home now and finished work, just to clarify.The following driver types will integrate into boot.wim and install.wimHDCSCSIADAPTERSYSTEMMTD1394Everything else is just install.wim Quote Link to comment Share on other sites More sharing options...
ChiefZeke Posted May 16, 2011 Share Posted May 16, 2011 ChiefZeke for some reason the packages program i use to show hidden packages does not like spaces in the mount path ie.C:\W7T\Mount, seems to be okC:\W7T\Test Mount 1, seems to error.EDIT: I have used the source code of that program to fix the issue, it should now support spaces on the next version. Hopefully So, even though I had enclosed things in double quotes, ""**"", to comply with DOS rules about no spaces you're saying that is incorrect also - have yet to check new version as I'm in XP right now, but I thought I'd ask about the double quotes while here; for my own edification.Your second example, above, I would think would work as: "C:\W7T\Test Mount 1" ? Quote Link to comment Share on other sites More sharing options...
Sorin Posted May 16, 2011 Share Posted May 16, 2011 Lego, Thank you for making clear the whole pic ) i got it now! Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted May 16, 2011 Author Share Posted May 16, 2011 (edited) W7T automatically added quotes, but even if you had used them for the other program it would not work, luckily someone provided me the source code on another topic and i managed to modify it and fix a bunch of bugs. Double quotes and normal quotes just did not work but it should work now. The external program open another command prompt tool and it did not add the quotes.So is it all working properly now? Edited May 16, 2011 by Legolash2o Quote Link to comment Share on other sites More sharing options...
ChiefZeke Posted May 16, 2011 Share Posted May 16, 2011 W7T automatically added quotes, but even if you had used them for the other program it would not work, luckily someone provided me the source code on another topic and i managed to modify it and fix a bunch of bugs. Double quotes and normal quotes just did not work but it should work now. The external program open another command prompt tool and it did not add the quotes.So is it all working properly now?W7Toolkit 1.0.2.6?(10) and Win7 Ultimate 64-bit w/SP1Component Removal > Win7 Ultimate > Select > Mount > 102 items were listedProblem solved Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted May 16, 2011 Author Share Posted May 16, 2011 YAY it works Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted May 16, 2011 Author Share Posted May 16, 2011 (edited) v1.0.2-7F, some very important fixes... Also there is a bunch of links added to the 'Download' menu on the main tool selection screen.*FIX: Did not detect currently mounted images on non-English language*FIX: Did not display 'unknown' packages properly in Component Remover)*FIX: Capture Image did not work when drive root was selectedEDIT: Build 8 released with a fix to unattended creator, it now only shows current serial key when you edit the Serial Key instead of all inputboxes. Edited May 16, 2011 by Legolash2o Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted May 17, 2011 Author Share Posted May 17, 2011 Anyone having any issues with the latest build? Quote Link to comment Share on other sites More sharing options...
Sorin Posted May 17, 2011 Share Posted May 17, 2011 See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.************** Exception Text **************System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualBasic.PowerPacks.Vs, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.File name: 'Microsoft.VisualBasic.PowerPacks.Vs, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' at W7T.frmOptions.InitializeComponent() at W7T.frmOptions..ctor() at W7T.frmToolsManager.mnuOptions_Click(Object sender, EventArgs e) at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e) at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)WRN: Assembly binding logging is turned OFF.To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging.To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].************** Loaded Assemblies **************mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5444 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll----------------------------------------W7T Assembly Version: 1.0.2.9 Win32 Version: 1.0.2.9 CodeBase: file:///C:/Users/A/Desktop/W7T102-9F/W7T.exe----------------------------------------System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll----------------------------------------System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5660 (QFE.050727-5600) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll----------------------------------------System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll----------------------------------------System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll----------------------------------------System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll----------------------------------------************** JIT Debugging **************To enable just-in-time (JIT) debugging, the .config file for thisapplication or computer (machine.config) must have thejitDebugging value set in the system.windows.forms section.The application must also be compiled with debuggingenabled.For example:<configuration> <system.windows.forms jitDebugging="true" /></configuration>When JIT debugging is enabled, any unhandled exceptionwill be sent to the JIT debugger registered on the computerrather than be handled by this dialog box.this happens when i click on the w7toptions Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.