[ilko_t]

That's a lot better, nice job wimb

A small suggestion- when searching for BTS drivers I think would be better to use another marker, not the directory OEM, as it might be some OEM custom folder. Use DPsFnshr.7z in \OEM\bin or some other file, which definitely belongs to BTS pack. I believe if that file exist, presetup.cmd will exist too.


@all- any ideas how to make USB hard drive to look as removable?
My idea- the removable flag should returned as result by disk.sys or usbstor.sys. If it is written somewhere in registry and we use migrate.inf we may override this result and trick TXT Setup to think that USB disk is not fixed, thus giving it proper letter and position.
I have used similar technique to remove unwanted devices from safely remove hardware by setting device capabilities to 80, from default 64. On restart this setting is lost, because the driver returns the flag, but use reg file to change it on startup and it's fine.
In my case I wanted to remove some hard drives from safely remove list-

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\SCSI\Disk&Ven_SATA&Prod_HDS72251&Rev_\5&b721abc&1&010

http://msdn2.microso...y/aa491648.aspx
http://msdn2.microso...y/ms792967.aspx
http://support.microsoft.com/kb/298504

I was thinking would it be possible similar approach to be used. Any detailed information what exactly Hitachi microfilter does, or Dietmar's dummy.sys? We need the opposite result, but not using filter driver, or if it easy to use such at this point why not...

[jaclaz]

ilko_t said:

I was thinking would it be possible similar approach to be used. Any detailed information what exactly Hitachi microfilter does, or Dietmar's dummy.sys? We need the opposite result, but not using filter driver, or if it easy to use such at this point why not...

A small correction, there is no such thing as a "Dietmar's dummy.sys".

The file is on CodeProject, it's author is Anton Bassov
http://www.codeproje...ect_hooking.asp
and it comes with source code and an article explaining it.

At the time I "found" it and suggested it to Dietmar:
http://www.911cd.net/forums//index.php?sho...181&st=1954
as an alternative to the Hitachi Microdrive one (that has no source code), and Dietmar tested and adopted it.

Now we need someone with programming skills and the correct DDK/Compiler etc.

jaclaz

[ilko_t]

jaclaz, on Aug 29 2007, 05:34 PM, said:

A small correction, there is no such thing as a "Dietmar's dummy.sys"....

Thanks for correction.

jaclaz, on Aug 29 2007, 05:34 PM, said:

Now we need someone with programming skills and the correct DDK/Compiler etc.

Your suggestion is to modify driver to return the opposite result and use it during Text mode right? In this case wouldn't it be difficult to use it at that stage? How do we load lowerfilter drivers via txtsetup.sif?

I did another search in registry for clues, cannot find a single entry which may override the result returned during Text mode. I am still hoping that something is written in registry and programs query that key to get removable status, rather than querying and getting result from usbstor.sys on-the fly. Find that key(s) and use migrate.inf to add it, if possible at all.

BTW source code of Hitachi microfilter driver is included in the download.

[wimb]

ilko_t, on Aug 29 2007, 01:58 PM, said:

A small suggestion- when searching for BTS drivers I think would be better to use another marker, not the directory OEM, as it might be some OEM custom folder. Use DPsFnshr.7z in \OEM\bin or some other file, which definitely belongs to BTS pack. I believe if that file exist, presetup.cmd will exist too.

Good idea, I will surely use it in the next version

[iceangel89]

ilko_t, on Apr 22 2007, 01:59 AM, said:

1. Format the USB stick, I used HP USB Format tool, because XP format was reported as incorrect in GRUB.
2. Install GRUB MBR on the stick, the quickest way I found is by GRUBINST_GUI for WIN
3. Get the latest GRUB4DOS and copy GRLDR to the USB root.

erm i didn't have a problem with windows formated NTFS. so i did not use HP Format Utility (or is it because i am using a internal HDD?)

ilko_t, on Apr 22 2007, 01:59 AM, said:

Create MENU.LST in USB root

Quote

color black/cyan yellow/cyan
timeout 15
default 1
title Phase 1 WinXP Text Mode Setup
map --read-only (hd0) (hd1)
map --hook
root (hd1,0)
chainloader /ntldrstp
title Phase 2 WinXP GUI Mode Setup
map (hd1) (hd0)
map --hook
rootnoverify (hd0)
chainloader +1

This way the default entry is GUI mode, TXT mode must be selected manually. With these GUI entries XP can be installed and booted later from another partition on the hard drive, not only from the first.

for me the text mode works but the GUI didn't... the screen flashed and i am back to OS Selection... why is this so? i think is the last line? what does it does? "chainloader +1" and is there a GRUB4DOS documentation/manual?

ilko_t, on Apr 22 2007, 01:59 AM, said:

4. Backup your current BOOT.INI and in the XP setup folder \I386 run

Quote

winnt32 /makelocalsource /noreboot

after it's finished restore BOOT.INI

whats this for? why do i need to backup boot.ini? and below? whats it for? edit WINNT.SIF & MIGRATE.INF. its for the Read-Only? but why read only for?

ilko_t, on Apr 22 2007, 01:59 AM, said:

5. Copy two new folders in the USB stick root - $WIN_NT$.~BT and $WIN_NT$.~LS

6. In \$WIN_NT$.~BT modify
WINNT.SIF

Quote

[data]
msdosinitiated="1"
floppyless="1"
AutoPartition="0"
UseSignatures="no"
InstallDir="\WINDOWS"
winntupgrade="no"
...

and also this seem to remove my nLite unattended stuff?

[ilko_t]

Iceangel89, latest step-by-step guide is here:
http://www.msfn.org/board/boot_install_USB...636#entry659636

Latest batch file, which does 95% of the work is just a couple of posts above yours, think you can find it yourself

From your post I see very little usable information, need to know what exactly you are trying to achieve, what's the installation media (why talking about internal drive and NTFS? ), what version of Windows, how many partitions on the target hard drive, how many hard drives you have, SATA or ATA, and so on...

Backup of boot.ini WAS needed with the earlier guides, because winnt32.exe whit those parameters (in the early guides) adds an entry in the existing boot.ini so on next restart TXT setup is launched. With the latest batch file this is no longer needed.

To preserve NLite customization simply add /unattend:winnt.sif

winnt32 /makelocalsource /noreboot /unattend:winnt.sif

and don't forget to delete the whole unattended section after that. Applies again ONLY for the step-by-step guide, NO need to do that if using the batch file, which checks if winnt.sif is found, /unattend:winnt.sif is used in order to preserve customizations.

Quote

...but why read only for?

You really missed where all troubles come from when installing this way
Probably a little effort like reading at least pages 2 and 3 you will get why and what.

[iceangel89]

Quote

From your post I see very little usable information, need to know what exactly you are trying to achieve, what's the installation media (why talking about internal drive and NTFS?), what version of Windows, how many partitions on the target hard drive, how many hard drives you have, SATA or ATA, and so on...

i am trying to make an install of XP from a HDD, USB at first but since i think my external HDD adapter is not good, i plugged the HDD directly into the comp for now, making it internal... NTFS is so that the partition can be bigger (but it works). so install media is internal HDD (any diff to the process? for now it works, internally). Version of windows - XP Pro SP2 (nLited). number of partitions - 1 Main HDD, 3 NTFS partitions, on the "Temporary Internal" HDD, 2 NTFS partitions (1 for this, and another for Misc Storage)

and so it means Read Only is for USB problems which i escaped using an internal HDD? i think...

Thanks

[ilko_t]

The routine to install XP from USB flash drive does NOT work for now with USB hard drives, last 2 pages are all about that problem.
For your case you better read these threads:

http://www.911cd.net...showtopic=16713
http://www.911cd.net...showtopic=19745

Deletion of $win_nt$... folders is because they are considered as TEMPORARY, and as such SETUP deletes them on few stages when launched from them. This has nothing to do with USB, IDE, SATA...
These temp. folders are used when prepared by WINNT.EXE or WINNT32.EXE hard drive is started. M$ decided that when SETUP is launched from hard disk this must be one-off installation, and implemented it that way. I386 is used for CD drives and setup files detect install media.
Back to the temp. folders- if they are write protected or renamed when SETUP attempts to delete, them they survive ==> you can use the same prepared disk (usb flash drive) for another install. Basically during the posts here we learned how to invoke installation from new for XP SETUP media, how to trick it NOT to delete temp. files and folders, and how to fix the results of strange for SETUP environment (wrong boot.ini etc.).
I hope that clears a bit whats all about in this long thread.

This post has been edited by ilko_t: 19 September 2007 - 10:56 PM

[happyusers]

Hello to the community,
I tried the procedure given by ilko_t on april 21st. It is said 100% success for ATA. I have followed the tutorial line by line. The first stage (textsetup) from the stick went ok. But I didnt manage to reboot on HDD. I had a message "NTLDR missing". I tried with stick first through grub or hdd first, always the same message. I tried fiddling with boot.ini modifying hdr parameter but everything was useless. I think that the drive could have booted, it seems that, on another computer (I took it to format it) it could have booted.
I installed Win XP Pro sp2 on a Pavilion (512Mo 250 Go sempron 3400).
Would you have diagnostic or advices ?
Thanks very much.

PS : the DOS method went OK. The hdd booted on Win98 prompt and I ran Winnt. But how long it is : 3 or 4 hours!

[ilko_t]

@happyusers
You have used the very first guide, a lot has been improved since then, there is also a batch script preparing USB sticks, have you tried the last guide or the batch file? I'd rather use the batch file.

How many partitions you have on the destination hard drive? Were menu.lst and boot.ini amended accordingly?
Is your source on USB stick? Is it seen at bottom when TXT Setup lists hard drives to be installed on?
Is the message about missing NTLDR coming from Grub4Dos?

This post has been edited by ilko_t: 20 September 2007 - 04:22 PM

[happyusers]

To make things simple, I had only one partition on the destination drive. I think I have written boot.ini and menu.slt correctly. My sources were on the stick and I have not really seen if it was shown. I have to try again. I had noticed the script but thought tings were more under control if I did it by myself. I shall try it. I dont think the message came from grub because I tried both ways of booting, through grub on stick and directly on the destination drive and it was the same. NTDLR missing.
Is it possible that the drive boot when placed on another computer while not on the target computer?

[jaclaz]

"NTLDR is missing"
is an error message hardcoded in the bootsector of any partition formatted under 2K/XP/2003.
(if the "standard" english botsector is used)

So the error is generated long before BOOT.INI comes into play.

Forget for the moment anything about this thread and just:
1) Format the stick with the HP utility or petoUSB or any other method you use
2) Copy to the stick NTLDR, NTDETECT.COM and a BOOT.INI with at least two entries
3) Try booting from it

If it does, try again the method, using the latest tutorial and the batch file.

If it does not, post again, I'll try to help you in first booting part.

jaclaz

This post has been edited by jaclaz: 21 September 2007 - 05:14 AM

[happyusers]

Thank you Jaclaz.
In fact, I got the message (in french "NTLDR manque") when booting on the target drive not on the stick, just after textsetup phase. The stick boot was OK and the first phase of installation too.
According to what you say, that message is probably coded in the boot sector of my drive. Why does that bootloader complain when I boot from drive, I wonder. Is there any diagnostic I can run on the drive to understand what is going wrong?
Perheaps what you suggest for the stick would be applicable on the drive?

[ilko_t]

@happyusers

We could troubleshoot it, but I see no point to do it since a lot has been changed since that guide. NTLDR is missing most of the times it's not where it's expected to be. More interesting for us is why it was not there. My guesses:
1. USB stick was seen as fixed drive and boot files were (attempted to be) written there. That's why I asked you where was it in the list of available hard drives.
2. Grub4Dos didn't like your BIOS and mapping was wrong, try newer/older version. It happened to me already. Check for BIOS updates too.
For simplicity and compatibility in the latest batch file Grub4Dos is no longer used.
3. Anything else...

The batch file is open and customizable, I had no experience in batch scripts making it (wonder how it even worked ) but it's so simple so can barely call it script at all, wimb polished it a lot and there is nothing to mess with the other scripts used within (binifix.cmd and makeBS.cmd). So I suppose even if you have no experience with batch files you will see all the steps which it performs, and do them manually if you wish so. If you don't get something just ask.
I did not intend to write another guide, for now I am waiting a response in a few forums to get dummydisk.sys redone in the way we need it, then try to use it during TXT setup, test how it works and finally add comments to the BAT file, which can be used instead of a guide.

Regards,
ilko

[happyusers]

Hi all,
@jaclaz : I tried the script as you suggested. It is worse, the stick no longer boots. I dont know how to control stages of boot.
I have the message
"System disk invalid
I/O Error"
in french of course, my computer (HP s7705 is french).
I shall try the way you suggest, try to get a normal boot with boot.ini menu on the stick.
I am afraid I shall have to erase once again the wole staff on stick.
Is not there a method to control the content of the boot block on the stick and to repair it? I know it exists for mbr.
That's a pity to format a drive whose content is 99.99% good!

@ilko : I have used the batch usb_prep2. Is it the more recent? I shall try to check what it has done with the stick.
I come back soon.

First edit : I tried mbrwiz on the stick and found that the partition was not active. I toggled it and it seems to boot. We shall see further.
I reach the boot menu. I choose textsetup and have another error message : "Windows could not start the file system32\hal.dll is missing or corrupted".

This post has been edited by happyusers: 21 September 2007 - 05:13 PM

[ilko_t]

@happyusers
That's the latest file, yes.
I believe something is wrong with the boot order, or USB stick is seen as fixed.

1. Could you attach these files from the root of papered USB stick with your next post:
BOOT.INI
BackupBS.ori
SETUPLDR.bs

2. What options in BIOS do you choose in order to boot from USB?
2.1 Do you have an option in BIOS boot menu to emulate USB-ZIP, USB-HDD etc. ?
2.2 Do you boot from USB entering a temporary boot menu, e.g. F12 and choose USB something?

3. Did you have any other USB mass storage devices attached? Card readers, digital camera, MP3 players, printer with card reader...?
4. What version of windows are you running while preparing USB stick?
5. Which tool did you use to make stick bootable?

This post has been edited by ilko_t: 21 September 2007 - 09:14 PM

[happyusers]

Hi ilko,
My BIOS is phoenix award bios 5.04. I have tries booting both ways, usb stick as first device without menu and through the bios menu (not f12 but Esc). In either case, I get the boot.ini menu and after having choosen textsetup, Win complains that it cannot find hal.dll.
I have no other USB device. Win is Win XP Pro SP2 and I have prepared the stick with HPUSBFW.exe.
Here is the boot.ini file you ask for.

[Boot Loader]
Timeout=10
Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[Operating Systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="GUI Mode Setup Windows XP" /FASTDETECT

C:\SETUPLDR.bs="TEXT Mode Setup Windows XP"

It seems that I cannot attach any other file than text files that way, the system hangs.

Edit : I tried uploading with another browser, I have a warning "upload failed, you are not permitted to upload this type of file (BOOT.INI BackupBS.ori SETUPLDR.bs). Sorry.

This post has been edited by happyusers: 22 September 2007 - 01:51 AM

[jaclaz]

@happyusers
Try putting all files in a .zip archive.

jaclaz

[happyusers]

Thank you Jaclaz. Here are the files.
I was out for sunday, my experiments were delayed, no news.
PS : I cannot upload with Firefox, I have to run IE.

Attached File(s)

•  SETUPLDR.zip (1.32K)
  Number of downloads: 57

[ilko_t]

happyusers, on Sep 22 2007, 08:25 AM, said:

...I get the boot.ini menu and after having choosen textsetup, Win complains that it cannot find hal.dll...

I am puzzled, bootsectors seems fine, however Jaclaz should confirm that.
The only reason I can see is that your USB stick is NOT getting C:\ or first HDD during boot. It could be seen as superfloppy or something, but not hard drive. This way NTLDR passes boot routine to wrong path, producing this "HAL.DLL is missing...." or "NTLDR is missing" with the old guide. .
Probably that's why the other method failed too.

You may try to update your BIOS from HP site, and test with USB Legacy Mode Support option in Advanced Menu.

We may try a few tests to confirm that.
Once the stick is prepared change BOOT.INI on it to :

[Boot Loader]
Timeout=10
Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[Operating Systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="GUI Mode  Setup Windows XP" /FASTDETECT
A:\SETUPLDR.bs="TEXT Mode Setup Windows XP 1"
C:\SETUPLDR.bs="TEXT Mode Setup Windows XP 2"
D:\SETUPLDR.bs="TEXT Mode Setup Windows XP 3"
E:\SETUPLDR.bs="TEXT Mode Setup Windows XP 4"

and see which option (1-4) will start Text Mode Setup.
If it doesn't start we may try Grub4Dos will report a marker file is, wich will be placed on USB stick, but thats for later.