restore to usb?

[Eric]

Why not copy your .sys files under the drivers folder on the installation of the USB stick?
Copy them also under the OEMDRV folder.

[molecule]

edit-- whoops -- I didn't see page 2 so I missed your response

we are making progress
from ifw in 2k, I did a restore (manual) with all defaults (did not select set active, mbr, boot.ini, etc ... just default log)
I then manually added the 3 missing usb*.sys file to the image
the script no longer declares them missing ...
what is still missing is usbport.inf
I can't find that inf on the 2ksp4 cd or the install (there's a usbport.sys but not .inf)
it is found in XPsp3 install ... with another file (companion file?) usbport.pnf

usbport.inf may contain the list of files that I need -- can you help me read this
[code]
[DestinationDirs]
DefaultDestDir=11 ; LDID_SYS
;
; For Windows NT, all drivers go into %windir%\system32\drivers. Since
; there isn't a DIRID (LDID) that represents this path on both NT and Win95,
; we specify the relative path off of %windir%.
;
EHCI.CopyFiles.NT = 10, system32\drivers
OHCI.CopyFiles.NT = 10, system32\drivers
UHCI.CopyFiles.NT = 10, system32\drivers
USB.CopyFiles.NT = 10, system32\drivers
USBUI.CopyFiles.NT = 11
HCCOIN.CopyFiles.NT = 11
HUB20.CopyFiles.NT = 10, system32\drivers
[/code]

It looks like I copy all *EHCI, *OHCI, *UHCI, *USB and *HUB20 to system32\drivers -- I don't know what 10 or 11 means?
.CopyFiles.NT probably means copy source from I386?
I'll need to hack where *USBUI and *HCCOIN need to go

It'll take me a while to build them

the next section defines a Generic USB device:
; =================== Table of content =========================
; note that these are in alphabetical order
;
[Manufacturer]
...
%Generic.Mfg%=Generic.Section
%Intel.Mfg%=Intel.Section
...
%SMSC.Mfg%=SMSC.Section
...

under the Generic Section we find compatibility with Windows 2000:
[code]
; =================== Generic ==================================
[Generic.Section]
%PCI\CC_0C0300.DeviceDesc%=UHCI.Dev,PCI\CC_0C0300
%PCI\CC_0C0310.DeviceDesc%=OHCI.Dev,PCI\CC_0C0310
%USB\ROOT_HUB.DeviceDesc%=ROOTHUB.Dev,USB\ROOT_HUB
%PCI\CC_0C0320.DeviceDesc%=EHCI.Dev,PCI\CC_0C0320
; provides backward compatibilty with USB2.0 on WinMe and
; Windows 2000
%USB\ROOT_HUB20.DeviceDesc%=ROOTHUB.Dev,USB\ROOT_HUB20
[/code]
I don't have a clue what this code says ...

attached is a zip of USBPORT.INF from XPsp3 if that helps ...

the following is a description of chipset
from other USB boot builders it's apparent that the bios is working with the ICH10 chipset
meaning we're on the right track ... the problem is finding the OS driver
--end of edit--

do you remember which chipset your system motherboard had when you tested 2k?

my mobo is 2008 msi p43neo3f 775 core2duo e7300
chipset is intel P43 and ICH10
this is generally a XP chipset ... so far I haven't encountered any problems
bios reads SATA hdds as IDEs ... no raid or ahci
bios reads usb devices in legacy mode (bios options is enable or disable ... disable excludes UFDs from boot list - safety)

the bios and chipset is seeing the UFD
it boots parted magic (linux) built with unetbootin
2K-tbi image is also seeing the UFD, under dos loading os
at changeover to windows at logon ... bsod 7D
my suspicion is there's a 2K driver missing

I can't understand why script wouldn't see the 3 XP drivers that I copied into system32\ and drivers\

[Eric]

If it can't boot, it means that you are missing a driver.
You can copy (if not already there) in the installation in the UFD:
- hccoin.dll to \WinNT\system32\
- usbui.dll to \WinNT\system32\
- all usb*.sys to \WinNT\system32\drivers\
- usbport.inf to \WinNT\inf\

Then, run the script. It does everything needed to install the USB drivers as critical. It contains much more USB devices than you can find in the usb*.inf.
The script will see the .sys files if they are in the system32\drivers folder of the Windows install inside the UFD.

I'm thinking that you may also need to install all IDE drivers and change the HAl file to halaacpi.dll (if not already set to that). To do that, you may run the osdtool.tbs on the install in the UFD, and install them (go to "Install a driver" -> "Install default IDE drivers", and "Change HAL").
These operations are done if you decide to "Remove all installed drivers" when running UsbBoot.tbs (in addition to removing all third party drivers). But maybe you can just try that option directly?

[molecule]

Thanks Eric! I tried 3 permutations...
The script for each completed no exceptions noted, and concluded "Operation Successful."
Each booted, loaded text and vga systems, and then produced bsod 7D at logon.

(small suggestion ... when there are only 2 choices, it's not real intuitive to tell if the green or blue option is the one that is being selected ... maybe grey out the text for the one not being selected.)

I made an image of a working 2000SP4 system, updated with clean Microsoft patches, for 2000. Then restored the image to a USB Flash Drive (UFD).

In the next instructions, we copy over some XP drivers onto a 2K system.
Based on my noob reading of file usbport.inf in the XPsp3 set, I believe this is intended.
XPiso: = drive letter of cdrom with XPproSP3 install CD, or drive letter of a mounted iso file of the same.
2Kimage: = drive letter of the target UFD which contains the restored image of a working 2000SP4 system.

1) from the folder XPiso:\I386 extract file usbport.in_ to 2Kimage:\WINNT\inf\usbport.inf
2) from the folder XPiso:\I386 extract file hccoin.dl_ to 2Kimage:\WINNT\system32\hccoin.dll
3a) save the file 2Kimage:\WINNT\system32\usbui.dll if you want ...
3b) from the file XPiso:\I386\SP3.CAB extract file usbui.dll and overwrite 2Kimage:\WINNT\system32\usbui.dll
4) from the file XPiso:\I386\SP3.CAB extract 3 files to 2Kimage:\WINNT\system32\drivers\*.*

note)includign 3 files (usbccgp.sys, usbohci.sys, usbuhci.sys) or all usb*.sys will both produce "operation successful"

in 1st, I loaded just the files as above -- operation successful ... bsod-7d at logon
in 2nd, I used osdtools.tbs to change HAL to halaacpi.dll (single processor) (default was multiprocessor for core2duo) -- same
in 3rd, I let script delete all drivers -- same

Microsoft did something to cripple 2k? (to increase sales of XP?)

it may take me a while, but I'll try it on an earlier motherboard ... but I don't think that's it ... any thoughts?

[Eric]

I have forgotten that the usbport.PNF file should also be on the inf
directory. but that won't help.

Have you tried to install your XPsp3 on the UFD? Does it boot?
If so, you can send the System reg and I can analyse it to see which
device and which driver (service) it is using.

I will check my Win2k to see what it has.

[Eric]

Hello,
I think I know what is missing or what can be changed.
I think also that .sys files from XP are not backward compatible with Win2k.
But to be sure, have you tried the operation with XPsp3 on your mobo?
Thanks

[Eric]

Hello,
A new version of the UsbBoot has just been release in the main page of the OSD Tool Suite.
Should work fine for Win2k (but if installed under \WinNT, then the WINDIR constant should be modified).
Eric

[molecule]

hello eric ... thanks ... I haven't dropped the thread

when I went to install my xp pro sp3 version 2002 for the first time, I found out that XP professional version 2002 is really XP Home

the hologram side of the CD says XP Professional ...
the COA certificate with the Product Key says XP Professional ...
but the digital side of the CD installs XP Home
(cannot install domain, cannot logon as administrator,
default administrator cannot delete the required bubblegum administrator
the first Welcome screen is so much bubblegum that is an insult to anyone's intelligence
I was so angry when I learned this ... it just seems like everything MS does is somehow dishonest

winnt is the standard install for 2k

I'm still working on trying to find a cd or iso of XP pro that is XP pro on both sides of the CD ...

I don't want to mount the learning curve for a crippled version of 2K, which is what XP is really (when an administrator can't delete a user account, that's when I quit)

[Eric]

> winnt is the standard install for 2k

OK. I could have made the script manage both (as the osdtool does), but I think that most of the user will use the script under XP. For some, they just need to change a constant.

[mjnelson99]

Where did you get the disk from? It might be a pirated disk
made to look real.

I know I found an iso of Win 7 Home Premium online. As a
test i did install it with my install code and it worked.

Maybe you will be able to find an iso for XP.

On 10/4/2012 12:49 PM, molecule wrote:
> hello eric ... thanks ... I haven't dropped the thread
>
> when I went to install my xp pro sp3 version 2002 for the first time, I found out that XP professional version 2002 is really XP Home
>
> the hologram side of the CD says XP Professional ...
> the COA certificate with the Product Key says XP Professional ...
> but the digital side of the CD installs XP Home
> (cannot install domain, cannot logon as administrator,
> default administrator cannot delete the required bubblegum administrator
> the first Welcome screen is so much bubblegum that is an insult to anyone's intelligence
> I was so angry when I learned this ... it just seems like everything MS does is somehow dishonest
>
> winnt is the standard install for 2k
>
> I'm still working on trying to find a cd or iso of XP pro that is XP pro on both sides of the CD ...
>
> I don't want to mount the learning curve for a crippled version of 2K, which is what XP is really (when an administrator can't delete a user account, that's when I quit)
>
>