Jump to content

"fixed drive" usb driver integration


infiniti25

Recommended Posts

Yep, I meant \USBSTOR\gendisk. :blushing:

I guess that IDE connected card readers are nowadays a thing of the past, and PCMCIA CARDbus ;) are already (or will soon become) outdated by USB "stick-card readers", so not a big problem. :unsure:

jaclaz

Link to comment
Share on other sites

  • 3 years later...

Quite old topic, but I am stuck here. I followed the steps from cdob but when the setup checks the disk for error - it says that the drive U: is corrupted and setup can not continue. Any idea?

I am trying to install XP Pro from an usb stick (second partition, so integrated cfadisk driver) to hard didk partition. U: is the drive letter of the usb stick through migrate.inf.

Master Jaclaz, where are you? Thanks in advance.

Link to comment
Share on other sites

Master Jaclaz, where are you? Thanks in advance.

Here, right after you ;).

I am trying to install XP Pro from an usb stick (second partition, so integrated cfadisk driver) to hard didk partition. U: is the drive letter of the usb stick through migrate.inf.

And this thread is about installing TO an USB stick, not really a surprise that your mileage may vary.

I have NO idea WHat is happening/WHY it is happening, so all I can do is provide some "generic" advice.

You should check the available methods and become VERY familiar with them before attempting to introduce variations/complications, expecially if mainly UNneeded (in the sense of NOT really-really needed):

http://www.msfn.org/board/forum/157-install-windows-from-usb/

A much easier approach would be, if you really-really *need* to have the source in second partition to (temporarily) switch partitions and make it first one:

http://www.911cd.net/forums//index.php?showtopic=24392&start=0

On the other hand why some of the known methods to install XP from USB do use, in case of "Fixed device" (i.e. USB hard disk) a "reversed dummydisk.sys" to make it become "removable"? :unsure:

jaclaz

Link to comment
Share on other sites

:w00t: First of all, thank you very much for replying. I hope I am not hijacking the topic - if so, can you please move my topic to a new thread?

Allow me to clear up my view when I create an universal usb boot stick. My points are:

1) FAT32 is really slow in WinXP installation. So, FAT16 is the source partition (NTFS is not my option :no:).

2) FAT16 is limited to 2GB(64kb cluster is simply wastage of space and limited to 4gb) and I need a lot of recovery/repairing tool on the usb stick. Hence the second partition.

3) Some tools are used from windows, so the partition holding such tools must be visible from installed windows to be able to repair a devective installation/ recovering lost files.:D Of course this partition must be the first one.

4) The above implies that the WinXP source must be the second partition with the benefit that in case of infected system, at least always you have a virus free source in hand as the second partition is not seen by the infected system for infection.

5) You can of course, toggle something to fool XP setup and revert back; but consider the case of incomplete installation - where you toggled something and final command for revering back is not executed. Next time you try to install XP you need to repair your disk first. what a controversy!!:ph34r: By the way, I don't use the batch files for renaming the source folders during text mode setup for the same reason - I use write protection for the first copying portion and a tool DriveEject.exe which ejects the drive just before the setup completes, from winnt.sif. So, no file deletion during the setup from usb stick and no flipping of folder name.

6) I also use Win98 DOS on usb stick - you people know it's invaluable still now for quick repairing/access utitlities like undelete. So, XP setup is also accessable from DOS using winnt.exe - in case any system betray booting from usb. I can always dump the source on hard disk and run the setup from there by copying relevant files like io.sys...etc and transferring GRUB to mbr from still existing Windows.

Hence, I propose creating an USB stick with two partitions:

1) A big FAT32 partition holding all windows tools visible from existing Windows in first position

2) A 2gb active FAT16 partition holding XP source and DOS system/tools protected from infection for emergencies.

3) GRUB in 2nd partition boot sector thus somewhat protected from sudden overwrite of mbr and non bootability from any kind of mistake/infection. Simple recover of mbr boot code from any machine would revive your stick back.

4) Optional SysLinux in 1st partition boot sector for backup/additional operations like linux booting.

5) Optional ISO/linux files in 1st partition/3rd partition for linux rescue or special cases like NT password reset, Acronis bootdisk, KAV rescue cd etc.

Thus creating an all round usb stick for perfect system administrator who has to manage various odd sitiations at various locations. Carring such a portable utility stick as his weapon is obvious need.

Finally, this is all possible only when I can integrate cfadisk in XP setup source and make it bootable from 2nd partition. While it is perfectly doable using the current thread, the only bar is the setup is scanning the disks just before the file copy process and stuck saying the partition holding the source is corrupted and setup can not continue. Without cfadisk from 1st partition it is running properly. I used nlite to optimize the setup and integrated the mass storage drivers from driverpack.

Can the presetup scan be bypassed? Any other idea?

I have NO idea WHat is happening/WHY it is happening, so all I can do is provide some "generic" advice

What does it mean? Why the Lord of WinXP is so negative? :realmad: Any other taker?

Regards.

Link to comment
Share on other sites

:

I have NO idea WHat is happening/WHY it is happening, so all I can do is provide some "generic" advice

What does it mean? Why the Lord of WinXP is so negative? :realmad:

Not at all "negative", a simple, plain, statement. :)

Would you prefer that I lie and EITHER:

  1. tell you (falsely) that I know a perfect solution for that issue but I am not going to tell you exactly how to do it
    OR
  2. tell you (falsely) that I know a perfect solution for that issue then send you on some wild goose chase

jaclaz

Link to comment
Share on other sites

Thus creating an all round usb stick for perfect system administrator who has to manage various odd sitiations at various locations.

... I used nlite to optimize the setup and integrated the mass storage drivers from driverpack.

nLite is for personal use only, you agreed to that when installing it. :whistle:

Link to comment
Share on other sites

Very funny. Thanks for the reply though.

Good. :)

Now had you followed the given "generic advice", you would have found that you are not the first one to attempt something like that, there is at least a previous attempt:

unfortunately daddo1980 never came back to report if it worked....:(

A small Quote for you (still related to "generic" advice):

http://en.wikipedia.org/wiki/AK-47

http://en.wikipedia.org/wiki/AK-47#Design_concept

A lot of [soviet Army soldiers] ask me how one can become a constructor, and how new weaponry is designed. These are very difficult questions. Each designer seems to have his own paths, his own successes and failures. But one thing is clear: before attempting to create something new, it is vital to have a good appreciation of everything that already exists in this field. I myself have had many experiences confirming this to be so.

;)

jaclaz

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...