Jump to content

Sterlin

Members
  • Posts

    14
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • OS
    Windows 7 x64

Sterlin's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Had the same problem... deleted reg key and a file called 'wmfltr.sys'... problem solved on Win 7 Pro x64. Thanks Legolash20!
  2. Update: By entering a product key (instead of manually choosing the version to install), setup seems to respond more quickly. The disk partition section is almost instantaneous where previously it took 6-8 minutes to navigate. The question now is whether or not there is a way to avoid the delays created by not entering the product key? Thanks in advance, ~S
  3. I could have sworn that I asked before, but I can't locate the post... Everything seems to work as expected with a Vista SP2 disk (updates, tweaks, etc), but when the installer gets to the disk format/partition screen, the installer gets extremely slow. This is the case whether or not an Autounattend.xml file is used. The problem exists with Virtualbox and VMware, both of which are assigned CPUx2 and 4GB RAM. I am going to test on a bare metal box this afternoon. The problem doesn't occur with Windows 7. Has anyone else had this issue? Thanks in advance, ~S
  4. I have created an autounattend.xml file for my all-in-one Vista SP2 disk and it seems to work nicely, except that the installation slows to a CRAWL once it asks for the product key. Typically I set it up so if I don't enter the key, it will ask which version, which occurs but at a snail's pace. The installation proceeds at a normal rate without the XML file. WinSIM says the XML file is all good... it is attached... any help would be appreciated! Autounattend.xml
  5. Quick reply, thanks! I will watch that thread... ~S
  6. I had the same issue... just posted in "Runtime error" thread. Sorry for the duplicate post! ~S
  7. I have been getting consistently good results from the latest versions of W7Tkit and I thank you for your efforts. I have struggled, however, to find the option to specify the language, time/currency, and keyboard format in the autounattend.xml builder. Am I missing something or is it not an option at this point? Thanks in advance! ~S
  8. I received a runtime error during integration yesterday... the option "continue" allowed Win7 Toolkit to finish, although it had an elongated, red "X" in the lower section of the window. The program completed and produced expected results. The error text follows: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index at System.Collections.ArrayList.get_Item(Int32 index) at System.Windows.Forms.ToolStripItemCollection.get_Item(Int32 index) at System.Windows.Forms.ToolStrip.OnPaint(PaintEventArgs e) at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs) at System.Windows.Forms.Control.WmPaint(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.StatusStrip.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) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5448 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll ---------------------------------------- W7T Assembly Version: 1.4.0.11 Win32 Version: 1.4.0.11 CodeBase: file:///C:/Users/Brian/Documents/OSwork/Win%207%20Toolkit/W7T.exe ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5453 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5446 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.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 ---------------------------------------- System.Management Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll ---------------------------------------- Vista Api Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Users/Brian/Documents/OSwork/Win%207%20Toolkit/Vista%20Api.DLL ---------------------------------------- SevenZipSharp Assembly Version: 0.64.3890.29348 Win32 Version: 0.64.3890.29348 CodeBase: file:///C:/Users/Brian/Documents/OSwork/Win%207%20Toolkit/SevenZipSharp.DLL ---------------------------------------- Microsoft.VisualBasic Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.5420 (Win7SP1.050727-5400) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.
  9. I've built several versions at once and it takes just under 2 hours... by far the quickest tool I've used with Vista or 7. The adjustments should occur in the folder that you specify at the start... did you create the ISO and boot from that? I'm new to this myself...
  10. Thanks Bob... got the setupcomplete working. Do you all recommend integrating the unattended.xml before using the All in One tool? I'm figuring that maybe the file needs to be rebuilt into the images and doing that part first may help. -S
  11. Thanks for the link bp... I'm reading now that there is an issue with the unattended part of the AIO tool. That seems to be my major issue right now. I've actually tried to use the setupcomplete.cmd to no avail. Anybody got advice on that method?
  12. ...I have selected my images, made my choices on each tab, and started the process. I then went and selected my unattended options and created an ISO. I was thrilled because it only took about 2.5 hours and I thought we had ourselves an AIO Win7 install disk. My test in VirtualBox wasn't unattended and none of the silent installers seemed to have run... I shut it down before I looked to see if the updates were installed because I am obviously going to have ot redo the thing. I looked around the tutorials but couldn't find anything... I am a bit tired though, and a few Heinekens in me... can somebody post a link for the ID10T that can't find his hand in the dark? Not sure what I missed. Thanks very much in advance, S
  13. I have used this and another application to integrate driver packs into an unattended Vista disk, but it seems that the install freezes or gets slowed up dramatically after I enter the product key. Is there something that I'm doing wrong or is it not a feasible option to integrate multiple drivers in Vista? Thanks for your help, S
×
×
  • Create New...