-
Posts
109 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Sorin
-
-
Still waiting for .03 alpha version :type: :ranting:
-
Hey lego!
Silent installer now works well and is fine. It does not work if it is a USB stick on the hard disk copied.
It runs from the DVD just fine but if imagen size is 7 gb it will not fit on a DVD.
I copied the image files, therefore, Bootable USB, which copy the backup program on the hard disk. Start the installation from there. Silent installer displays an error.:thumbsup_anim:
Don't know why , but you've done something wrong. The silent installer WORKS even it is on a USB stick . And the silent installer doesn't displayed any error to me. Proof: Fresh install(LIVE) on an i3-540 at 1:25 AM. Look at the pic. Everything went grait with no errors!!!!
-
any news ? 1.0.3 alpha when its to be released?
-
link for the books please
-
Lego , i'm very relaxed i thought it was the WinSxS folder itself...anyway .. il let my post there for the people to see ..to don't make any stupid things.
-
to delete winSxS folder it's not a good ideea. If i remember correctly , the winSxS folder keeps a backup to the updates installed on your computer via windows update , and let you uninstall them. Doing so (removing the winSxS folder) it's probably a VERY BAD IDEEA.
Example : you get a bad update from microsoft .what do you do then ?! system restore? format? NO ...just uninstall .. that's why i said it's a bad ideea to remove that folder.
-
wpi does what w7t does with the silent installer (and w7t does it better an much quicker. i've used wpi , and i have to say that is a killer if you don't know what you're doing). that's all..i've see no point in adding wpi to w7t. my oppinion.
-
waiting for a week to pass :dribble: :w00t: :type:
-
Having to unpack the .7Z files was not what I had in mind. The script written by the folks at DriverPacks was designed to do the following:
"Here is a script developed from the original SAD script. I'll call it SAD2
It'll automatically determine the running system OS arch and extract the correct dps from the right directory. Very slick.
Supports all NT5 (XP/2000/2003) & NT6 (Vista/Win7) OS types."
So, given that the script was written to determine the running OS and correct DriverPack(s) I mentioned it so that a determination could be made to verify its compatibility with W7Toolkit.
Trust me , THEY WORK! It's not the first time when i used their script
-
Having to unpack the .7Z files was not what I had in mind. The script written by the folks at DriverPacks was designed to do the following:
"Here is a script developed from the original SAD script. I'll call it SAD2
It'll automatically determine the running system OS arch and extract the correct dps from the right directory. Very slick.
Supports all NT5 (XP/2000/2003) & NT6 (Vista/Win7) OS types."
So, given that the script was written to determine the running OS and correct DriverPack(s) I mentioned it so that a determination could be made to verify its compatibility with W7Toolkit.
Chief, i know that script ..i've used it and it's very nice. Does the whole thing. I've created a setup that contains their script and all the driverpacks . Works on x86 and x64(my setup). It also works to be added on Silent Install with Lego's tool. But here a question : why don't you integrate the whole pack of drivers with Lego's tool? It works very nice..gave me a few errors ..specially from webcam , but it works..For example , i did a fresh install this evening (win 7 ultimate x64) and it detected from the start my motherboards drivers.. otherwise i've had to put on my dvd drivers and install them one by one ..
-
W7Toolkit 1.0.2.14?(13) and Win7 Ultimate 64-bit w/SP1
I noticed that right under the title bar you added a Downloads option; one of which points to DriverPacks for Win7 x64 and x86. (Also, this change is not shown at - please update.)
My question is: if DriverPacks are downloaded how are they integrated using the W7Toolkit? When I go to Drivers > Add Drivers and navigate to the DriverPacks location and select the folder I have titled Win7-DriverPacks none are selected. I am guessing this is because they are all .7Z files and therefore not recognized by W7Toolkit. I am also pretty sure the folks at DriverPacks created a script that is to be used for including their DriverPacks with Win7; see: http://forum.driverpacks.net/viewtopic.php?id=4954
Their latest script is version 110505 - called SAD2 (Stand Alone DriverPack)2
Chief, you have to unpack all the .7z's ..just create a folder called Drivers and unpack all the .7z into that folder. then, you'll be able tho select what drivers do you want , or , even the whole folder! that's the way i do it
-
oki then )
-
-
***********************************
WIM Manager (All-In-One Integrator)(frmWIMManager)
Unable to check for mounted images <-> this error shows up when i click on AIO
Exception: Object reference not set to an instance of an object.
***********************************
-
-
win 7 ultimate x64
i clicked the w7t options button
-
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 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.
this happens when i click on the w7toptions
-
Lego, Thank you for making clear the whole pic ) i got it now!
-
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 .
-
but the dispaly, audio, ethernet and all other drivers goes only into install.wim ...correct?!
-
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?!
-
good ideea rick
-
just a stupid question ... the .inf drivers i get integrated into windows , goes into boot.wim ?
-
can't download ..try uploading the new version to a different site
Windows 7 Toolkit v1.0.2 FINAL
in OLD Threads
Posted
Lego, how's the work progress on .3 version of the toolkit?