Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by ilko_t

  1. The posted method works and is tested working. Just follow the instructions.The one in QEMU, which is included with WinSetupFromUSB and presents the USB disk as a IDE one is also working, but the included HD image file test.img, which is the second hard disk, is a small one, only for a quick test. You can safely replace it with as big as you need your hard disk size to be. fsutil file createnew test.img filesize_in_bytesGood idea is to make filesize_in_bytes multiple of 512 or easier to calculate of 1024 to avoid warning messages from grub4dos for example. QEMU directory with test.img file used is in WinSetup_program_directory\files\tools\RMPrepUSB\QEMU. Then you can use StartFromUSB_WinSetup.bat in the same directory, or the QEMU option in the program to launch QEMU.
  2. There are several log files for the different parts of setup process. https://www.google.com/search?source=ig&hl=en&rlz=1G1GGLQ_ENXX251&q=windows+xp+setup+log+files&oq=windows+xp+setup+log+files&aq=f&aqi=g1g-b1g-bK1g-q1&aql=&gs_l=igoogle.3..0j0i8j0i8i30j0i22.546436.551738.0.551987. http://www.windowsitpro.com/article/installation2/what-log-files-does-windows-xp-create-during-installation-
  3. Just tested same scenario with reduced winnt.sif in VMWare Player as a regular USB boot and all worked fine, XP SP3 MSDN. ... G:\WINSETUP\XPpSP3.ISO G:\WINSETUP\XPpSP3\$OEM$ G:\WINSETUP\XPpSP3\AUTORUN.INF G:\WINSETUP\XPpSP3\DOCS G:\WINSETUP\XPpSP3\DOTNETFX G:\WINSETUP\XPpSP3\I386 G:\WINSETUP\XPpSP3\README.HTM G:\WINSETUP\XPpSP3\SETUP.EXE G:\WINSETUP\XPpSP3\SETUPXP.HTM G:\WINSETUP\XPpSP3\SUPPORT G:\WINSETUP\XPpSP3\VALUEADD G:\WINSETUP\XPpSP3\WIN51 G:\WINSETUP\XPpSP3\WIN51IP G:\WINSETUP\XPpSP3\WIN51IP.SP3 G:\WINSETUP\XPpSP3\$OEM$\$1 G:\WINSETUP\XPpSP3\$OEM$\cmdlines.txt G:\WINSETUP\XPpSP3\$OEM$\regkeys.reg G:\WINSETUP\XPpSP3\$OEM$\$1\tagfile_in$1.txt ... cmdlines.txt: [COMMANDS] "CMD.EXE /C echo TEST > C:\TEST1.TXT" "CMD.EXE /C echo TEST > C:\TEST2.TXT" "REGEDT32.EXE /S regkeys.reg" regkeys.reg: Windows Registry Editor Version 5.00 ; Enable Basic Authentification f.e. for WebDAV [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters] "Test"="Yes" tagfile_in$1.txt is non-empty one, or it gets deleted from source when copied. winnt.sif in i386: [data] msdosinitiated="0" AutoPartition="0" win9xupgrade="no" winntupgrade="no" EulaComplete="1" UnattendedInstall=Yes Floppyless=1 AutomaticUpdates=Yes [Unattended] OemPreinstall=Yes OemSkipEula=Yes WaitForReboot=No TargetPath=\WINDOWS DriverSigningPolicy=Ignore ;OemPnPDriversPath="_DRIVERS\ACPI_ATK0110;_DRIVERS\Atheros_LAN;_DRIVERS\ATI_Display;_DRIVERS\ATI_HDMI_Audio;_DRIVERS\ATI_SMBus;_DRIVERS\DLink_DWL-G122_revC1;_DRIVERS\Intel_Chipset;_DRIVERS\Intel_Grafik;_DRIVERS\Intel_HDMI_Audio;_DRIVERS\Intel_SATA;_DRIVERS\MitsubishiCP9550DW;_DRIVERS\MSI-US300EX;_DRIVERS\Nvidia_Away;_DRIVERS\Nvidia_Display;_DRIVERS\Nvidia_HDAudio;_DRIVERS\Nvidia_LAN;_DRIVERS\Nvidia_SATA;_DRIVERS\Nvidia_SMBUS;_DRIVERS\Nvidia_SMU;_DRIVERS\Realtek_AC97;_DRIVERS\Realtek_HD_Audio;_DRIVERS\Realtek_LAN_PCI;_DRIVERS\Realtek_LAN_PCI-E;_DRIVERS\SIS_Grafik;_DRIVERS\TP-Link_TL-WN721N;_DRIVERS\VIA_HD_Audio" UnattendMode=FullUnattended UnattendSwitch="Yes" [UserData] ProductKey = "xxxxx-xxxxx-xxxxx-xxxxx-xxxxx" FullName="Home User" OrgName="Home" ComputerName=HomeComputer [GuiUnattended] AdminPassword="1234" EncryptedAdminPassword=No AutoLogon=Yes I'd start with winnt.sif, compare differences and check if and where it gets broken. Next check setup log files in Windows directory for clues.
  4. Yes. What is bothering you? There are tooltips on each element of the GUI giving brief information what this button/option is for. You can also always ask here if something is not clear. As for tutorials, most of the ones in i-net for beta7 should be relevant, except of the few new options. You will have more detailed...
  5. Try replacing these lines in winsetup.lst: title Load F6 SATA/RAID/SCSI drivers from ahci.img\nSelect once before Text mode of Setup map --unmap=0:0xff && map --unhook && map --rehook set FLPIMG=/WINSETUP/ahci.img ls %FLPIMG% > nul || find --set-root --devices=hf %FLPIMG% > nul map --mem %FLPIMG% (fd1) map --mem (md)0x6000+800 (fd0) map --hook dd if=(fd1) of=(fd0) count=1 set DPMS=1 ls /usbdrive.tag > nul || find --set-root --devices=hf /usbdrive.tag > nul configfile /winsetup.lst #F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6# #DO NOT REMOVE THESE LINES with: title Load F6 SATA/RAID/SCSI drivers from ahci.img\nSelect once before Text mode of Setup map --unmap=0:0xff && map --unhook && map --rehook set FLPIMG=/WINSETUP/ahci.img ls %FLPIMG% > nul || find --set-root --devices=hf %FLPIMG% > nul map --mem %FLPIMG% (fd1) map --mem %FLPIMG% (fd0) map --hook set DPMS=1 ls /usbdrive.tag > nul || find --set-root --devices=hf /usbdrive.tag > nul configfile /winsetup.lst #F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6##F6# #DO NOT REMOVE THESE LINES If doesn't work- remove the line: map --mem %FLPIMG% (fd1) In addition- Setup auto loads from the virtual floppy image only default driver as stated in txtsetup.oem, if floppy image contain multiple drives as in this case. Try pressing F6 and select the appropriate driver. Or edit txtsetup.oem, read around this post for details: Just tested your file with the above changes on Dell Latitude E6400 in AHCI mode, this requires iastor7 from BTS mass storage DP, VEN_8086&DEV_2929. Pressed F6, then S, selected "Intel® ICH9M-E/M SATA AHCI Controller" and Text mode loaded fine to the partition screen displaying the internal disk too. Can't test further, this is a work machine.
  6. @dadaniel I am getting it, there is mismatch, Text mode uses, create such service and copies iastor7.sys, PNP detection in GUI mode replaces it with iastor.sys as in the inf file, the file is missing, hence the error and BSOD on first reboot. This is to be taken care of, will see what I can do. As for the floppy image- can you post contents of it with txtsetup.oem included?
  7. Attached are another 2 test versions, please run them the same way. If none of them work, then there must be something broken in regards to WMI on this machine. Can't make much sense of the first error reported, that's something new to me, but most likely it has something to do with restricted or broken access to WMI due to corrupted WMI or access restrictions via group policy, domain restrictions or something along these lines, cannot comment further reading these errors for now. Note: If this is a workstation used for work I wouldn't go further as it could become tricky and messy. The next diagnostic tool may be doing changes and fixes as it runs, never used it before. Can you start a new thread, to not overload this one as issue doesn't seem to be program related, and post the log file from Microsoft's WMI Diagnosis Utility, hopefully could spot something interesting in it : http://www.microsoft.com/en-us/download/details.aspx?id=7684 Hey ilko_t, Do you remember #1687? I've just tried your new test version and it seems to run in Windows 2000. Thanks for the report, this error handling will go into the next version. Meanwhile you could safely use this test version, it's beta8 with a few extra lines for COM error handling. WinSetupFromUSB_1-0-beta8_testWMI2.7z WinSetupFromUSB_1-0-beta8_testWMI3.7z
  8. Attached is a test version, please place it next to the original file from 1.0 beta8 and run it. Post back the log file produced in program directory, winsetupfromusb.log. WinSetupFromUSB_1-0-beta8_testWMI.7z
  9. Does setup continue despite this error? Is iastor.sys present in \system32\drivers when this error comes up? Shift+F10 when it shows up and cd/dir to the drivers folder to find out. Is this a modified Windows source? Any mass storage drivers included in it? It's not supposed to be. Can you elaborate? Where is no option, in boot menu? Did you use the option in the program?
  10. This is interesting, haven't had any similar reports yet. Will prepare a test version for you with some mode debug information in a few days, please keep an eye on this topic for updates. By the way- what is full computer/host name as result from the command "hostname" in command prompt?
  11. http://www.upan.cc/tools/mass/Innostor/ http://www.upan.cc/tools/mass/Innostor/2012/IS902E_V203.html http://ap.upan.cc/plus/download.php?open=0&aid=2083&cid=3 Download link is on bottom left. Password is IS0024. But can't see an option to flip the removable bit and this seems to be the newest version of this tool for this chip. Warning- if you decide to play with such tools, it's on your responsibility, you can easily damage the stick. Most likely this will void warranty too. To search for manufacturer tool by keywords, such as VID&PID, controller name, manufacturer etc. etc.Google search also helps, e.g. search terms "IS902E site:flashboot.ru" without the quotes. Google translator is also your friend. But sorry, that's what I could do, seems like back to square one. Hope somebody else gives you better answers.
  12. What version of the program did you use to prepare the USB disk?If beta8, did you use the option "auto format"? If it was not beta8, or if beta8 auto-format was not used, then you have to restore grub4dos MBR. You may use BootIce and process MBR option, then select grub4dos MBR. If it was beta8 and auto-format option then in program directory\files\tools run in command prompt: fbinst --list make note of disk number of the USB disk then replacing X with HD number run; fbinst (hdX) restore
  13. Stock Windows recognizes only first partition on multipartitioned USB removable disk.So you are stuck to the following options as far as I am aware: 1) Use single partition on USb sticks seen as removable disks 2) Use multiple partitions and flip in advance which one is recognized and used by Windows per need. BootIce allows that (Parts manage-->ReFormat USB disk-->Set Accessible), Wimb's USB_Part_Flip also can do it. 3) Flip permanently the removable bit in the controller on the USB stick so it's recognized as fixed disk. This is done using a program from manufacturer of the USB stick. Here is a good starting point. 4) Integrate or start by other means a filter driver (dummydisk, cfadisk, diskmod) in the Windows being installed, so it recognizes the USB stick as fixed(basic) disk and mounts and uses all partitions on it.
  14. Is the removable bit flipped on this USB stick so it shows as a hard/fixed disk? Or are you using a filter driver to show it as a hard disk? If that's the case, the Windows being installed also needs such driver to be able to see the other partitions, not only the first one... Does the same happen when Windows setup files are put in the first partition?
  15. You can put up to 10 for 0.X.X versions and up to 99 for 1.0 versions of Windows 2000/XP/2003 Setup. Just add them one after another the same way you put the first one, nothing special, program does everything needed. No need to restart the program either. All this is also in a tooltip, if you hold the mouse over the Windows XP/2000/2003 Setup checkbox. Similar information is displayed for almost every element in the GUI, it might be a good idea to have a look or two. Read the first post and the links within if you need multiple Vista/7/8/Server 2008 sources in the same partition.
  16. You might also want to try with other Windows sources, as always preferably unmodified ones. Also good idea is to keep the antivirus program turned off while preparing the USB disk.
  17. Most likely you have problem elsewhere- the USB disk, the hardware on the target machine or something relevant. What do you mean? The issues you are experiencing have nothing to do with detecting or not the USB disk, not to mention that during Setup process the program is not running at all, thus is not detecting anything...
  18. Attached is another one, please run it and report if any errors. Modified from here: http://www.activexperts.com/admin/scripts/wmi/vbscript/0054/ disk_drive.vbs.txt
  19. Can you run the VBS script in this post to rule out if WMI on this machine is broken? Does it run properly, no errors etc. ?
  20. What are contents of the ASUS Eee PC disk? Can you list them, screenshots or list of parent directories and files?
  21. Glad you found a good solution. It will be updated in the next version. Meanwhile I have just added it to download list where current version of WinSetupFromUSB is: http://code.google.com/p/winsetupfromusb/downloads/list
  22. You may also use BootIce for example and flip which partition is visible to Windows- Parts Manage-->ReFormat USB disk-->Set Accessible. Still a bit limiting, only one partition visible at a time.
  23. When it stops press shift + F10. Type "notepad" and press enter. In Notepad open the relevant setup log files and look at the last few lines, they might give you a clue what is going wrong: http://www.windowsitpro.com/article/installation2/what-log-files-does-windows-xp-create-during-installation- What operating system is on this machine currently? Does it behave properly? Hardware issue is another possibility. You mention CD drive is broken, try removing it if it is not.
  24. Can you try again preparing the USB disk, but this time using latest 1.0 beta8 version?
  • Create New...