Jump to content

ilko_t

Patron
  • Posts

    1,720
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by ilko_t

  1. If you have a chance when the error appears press shift+F10 to open CMD window. There you can type: type %systemroot%\winsetup.log or even copy it to USB stick if it is still available: copy %systemroot%\winsetup.log U:\
  2. Can you check and attach \windows\winsetup.log, from the machine where Windows is being installed to? Have you tried the same USB stick and setup on another machine? Try also to edit setup.cmd in G:\WINSETUP\XPpSP2\I386\ and change rem start /min "USB keep mounted work arround, do NOT close!" pushd %CDDRIVE% to start /min "USB keep mounted work arround, do NOT close!" pushd %CDDRIVE% What is the machine in question? Laptop, desktop? What model/motherboard model?
  3. There shouldn't be a reason for that, apart from disk not properly formatted. Format it with the tools included and it would show up. If does not- please post WinSetupFromUSB.log file in program's directory.It would not appear in the previous versions as well, if it's not properly formatted, even the previous versions are more restrictive- an active partition is required too. Well, the file you posted seems corrupted, you'd need to find out why yourself.And you do have it in the CD, look again.
  4. @comt Your txtsetup.sif is corrupted, it's full of weird characters, bad download or something. Check the original source if it's corrupted too and find another source, you may have other files broken. And use later versions, even betas, 0.1.1 is quite outdated, a lot has been improved since it. @Siginet I guess you will understand this- assume the following snippet: $CurSelPrimPartLetter = "K:" If Not FileExists($CurSelPrimPartLetter & "\grldr") Then FileCopy(@ScriptDir & "\files\grub4dos\grldr", $CurSelPrimPartLetter, 1) EndIf If you execute it from within K:, grldr will end up in @ScriptDir and FileCopy will return "Success", if executed from any other drive than K:, it will go to root of K:, that's why it was not noticed for long time. Thanks for the good catch, I'd never have guessed to test the program from the same USB drive
  5. Could you attach txtsetup.sif and mention which line exactly is mentioned? Which tutorial? On every attempt for setup the line number changes? Is that what you mean?Do you have problems with other Windows sources? What program and version are you using?
  6. Multiple 2000/XP/2003 is fine, when program completes just select the next source and GO, everything is done automatically, no need to relaunch the program. Multiple PE type (BartPE, UBCD4Win, WinFLPC, WinBuilder) in the same partition- no. Multiple Vista/7/Server 2008 in the same partition- no. All this is actually in the first post in this thread, please refer to it Mind you, most if not all modern machines support USB 2.0, but many (still) boot from USB on lower speeds, USB 1.1 etc. Once USB driver takes control, you are flying again.A few years back I wrote to Gigabyte's tech support asking them why and if they had intentions to start supporting USB 2.0 boot in several motherboards- after several emails, until we clear up what the issue actually was, I was told "sorry, we have no plans to make changes in order to support USB 2.0 boot". I guess, if there is enough interest and pressure from customers, they will start thinking in this direction, eventually.
  7. It's a bug which shows up only if the program is placed in the same disk and partition, which is being prepared. Going to fix it in a few hours and post beta4 on the first page. Thank, nice catch, it's been like this since the first versions of the program and there were no reports for it. I guess very few people place the program on the USB disk they are preparing for installation
  8. I am afraid I won't be able to track this down without a log file. I've checked the code numerous times and tested latest betas on many computers with XP and 7 x64, none gave similar issue.
  9. Why are we mentioning boot.ini and Vista/7 ? They use BCD instead, boot.ini is the configuration file for NTLDR in NT-2003. http://msdn.microsoft.com/en-us/library/aa468626.aspx
  10. Most likely both machines support booting from USB on lower speeds, not 2.0. Have you tried loading PLoP boot manager first, selecting USB in its menu and then starting the Setup again?
  11. It's not Windows issue at all The problem is with not paying attention to the messages: Note the bolded part: Now reading your report: Did you miss something? What you posted is boot.ini on the USB disk, but you were starting from the internal disk...
  12. Hmm, very weird. Can you attach WinSetupFromUSB.log ?
  13. Did you try beta4? The character E shouldn't cause a problem.
  14. This is exactly what that method does- whole ISO is in memory, but in order to survive when protected mode kicks in, a driver is used- firadisk: http://www.boot-land.net/forums/index.php?showtopic=8804 OEM folder can go elsewhere, off the ISO, as long as it's findable at start of GUI mode.
  15. You might be better off using this method: http://www.msfn.org/board/7-t137714.html Should get you past all these errors as long as grub4dos finds the ISO file, but I've had no luck with Firadisk and anything but XP 32 bit, MCE should be alright too. Apparently Setup gets confused about this partitioning and throws those errors. With RAM disk method this will not be relevant, as all needed files are on a virtual CD.
  16. Do you have productname and spcdname values there?
  17. The one just above, without map (hd0) (hd1) and with rdisk(0) as ARC path.
  18. Thanks for this, a few thins have to be corrected, I need Strings section of various other languages to be able to make it compatible. Please post Strings section of txtsetup.sif. Added: Attached version should do the trick, just put it alongside the old exe and run it. Please test and let me know. WinSetupFromUSB.log file would be very helpful, along with Strings section from txtsetup.sif. WinSetupFromUSB_1_0_beta4.zip
  19. Try reformatting it with BootIce, FAT32 or NTFS, single or multiple partitions. You'd have to experiment a bit to find out which one works in your setup. There is no "universal" set of settings.
  20. title Install XP MCE Retail find --set-root /windefault map --mem /WIN_SETUP/XP_MCE_Retail.ISO (0xff) map (hd0,1) (hd0,2) map --hook root (0xff) chainloader /I386/SETUPLDR.BIN SetupSourceDevice=\ArcName\multi(0)disk(0)rdisk(0)partition(2) BootDevice="multi(0)disk(0)rdisk(0)partition(2)" I guess BootPath is correct, right?
  21. I guess I'd have to add an advanced settings page
  22. Try this: title Install XP MCE Retail find --set-root /windefault map --mem /WIN_SETUP/XP_MCE_Retail.ISO (0xff) map (hd0) (hd1) map (hd1) (hd0) map (hd1,1) (hd1,2) map --hook root (0xff) chainloader /I386/SETUPLDR.BIN or this: title Install XP MCE Retail find --set-root /windefault map --mem /WIN_SETUP/XP_MCE_Retail.ISO (0xff) map (hd0) (hd1) map (hd1) (hd0) map --hook map (hd1,1) (hd1,2) map --rehook root (0xff) chainloader /I386/SETUPLDR.BIN txtsetup.sif: SetupSourceDevice=\ArcName\multi(0)disk(0)rdisk(1)partition(2) BootDevice="multi(0)disk(0)rdisk(1)partition(2)" or SetupSourceDevice=\ArcName\multi(0)disk(0)rdisk(1)partition(1) BootDevice="multi(0)disk(0)rdisk(1)partition(1)" or SetupSourceDevice=\ArcName\multi(0)disk(0)rdisk(1)partition(2) BootDevice="multi(0)disk(0)rdisk(1)partition(1)" BootPath and SetupSourcePath are not changed, leave them as they are.
  23. What about if we map (hd1,1) to (hd1,2) if WIN_SETUP is in (hd1,0) after making hd0 as hd1, so both partitions have the same contents Check in grub4dos prompt where winsetup directory is: find /WIN_SETUP/XP_MCE_Retail.ISOuse tab to auto complete names. You would have something like this: if WIN_SETUP directory is found in (hd1,1) or map (hd1,2) (hd1,1), if WIN_SETUP directory is found in (hd1,2).
  24. What's the error code on the blue screen? This is the important part If it is 0x0000007B try the modified ntdetect.com : http://www.msfn.org/board/faqs-t116766.html Q3/A3 I've tried to put "codebox" tags around the log you posted, but weirdly the entire log disappeared. Please when posting such large text, put [code-box]large text[/code-box] around it. Remove the dash of course.
×
×
  • Create New...