class101
Content Type
Profiles
Forums
Events
Posts posted by class101
-
-
Hey ilko I have more Windows 8 infos
at home, installation of Windows 8 with eSATA key worked
at work, installation of Windows 8 with USB failed (same key in usb mode), it complains right after I click Install it does not find a driver, with FAT32 partitioned key, no advanced options
but I don't really know which driver is it about, my key does not need a specific driver to work in usb mode, I will try in NTFS mode and a few of your advanced options and let you know
//Edit: Same in NTFS with advanced option #3
//Edit2: Tried DriverPacks Mass Storage and Chipsets but couldnt find one working for the problem, Intel SATA AHCI and USB drivers are shown in list but when I select it and continue it comes back to the driver selection, will look if someone in thread as got same problem
//Edit3: Have tried numerous of drivers without sucess, the "Windows 7 USB DVD Download Tool" also failed to recongize my usb stick, I will try another approach by using bootsect.exe to make usb bootable and XCOPY windows files, its explained on MSDN blog here
//Edit4: Looks like machine specific problem rather than a usb key problem because now I'm back at home, the same key works in USB mode, the only difference I notice is that on my home machine(where it works for both eSATA+USB) I see the grub4dos menu you have customized with a Green background, and on my work machine (where it fails in USB) booting on the key does never show the grub4dos green menu, instead there is a blackscreen for 10sec. (seen physically and also in Qemu) then the Windows installation starts and fails later (asking for an unknown driver after hitting Install), very weird bug, I'm stuck, I will try to look the long list of replies to see if someone experienced the same trouble
//Edit5: Finally method in Edit3's link worked with diskpart.exe, bootsect.exe and xcopy.exe invocations on my work computer, it looks like a winsetupfromusb with win8+usb problem, unfortunelly it is not a complete solution for you ilko but at least from my edits you can easly spot there is something wrong with winsetupfromusb with win8+usb but not with esata
0 -
It is an historical day, Windows 8 goes RTM and is available to pros in its final state in MSDN
I confirm WinSetupFromUsb 1.0 beta8 worked here for installing Windows 8 Pro (x64) through an eSATA flash drive
No problems at all, thanks again MSFN and ilko and good bye MS aero
0 -
Ha sorry dude Im too much formatted with windows =) it seems it does not exist tools like Defraggler but for linux. However I have read a few lines saying if you had moved the iso to another place, you could get it back in 1 fragment and you could have saved your bandwith. Not sure so could be a fake rumour but next time try this trick too
0 -
use Defraggler to defragment the iso file NT Man, I'm not sure but I think this error is due to booting on a fragmented file
0 -
Sophos 9 reports \WinSetup-1-0-beta4\files\winsetup\PyronSetup\i386\setup.exe & setup_dbg.exe as Mal/Generic-A
But I think its much about a false warning I dont get suspect activities here and Sophos usually detects a lot of stuffs not supposed to be on an enterprise computer
0 -
Hey ilko I realized you made a new topic from my post in the old thread, just for information do you want the old thread to die or should I grab now WinSetup 1.0 beta2 from another thread ? Because I see you are on many projects but I dont really now if they are related or which thread should I follow I m a biut confuised because the old thread was talking about WinSetup from Smal iso, there is another one with Loaded RAM iso, I see too How to install from USB- WinSetupFromUSB with GUI, or add ion your sig the different projects yoiu are one to clear things up ^^
0 -
Ok so below are the logs,
C: is VolumeRAID0, (2x disks of 1Tb)
Y: and Z: is my Maxell SSD drive, one partition is for NTFS and the other is FAT32 where I'm putting all my bootable stuffs WinSetup OS aswell
Could be problematic so if you dont want to add PhysicalDrives for security, maybe you can code a warning when a physical drive is selected for a user confirmation the destination drive is the one wanted.
Well anyway if that is too complicated nvm its fast to workaround here
2010/02/23 20:53:58- WinSetupFromUSB 1.0 beta5 started
2010/02/23 20:53:58- OS: WIN_XP Architecture type: X64 ServicePack: Service Pack 2 OS Language: 0409
2010/02/23 20:53:58- Program directory: C:\Temp
2010/02/23 20:53:58- Getting USB drives information
2010/02/23 20:53:58- VolumeRAID0
2010/02/23 20:53:58- Interface type: SCSI
2010/02/23 20:53:58- DeviceID: \\.\PHYSICALDRIVE0
2010/02/23 20:53:58- PNPDeviceID: IDE\DISKVOLUMERAID01.0.00__\4&19FEAA6C&0&0.0.0
2010/02/23 20:53:58- Partitions count: 1
2010/02/23 20:53:58- Disk--Partition: Disk #0, Partition #0
2010/02/23 20:53:58- Logical Disk: C: File system: NTFS Primary: True
2010/02/23 20:53:58-
2010/02/23 20:53:58- Interface type: SCSI
2010/02/23 20:53:58- DeviceID: \\.\PHYSICALDRIVE1
2010/02/23 20:53:58- PNPDeviceID: IDE\DISK________________________________________02.10103\4&19FEAA6C&0&0.1.0
2010/02/23 20:53:58- Partitions count: 2
2010/02/23 20:53:58- Disk--Partition: Disk #1, Partition #0
2010/02/23 20:53:58- Logical Disk: Y: File system: NTFS Primary: True
2010/02/23 20:53:58- Disk--Partition: Disk #1, Partition #1
2010/02/23 20:53:58- Logical Disk: Z: File system: FAT32 Primary: True
2010/02/23 20:53:58- Drive letter of the selected partition- C:
2010/02/23 20:53:58- Drive letter of the first primary partition in selected disk- C:
2010/02/23 20:53:58- Disk number of the selected disk- 0
2010/02/23 20:53:58- PNPId of the selected disk- IDE\DISKVOLUMERAID01.0.00__\4&19FEAA6C&0&0.0.0
2010/02/23 20:53:58- File system type of the selected partition- NTFS
2010/02/23 20:53:58- Disk type of the selected disk- Fixed
2010/02/23 20:53:58- Total target size avialable- 682 MB
2010/02/23 20:53:58- Checking sizes...
2010/02/23 20:53:58- Total source size- 0 MB
2010/02/23 20:53:58- Target space available- 682 MB
2010/02/23 20:54:12- Removing TEMP folder
2010/02/23 20:54:12- ---------------------------------Program quited-----------------------------------------------0 -
Hey ilko I have a small request at 1.0 beta2
The method you are using to detect USB sticks is problematic when using eSATA drives like the OCZ Throttle or Maxell SSD, they physically have the size of USB keys but they are recognized like HDD SSD drives and because WinSetup is looking for trus USB pen, I can't have my eSATA drives detected to install properly
But yet I have found a workaround which is to mount a real usb drive, then WinSetup set the drive letter correctly, and the workarounds come here, I'm uplugging the USB pen, plugging the eSATA pen, I set the same drive letter in Wiundows that the USB pen had and then WinSetup thinks it is copying on USB but in reality this is my eSATA drives
Else I have tested with Win7 x64 install after an XP x64 installed at dual booting, all went fine except it wrote the boot informations to my eSATA drives instead of my real HDD byt anyway I dont care to have this fixed this is easly doable now with bootsector /NT60 all
Id like to show you how fast it is to install windows with your WinSetup application from a eSATA drives on RAID0, its soooooooooo fast I love you so much
0 -
I got the USB stick to boot and 2003 x64 installed in 18 minutes (slow usb and old machine), hoping it will be faster with my new Voyager GT and some nice new servers...
May I suggest you instead of that Voyager GT something pwning it
Both keys I have speedtested in a very long speedtest thread
Maxell SSD, OCZ Throttles, only in USB mode it pwns the fastest USB key GT included and in eSATA mode no comments ...
0 -
I have managed to temporarily finish my XP X64 SP2 setup 100% done here.
1) TXT setup
2) with a famous bootcd copying install partition from hd0 to an unpartitioned space on h1 our destination windows with partition magic 8 for dos, dont hide and dont set active the newly created part, it will be D: on GUI setup
3) GUI Setup works as on XP X32 SP3, no invalid paths warnings, cmd prompt is in D: so pushd D: worked
4) Im yet inside X64 and all my past problems solved, IE windowsupdate and all other missing stufffs I had reported are installed correctly now
In case you do not find a workaround dude that maybe enough to code a warning that on X64 you have to copy files between TXTsetup and GUI, it does not requires more hacks because I haven't edited at your files and it worked perfectly as for the 32bit version
0 -
I have partially solutionned the last problem with your last version ilko
for XP SP3 32bit, files copy + boot + txt setup ok, gui setup ok, installation 100% ok
for XP SP2 64bit, files copy + boot + txt setup ok, gui setup wrong path and installation uncomplete, missing inf registration, unstable os
XP x64 still has a wrong srcpath = \??\\WIN_SETUP\XP_x64\, it should be \\?\GLOBALROOT\Device\Harddisk1\Partition1\WIN_SETUP\XP_x64\AMD64 nor according to XP you are expecting D: to host it but thats not the case here I have checked all letters at setup gui boot they are all unaccessible
I have found out that it is linked to your precmd script and 64bit version because on xp 32bit your "pushd D:" correctly mounts the installation files to D: but under 64bit D: is accessible later during the Device setup when 34 minutes lasts, there is no possible ways to get install files from a drive letter at the very beginning of setup gui unlike xp 32bit.
Thats probably why I get all these .inf problems because in the background, windows stores this wrong path for a later use and it does not alert if the path is wrong, it passes over giving an uncomplete and unstable Xp 64bit
The way you setup src path is to review I think
presetup.log
srcpath = \??\\WIN_SETUP\XP_x64\
regopt.log
************************************************************
Region and Languages Options Unattended Mode Log
************************************************************
/f:"C:\WINDOWS\system32\$winnt$.inf" /s:"GLOBALROOT\??\\WIN_SETUP\XP_X64\AMD64"
Switch /F detected!
Switch /S detected!
In setup mode!
The unattended mode file path is: \$winnt$.inf
Supplemental Language Support installation cancelled - The operation was canceled by the user.
************************************************************
Region and Languages Options Unattended Mode Log
************************************************************
/I /s:"GLOBALROOT\??\\WIN_SETUP\XP_X64\AMD64"
Switch /I detected!
Switch /S detected!
In setup mode!setupact.log
The external program RUNDLL32 shell32,Control_RunDLL intl.cpl,,/f:"C:\WINDOWS\system32\$winnt$.inf" /s:"GLOBALROOT\??\\WIN_SETUP\XP_X64\AMD64" returned exit code 0.
Setup aborted processing the file queue because of the following error:
The operation completed successfully.0 -
yet testing a XP SP3 32bit in Qemu 0.11.x and virtual 10GB hdd, NTFS Primary Active partition for WinSetup files on hd0 and C: destination partition on the hd1 (been able to get C: that way good job
)All seems fine until the Setup GUI is reached, is returned an unknown path
GLOBALROOT\Device\Harddisk0\Partition1\WIN_SETUP\XP\I386
which is fixed just by adding \\?\ in front of the path, that way
\\?\GLOBALROOT\Device\Harddisk0\Partition1\WIN_SETUP\XP\I386
I have to repeat that ~30 times and the next parts of the install goes fine
At least I'm sure you should add \\?\ somewhere ilko because I have noted this small problem since the beginning of your project when it was called USB_MultiBoot_10
0 -
I confirm the .iso is created with new version now
I will do further test later I should go out to see a friend but as far I can see yet in logs it looks all good, the ERROR message is removed aswell2009/11/20 21:18:05- Copying completed. Took: 411.64418913577 seconds
2009/11/20 21:18:05- Creating boot ISO
2009/11/20 21:18:05- Launching MkMigrateInf4.cmd
2009/11/20 21:18:06- Ensuring presetup is launched
2009/11/20 21:18:06- setupORG.exe not found, replacing the original file
2009/11/20 21:18:06- mkisofs.exe -iso-level 4 -volid ""WIN_SETUP"" -R -o C:\WinSetup\temp\XP_x64 C:\WinSetup\temp\
2009/11/20 21:18:09- Checking sizes...
2009/11/20 21:18:09- Total source size- 0 MB
2009/11/20 21:18:09- Target space available- 27488 MB
2009/11/20 21:18:09- Getting USB drives informationKeep it up that very helpful script , saves DVD and thats faster, good for the planet
0 -
how stupid Im, I should have tested to run mkisofs.exe before writing
This is just cygwin1.dll missing
"This application has failed to start because cygwin1.dll was not found"
Else I have shortened paths and exe name but the log didnt changed, I think that is just about the missing cygwin lib I dont have it Im much with mingw liter
so a workaround would be to find a mkisofs not cygwin-ed nor to include the lib.
0 -
ilko, there is something wrong with WinSetupFromUSB_0-2-4 which seems the source of my problem with the past version < 0.2.4 which I had explained here in the actual latest post
bug:
2009/11/20 13:02:07- Creating boot ISO
2009/11/20 13:02:07- Launching MkMigrateInf4.cmd
2009/11/20 13:02:07- ERROR!!!--- Could not create migrate.inf
2009/11/20 13:02:08- Ensuring presetup is launchedin your TEMP folder stands the files ready to be packed as .iso + migrate.inf
Result in: no iso created and the job is not 100% done.
I attach the 0.2.4 log file to this post, I can also add Im trying with a XP64 SP2 sleapstreamed, nothing ripped, on an Active FAT32 partition from USB HDD eSATA only connected in USB mode, and in WinSetupFromUSB im forced to use "Force Target Disk Type" => removable because there is no rdummy.sys for x64.
USE 7-zip to unpack the attached log file
0 -
In case of 64-bit only TXTSETUP.SIF stays in I386, the other 2 files go in \AMD64\.I'm using -graft-points to create the ISO file. Files are read from USB drive.
\WIN_SETUP\mkiso.cmd
set win_root=%~dp0
set win_files=XP_x64
mkisofs.exe -graft-points -o %win_root%/%win_files%.ISO ^
/I386/SETUPLDR.BIN=%win_root%\%win_files%\I386\SETUPLDR.BIN ^
/I386/NTDETECT.COM=%win_root%\%win_files%\I386\NTDETECT.COM ^
/AMD64/TXTSETUP.SIF=%win_root%\%win_files%\AMD64\TXTSETUP.SIFme confused so who is right about the file locations?
I think ilko is wrong saying TXTSETUP staying in I386 because the default location of this files in an official iso are where wrote cdob
0 -
thank you ilko will look at this method.
I dunno if its coming from winsetupfromusb but on 3x install of WinXP x64 I fall always on the same problems, it seems windows does not install 100% fine
-No windows update I had to rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 %systemroot%\inf\au.inf toinstall it
-No Keyboard languages, I had to rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 %systemroot%\inf\qmgr.inf
-No start menu advanced settings, I had to rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 %systemroot%\inf\shell.inf
-sound is not working even with the right drivers installed
even more .inf not regged but they are all present on the partition
My XP is nlite (without rips, just SP2 sleapstreamed) but I have already installed from nlited CDs without getting such problem in the past so I think it comes from the winsetupfromusb conversion.
I have carefully checked the TXTSETUP.sif from the original iso with the one from you tool, there is just 3 differences,
binifix5.cmd=1,,,,,,,82,0,0presetup.cmd=1,,,,,,,82,0,0
setupORG.exe=1,,,,,,,82,0,0
setupORG.exe doesnt seems to do the same job than the original one
0 -
ha yeah sorry this is the logical volume I mean to set active
1 Extended Partition + 1 Logical volume
&
1 really small primary partition like 100Mb and active
Forget about the Logical volume made active, I just tested again with a small primary partition made active and this was enough to have winsetupfromusb detecting the USB hdd
To resume how I do it:
1) my usb stick has no partition
2) doing 1Gb extended partition
3) inside a 1Gb logical volume
4) a small 100Mb primary partition inside the unpartitioned space
5) set active the primary partition
6) installing grub though grubinst
7) Copying XP setup on logical volume through your SetupwinfromUSB program
8) moving some boot files from the primary part to logical drive
9) deleting primary partition
At this point the install hdd is ok
10) copying HBCD from Hiren's BootCD 10.0 iso to logical drive
11) adding the code below to menu.lst
At this point the install hdd is ok + hiren boot cd to install the loaders to our futur C:
then I reboot
12) TXT setup
13) to the partitioning options you should see only ONE partition, our USB HDD (logical volume) is shown down with a letter D:
14) create the C: partition to your disk (should be shown first)
15) create a small partition inside the unpartitioned space of your usbhdd (windows will tell you it anyway because it refuses to write boot files to a logical volume)
Then to the reboot, poweroff, reinstall grubinst to the USB HDD, reboot with it and the second step starts
Setup may then warn you it fails at finding HarddiskVolume2, just set instead Harddisk1/Partition2 and its works perfectly
finally copy boot file from the small primary partition you created during setup and install an MBR to the C: with Hiren bootcd.
Hope it helps I made that quickly I need to eat
so yesterday I had done to get the logical volume detected in setupwinfromusb tool without having to create a fake primary part and moving boot files but can't remember yet how I did, will post if I remember
0 -
Hi guys, small contribution:
-I have verified that this is possible to install Win x64 from an USB HDD + 1 Extended Partition & 1 Logical Drive + it works around XP setup "stealing" C:
Tips:
1)
-with diskpart, set the logical partition active
-create a temp primary partition very small and set it active
after that done, WinSetupFromUSB_0-2-3 will detect the logical drive so you can deploy your installation on it
-don't forget to delete the temp primary partition (this one is just needed for WinSetupFromUSB and this could be a problem after because this partition will still your the C: drive letter)
2)
-make sure you just have your USB HDD plugged in your comp and no existing primary partition, start WIndows Setup and when to the partionning page you should see the destination drive first unpartitionned, and second place for your USB drive with a D: assigned to your logical partition
-create your destination partition, C: will be applied to it
-create a partition in an unpartitioned area of your usb hdd so win write boot files inside
Then some small boot fix and that is done, better to have 2 comp on that method but without thats not possible to assign C because setup files are on a primary partition so thats technically not possible to use C: because Windows assigns C to the USB HDD
It seems Windows installs fine from a logical drive and auto assign D: to it, refusing to assign C: to a logical part to our benefit
Verified with a nlited XP x64
Sorry for my crap english guys Im french
0
How to install Windows from USB- WinSetupFromUSB with GUI
in Install Windows from USB
Posted · Edited by class101
sorry for the late reply ilko, but busy, I will do this tommorrow once back at work
//EDIT1
Machine dxdiag is attached
Summary
Key: Maxell SSD 32Gb eSATA link
Forgot Bios stuffs, will watch them Monday
DxDiag.txt