ilko_t

7/Vista setup files cannot be easily put in a subfolder. If you really need to- follow steps outlined here: http://sites.google.com/site/rmprepusb/tutorials/how-to-create-a-usb-drive-that-will-install-vista-win7-and-server-2008

Files to amend with your custom location: 1) menu.lst 2) winsetup.lst 3) txtsetup.sif in the small ISO in \WINSETUP\, section SetupData 4) setup.cmd in \WINSETUP\XP....\I386 5) the one(s) I've forgotten about Are you really bothered by 2 folders on your USB stick ?

Did you happen to use PLoP?

I understood you were going to make your custom files hidden. Which version of WinSetupFromUSB did you use? Folder structure is different between 0.x.x and 1.x versions.

[GUIRUNONCE] "U:\DriverInstaller\DriverInstaller.exe" I would use a cmd script, which finds the USB drive letter and executes whatever you need from it. Add an entry for this script in txtsetup.sif so it gets copied to system32 or wherever. Something like this: I am not so familiar with 7/Vista, but if you don't get an answer here search or ask in the relevant subforums:http://www.msfn.org/board/forum/167-unattended-windows-7server-2008r2/ http://www.msfn.org/board/forum/165-windows-7/ Should cause no problem, just in case, always copy boot files first/prepare the USB drive and add custom files later.

Wow, well done McAfee, guess next step is the scanner to detect itself as a packer For reference I am posting a link to one of the numerous attempts to report false positive to McAfee: https://community.mcafee.com/thread/29747

Download link works just fine from here...

In addition to what Jaclaz is going to instruct you, copy NTDETECT.COM, NTLDR, and BOOT.INI from the USB stick to C: and change rdisk(1) to rdisk(0) in C:\BOOT.INI.

Can you boot to XP using the USB drive? Post a screenshot from disk management.

Thanks for the feedback. Putting it in the to-do list. Well, it's perfectly normal to get these errors if you haven't passed the first part of setup. The point is why it's not showing up.Use either the latest stable 0.2.3 version or even better- 1.0 beta7 and try again. It would be good idea if you only disabled the other internal disk in BIOS to disconnect it, not only disable it.

An this CD image contains PLoP boot manager, which is known and often used in here, also included by default in latest WinSetupFromUSB versions http://www.plop.at/ Thanks for sharing anyway

On more test, try building the stick using WinSetupFromUSB 1.0 beta7 and report what happens.

title EXPERIMENTAL - Start PLoP boot manager\nYou may want to try it if your computer boots from USB slowly.\nOnce booted,select USB from its menu to load USB 2.0 drivers.\nPlease report any issues to its author at www.plop.atls /usbdrive.tag || find --set-root --ignore-cd /usbdrive.tag kernel /plpbt.bin to title Start PLoP boot manager\nYou may want to try it if your computer boots from USB slowly.\nOnce booted,select USB from its menu to load USB 2.0 drivers.\nPlease report any issues to its author - www.plop.at find --set-root --ignore-cd /usbdrive.tag kernel /plpbt.bin and title Start linuxmint-9-lxde-cd-i386 from partition 0 map --unmap=0:0xff map --unhook root (hd0,0) map /linuxmint-9-lxde-cd-i386.iso (0xff) || map --mem /linuxmint-9-lxde-cd-i386.iso (0xff) map --hook root (0xff) configfile /grub4dos.lst || chainloader (0xff) map --unmap=0:0xff to title Linux Mint Lxde9 find --set-root /linuxmint-9-lxde-cd-i386.iso map /linuxmint-9-lxde-cd-i386.iso (0xff) map --hook root (0xff) kernel /casper/vmlinuz file=/cdrom/preseed/mint.seed boot=casper persistent iso-scan/filename=/linuxmint-9-lxde-cd-i386.iso splash initrd /casper/initrd.lz I doubt this has anything to do with PLoP entries, they appear correct. It is the Linux Mint entries which needed changes. The program would not recognise it's an Ubuntu based distro and would make just a generic entries, which would boot ONLY ISOs which are compatible with this method, examples: http://reboot.pro/5041/ Tip- as the program searches for 'buntu' string in the iso file name being added, simply adding this string to the file name of any Ubuntu based distro ISO which support the "iso-scan/filename" kernel parameter, would result in a properly generated entry, as the one you posted. File name must not contain spaces. Of course I have no means to test and include all Ubuntu derivatives and their versions, which support that parameter and search for their ISO file in this location, but reports are always welcome. Error11:Unrecognized device string. You must have missed space after 'root', but anyway, we got what we needed. I'd like this to be confirmed. You are right it didn`t happen without plop. The install without plop works as expected(actually much better than that).It was really fast.it boot the installer slow as expected, but the actual copy of files to the partition was extremely fast(less than 10sec(how is that possible?)) and the second part of the install was very fast too.total install time ~10min.It`s the fastest install time i have ever seen on that PC! So i am stunned. I want to congratulate you again for the great work your doing.I am sorry couldn't `t answer all the questions, but i don`t really see the point of using plop. Was this a slimmed down source Fast, fast, but it shouldn't be that fast. If whole setup worked fine then good, happy to read this. In fact, PLoP would speed up only the initial loading process on slow USB booting machines during XP/2000/2003 Setup, only when loading drivers, after that stage built in OS USB 2.0 drivers take control and one would have full USB speed. There are other scenarios on such machines, say loading big, fragmented, Ubuntu or whatever ISO file in memory, when PLoP would greatly improve speed.

Would you write what exactly you change? Will later today. I am planing to test it today again for you, so if you have more question or need more information please ask now. because the period of actual testing will be short.thank you 1) what entries do you change for PLoP? 2) Was this a USB hard disk? It should work formatting it by disk management. How far did you get when it didn't work? What was the last thing you saw on the screen?If USB stick- yes, you better to use the tools supplied.

Would you write what exactly you change?

I'd like this to be confirmed. There were changes in PLoP version 5.0.11 and it's a bit tricky to figure out what's the right combination of PLoP and WinSetupFromUSB version on a particular machine, hence the capitalized EXPERIMENTAL in PLoP menu title. http://www.plop.at/en/bootmngrusblog.html Previous versions do not need and use ARC paths, with msdosinitiated=1 Setup defaults to using ~BT and ~LS folders and searches for them, this is hardcoded. Default and somehow supported by MS method, which also brings number of nasty limitations, which all were avoided using the small ISO method in the newer versions. Can you elaborate a bit more?

I think that's the case, changed drive mapping leading to wrong ARC paths. Without PLoP, I guess, you could run the first part without errors, although a bit slowly.

If this folder contains a valid source you should be good to use it, on Windows 7 too. Just try 0.2.3 first and if no luck 1.0 beta7 and report back any issues if there are such.

@ Lockszmith Thanks, that's very good usage. In case of large hard disks wouldn't it better to create several GBs primary partition at beginning of the disk and place all those files there? In another partition(s) goes all the rest. Why aren't you using such partitioning?

Have you tried any of the other methods in the pinned topics?

I wiill check it and try to confirm it. Testing on msi gx serie based laptop, which have only ahci enable/disable option in bios. As i am aware IRRT is not suported by hardware. I tried it. 1st part of install pass well, but it fails with a hal error at the boot of 2nd. Not sure if its related to the 'unknown error'... This would be a nice testing machine... 1) Can you check what has been written in boot.ini in the internal disk? You may use some live distro, XP Recovery Console, or even grub4dos: find /boot.iniif the output is like (hd0,1) then type: cat (hd0,1)/boot.ini 2) Did you start from USB for the second part, the GUI mode? 3) Did you use PLoP by any chance? 4) In grub4dos CLI (press "c" when you see boot menu entries) type the following: root ( and press [TAB] right after (, what's the result? geometry (hd99) and [ENTER] , what's the result? find /usbdrive.tag[ENTER] , what's the result?

I guess it won't be fatal error, but that's yet to be confirmed.By the way- on what machine are you testing? Does it have in BIOS an option for the SATA controller called IRRT, alongside IDE and AHCI?

...or make one yourself:http://www.windowsvalley.com/create-windows-7-aio-all-in-one-dvd-or-merge-all-editions-of-windows-7-in-single-dvd/

In addition to the false positive issue and McAfee- even posting in McAfee forum hasn't helped so far, even though a few McAfee staff members replied in it: https://community.mcafee.com/thread/29747?start=0&tstart=0 @sway Do you need help with integrating mass storage drivers? Please open a new thread, this is far out of the scope of this one. Something to get you started: http://www.google.com/search?sourceid=mozclient&num=50&scoring=d&ie=utf-8&oe=utf-8&q=bladder+pain+bloody+urine#sclient=psy&hl=en&q=integrate+sata+drivers+xp&aq=f&aqi=&aql=&oq=&gs_rfai=&pbx=1&fp=9111c1d610a8252 Or an universal solution: http://driverpacks.net/docs/beginners-guide-windows-xp

Program updated to 1.0 beta7, please refer to first post for list of changes and download link.