
ilko_t
PatronContent Type
Profiles
Forums
Events
Everything posted by ilko_t
-
Here is a version, which does not check for and install grub4dos MBR. It will copy the needed file to the partition selected. You need to find a way to chainload grldr in this partition. If it's FAT32/NTFS and set active, and your MBR will start this active partition, you may rename grldr to ntldr if formatted with 2000/XP/2003 bootsector, in case of Vista and above bootsector- rename grldr to bootmgr. Alternatively, if supported at all, you may install grub4dos bootsector using the utilities in \files\grub4dos\ folder, Grubinst_GUI.exe or the command line grubinst.exe. http://www.datafilehost.com/download-7345a923.html If disk space is concern- you may use NTFS and the included in \files\tools\DFHL.exe to create hard links once you put all windows XP/2003/2000 versions. http://www.jensscheffler.de/dfhl Let us know how it goes, this is interesting stuff.
-
@barnai When you boot from USB and get to grub4dos menus, before you select anything else, press "c" to enter command prompt. Then enter: find /winsetup.lstWhat's the result returned? As for the mapping- re-mapping is valid, the information is gathered during real mode and passed to the setup as we modified it. There is no further rescanning. Thus grub4dos mapping survives, serving our needs perfectly BTW- what's the motherboard model if it is a desktop? If laptop- what's the exact model?
-
I have no idea what would happen with GPT formatted disks since the program is installing grub4dos MBR. Does grub4dos MBR like such formatted disk? Reading here too: http://www.microsoft.com/whdc/device/storage/GPT-on-x64.mspx If you have no valuable data you may try, but be ready for reformat it and lose whatever data is on it. As for the question- The setup would work just fine from another partition using the method latest WinSetupFromUSB uses, as long as it's primary one. But you need to have a properly formatted bootable disk. Out of curiosity- why this disk is formatted like this? What advantages does this give you, compared to a regularly formatted disk?
-
What drive type is this? USB stick, hard disk, memory card...? Do you need this hidden partition, if it is such at all? Usually all vendors have a tool to unlock and erase this partition, as last resort. Is the first, hidden partition primary? Is the second, visible partition primary? Which one is active? The new beta of WinSetupFromUSB should work just fine from another partition, but we need to ensure Windows setup will "like" your drive first and see the second partition. http://www.msfn.org/board/install-2000-xp-...p;view=findpost
-
Try this line in winsetup.lst first: Change map (fd0) (hd1) to map (fd0) (hd1,0) and test. Next, if still no luck- can you rebuild the ISO file in \WIN_SETUP directory? Have the tools? UltraISO is the easiest way, next is mkisofs tool. Let me know if you need more details. You'd need to extract txtsetup.sif from it, change this line in SetupData section in it: from BootDevice="multi(0)disk(0)rdisk(1)partition(1)" to BootDevice="multi(0)disk(0)fdisk(0)" and rebuild the ISO with the modified txtsetup.sif. If still no luck try to change SetupSourceDevice=\ArcName\multi(0)disk(0)rdisk(1)partition(1) to SetupSourceDevice=\ArcName\multi(0)disk(0)fdisk(0)as well. You may need to remove the lines map (fd0) (hd1,0) or map (fd0) (hd1) in winsetup.lst. Another combination could be BootDevice="multi(0)disk(0)fdisk(0)partition(1)" SetupSourceDevice=\ArcName\multi(0)disk(0)fdisk(0)partition(1)again without the 'map' lines mentioned in winsetup.lst.
-
Try Bootice, there are also HP USB format utility and PEtoUSB, in folder \tools.
-
Use the latest beta: http://www.datafilehost.com/download-20d0545c.html Extract contents of the archive in C:\ for example, run WinSetupFromUSB inside. Format the USB sick and prepare it with your Windows source. Assuming it's XP. Once finished open up in Notepad h:\winsetup.lst, replace H: with the drive letter of your USB stick. Replace: map (hd0) (hd1) map (hd1) (hd0) with: map (fd0) (hd1)in both places. Save winsetup.lst and ensure it did not end up with .txt extension. Test installation and report with details what happened and on what stage.
-
How about we start PLoP from the hard drive and then start from USB using it? E.g. boot.ini-->grldr-->PLoP floppy image-->USB There might be a better option to start PLoP from ntldr/boot.ini, without grldr in the middle, haven't looked at it's web page for alternatives. There might be needed some adjustments in txtsetup.sif as it uses ARC path to the USB disk and I am not sure if BIOS does not support boot from USB, whether such path will be valid to the USB disk.
-
Install WinXP OEM VLK and RTL using only about 500MB
ilko_t replied to Siginet's topic in Install Windows from USB
Nice one -
@barnai I have a couple of ideas and need someone to test them on such hardware as I can't find such. This would eventually be a workaround for all those cases where BIOS insists on showing the USB stick as a floppy. Wanna give a hand with this?
-
Install 2000/XP/2003 from RAM loaded small ISO
ilko_t replied to ilko_t's topic in Install Windows from USB
Txtsetup.sif amended and usb group starts earlier, thus in case of USB hard disk it's detected and a drive letters given at start of GUI. The rest is as per cdob's last post. -
oembi01.bin = 1,,,,,,,2,0,0,oembios.bintells setup to rename oembi01.bin to oembios.bin while being copied. So alongside the original oembios.bin, you out oembi01.bin for corp, oembi02.bin for vlk and so on and replace in txtsetup.sif oembi01.bin with the desired one. It will be copied to the destination as oembios.bin. No need to create extra folders and 990 directives for the different files. As for winnt.sif- it also could be put on a virtual floppy, mounted by grub4dos. Have a set of floppies gziped and mount whichever you need. Or have a blank floppy image and dd the desired winnt.sif to it. What was wrong with the missing files during GUI part? Using txtsetup.oem as a file name wouldn't be a good idea, it's already hardcoded and read for other purposes, use txtsetup.oen or something similar.
-
Install 2000/XP/2003 from RAM loaded small ISO
ilko_t replied to ilko_t's topic in Install Windows from USB
Beta version of WinSetupFromUSB if anyone wants to help testing: http://www.datafilehost.com/download-20d0545c.html edit: Newest download link is in the first post. -
Nice progress, much closer now Not keeping the original info, amend it just as you did.Have you tried the first approach? They are two different, not completing each other. Seems easier to me, plus GUI may find them right away. As for the missing files at GUI- have a look at setup log files in \windows, there could be something interesting. About winnt.sif- I must be wrong then, as I wrote, don't quite recall if it was applied or not, apparently not. For hexediting setupldr.bin for winnt.sif- would work just fine, for 2003 versions checksum check patch is needed: http://unattended.msfn.org/unattended.xp/view/web/16/ Need modifype.exe This may help:http://gosh.msfn.org/txtsetup.htm
-
Is any of them, apart from txtsetup.sif and winnt.sif, loaded and used during text mode? A couple of ideas: 1) Put the second set of files, renamed, alongside the original set. Use txtsetup directives to rename them while being copied, e.g.: [SourceDisksFiles] ... oembi01.bin = 1,,,,,,,2,0,0,oembios.bin oembi01.cat = 1,,,,,,,,3,3,oembios.cat ... etc. etc. 2) Copy them in another directory, and use it instead the original one: [SourceDisksNames.x86] .... 990 = %cdname%,%cdtagfilei%,,\corp 991 = %cdname%,%cdtagfilei%,,\home 992 = %cdname%,%cdtagfilei%,,\oem Then [SourceDisksFiles] ... oembios.bin = 990,,,,,,,2,0,0 oembios.cat = 990,,,,,,,,3,3 ... Since txtsetup.sif is loaded into memory use grub4dos search&replace and change values on the fly. About winnt.sif- can't recall exactly, but I think it's used if present in the small ISO file loaded. More tests are needed. Are those files protected by other means, e.g. layout.sif, checksum check or something similar?
-
Siginet, can you list what files are different? Can't find the topic you mentioned them. I believe this could be easily done via txtsetup.sif, using different source location or source file names for those files.
-
You need to make your USB stick appear as a hard disk, not as a floppy. Some motherboards simply won't do that. Have a look here for ideas: http://www.msfn.org/board/install-xp-usb-c...ro-t135364.html If you do a little search in the subforum you would find several similar posts/threads.
-
Install 2000/XP/2003 from RAM loaded small ISO
ilko_t replied to ilko_t's topic in Install Windows from USB
Thanks cdob. Run a few tests on real hardware with the same USB hard disk, using USB-IDE adapter. Added changes to txtsetup.sif for starting usb group earlier. Left changes to USB at start of GUI as a backup. None of the tested versions (2000-XP-2003 32 and 64 bit) required reboot at start of GUI and installed right to the end. Why did you give up on changing txtsetup.sif? Did you encounter any troubles using it only? -
How to install Windows from USB- WinSetupFromUSB with GUI
ilko_t replied to ilko_t's topic in Install Windows from USB
This is very interesting. Did you install from USB hard disk? Do you start Windows with USB disk inserted? Does it hang if you start without USB disk inserted? Open command prompt, what's the result of sc query rdummy If you see it installed, issue "sc delete rdummy" and reboot. Does that fix your problem? This is the only one I can think of, although there have not been any similar reports yet. -
It might take long, on motherboards which boot USB on 1.1 or lower speed. In other words you may need to wait like 10-15 minutes. You may try first booting Plop and then warm booting USB again, in order to get 2.0 speed: http://www.boot-land.net/forums/index.php?showtopic=8605 Mind you, it's picky
-
Which on is the active partition? Setup expects to find its boot files on the first partition, which is active, said for simplicity, details: http://www.msfn.org/board/usb-multiboot-se...ck-t129454.html http://www.msfn.org/board/xp-source-2nd-pa...pid-837621.html What prevents you to start Setup from the first partition, but once on the partitioning screen to select the second one as destination? You'd have to remove completely the unattended section in the answer file, or it will start installing right away in the partition where the temporary folders (~BT and ~LS) are, without getting you to the partition selection screen. Exception is if there is not enough space on that partition as per values in txtsetup.sif, in this case Setup will throw an error for not enough space and let you choose another partition, sending you back to the partitioning screen. I recall a few other switches in winnt32.exe, which may allow source files to be elsewhere, not tested, use winnt32.exe /?.
-
How to install Windows from USB- WinSetupFromUSB with GUI
ilko_t replied to ilko_t's topic in Install Windows from USB
It may seem as frozen if it was copying a large file, and this is what appears from your log file- it did start copying. Did you give it a chance to continue? How long did you wait for it? -
@Ognjeni If you are booting the second stage (GUI mode) from the USB stick, you'd need to modify BOTT.INI on the USB stick, NOT on the local hard disk. Check FAQs as well: http://www.msfn.org/board/faqs-t116766.html Q4/A4
-
Install 2000/XP/2003 from RAM loaded small ISO
ilko_t replied to ilko_t's topic in Install Windows from USB
You've basically run into the problem we are trying to resolve since the beginning Yes, 64 bit versions do not mount and give drive letter to the USB drive early and this is the main problem. This leads to all kind la problems- every application during GUI, expecting a drive letter fails. Getting around this, using \\?\GLOBALROOT\Device\Harddisk1\Partition1\WIN_SETUP\XP_x64\AMD64 is not a solution, for example BTS driver pack will not install too, it expects to find the drive letter of the CD(USB) drive and extract files from there. srcpath = \??\\WIN_SETUP\XP_x64\ in presetup.log is a clear indication, that drive letter for the USB drive was not found. Look at presetup.cmd- srcpath = \??\%CDDRIVE%\...... in this case %CDDRIVE% was null. Srcpath should have been \??\D:\WIN_SETUP\XP_x64\, which is later (right after real setup is launched) translated to D:\WIN_SETUP\XP_x64\, saved as the value of dospath in $winnt$.inf and used for the rest of the setup. Pushd uses %CDDRIVE% variable too, but in this case it pushes nothing. Yesterday I managed to recreate the problem on 32 bit XP SP3 and another computer, using USB hard disk- same problem, USB partitions not mounted. Setup transferred to USB stick- everything normal, on the very same machine. The difference with 64 bit versions (2003 in particular), was that in XP 32 bit diskpart showed USB partitions as volumes, and I could assign a drive letter, whereas in 2003 x64 those volumes were not present at all. Played with BIOS setting how USB boot is performed- via a hotkey or hard coded in boot order- no difference. Tried also to start GUI from the internal disk directly changing BIOS settings as well- again no luck. You can play with that- when you see the error message asking for the source files hit SHIFT + F10 and start DISKPART, then issue "LIST VOL". This is still in experimental stage, looks quite promising method, avoiding all the limitations of the other methods, but still has to be fully explored. Have quite busy days at work, and although it's driving me nuts to find out what's happening exactly, will have to postpone tests for a while. -
Install 2000/XP/2003 from RAM loaded small ISO
ilko_t replied to ilko_t's topic in Install Windows from USB
Uploaded a new version. Fixsrcpath.exe does not work that early in XP 32 bit, fixsrcpath.cmd is used instead. For 64-bit the exe is used. @class101 The reason it didn't work is above, please use the new version. Adding \\?\ at front is a nice idea, I'll play with that a bit. As for USB-multiboot- it does not use any of this stuff, modifying boot and source paths, so no idea what exactly you have in mind.