Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

USB functional patches for Win2000 after SP4 and R1

- - - - -

  • Please log in to reply
20 replies to this topic

#1
pointertovoid

pointertovoid

    Advanced Member

  • Member
  • PipPipPip
  • 466 posts
  • Joined 16-January 09
Hello dear Windows 2000 users!

This thread is an (ambitious...) attempt to list all patches released after SP4 and Rollup 1 to improve function, not security, of the files implementing USB on Win 2000.

These patches aren't highly publicized by Microsoft (most were intended for an SP5 that was never published) and don't appear in automatic updates, so such a list isn't very common despite the patches may improve USB function for some users.

Microsoft's warning in these patches' descriptions is that they haven't been tested enough, so one should use them only if experiencing the specific undesired behaviour that a patch cures. Anyway, at least we'll know they exist.

To find the patches, I googled the filenames through support.microsoft.com in English only, which did take some time - hopefully saved to other users. This method certainly has limitations, so additions, improvements etc are welcome.

The wise users of Gurgelmeyer's unofficial SP5 have all these files already in their latest possible versions - at least, this is what I saw in its i386 folder without having installed the uSP5. The only exception is Usbport.sys at v6926 instead of v6941, which is hard to explain, as only KB843503 brings Openhci.sys v6940 present in uSp5 and this KB843503 brings Usbport.sys v6941 as well. As a consequence, the uSp5 may benefit from KB843503.

In the coming table, I shortened some repetitive numbers... So
1234 means version 5.0.2195.1234
123456 means KB123456 corresponding to these descriptions and patch file name:
http://support.micro...kb/123456/en-us
Windows2000-KB123456-x86-ENU.EXE
(you must replace ENU by your language, like DEU ESN FRA PTB ITA, but should better stick to en-us!)

The first version number is observed in an (old) Win2000 with SP4 and R1 that has all security patches up to January 2009 but no function patch more recent than R1 - that is, a rather common situation. Interestingly, all these files are ENU or ANY on the non-English Win2000 I observed (but ENU patches don't install).

Well, here it comes...


How to remove advertisement from MSFN

#2
pointertovoid

pointertovoid

    Advanced Member

  • Member
  • PipPipPip
  • 466 posts
  • Joined 16-January 09
The table is plain text to help you copy it. In order to display your copy properly, you'll need a fixed width font (like Courier new) where you paste it, for instance an Html document or a text editor (Metapad does it).

------------------Sp4,R1,-----------------PAY-----WGA----------BSOD
----------------Security---883528-838771-838921-838989-843503-838417-836111-823086-817765-841880-890202--
=========================================================================================================
hidclass.sys----2195.6655------------------------6882---6882
(hidusb.sys)----2142.1
openhci.sys-----2195.6675------------------------6882---6940----
uhcd.sys--------2195.6655------------------------6882---6882----
usbarw.sys------2195.1620
usbcamd.sys-----2135.1------------------------------------------------6883--
usbd.sys--------2195.6658-----------------6882---6935---6935---7008--
usbehci.sys-----2195.6709------------------------6882---6882--
usbhub.sys------2195.6689----------6883---6884-----------------7006--
usbhub20.sys----2195.6655------------------------6891---6891--
usbintel.sys----2134.1
usbport.sys-----2195.6681------------------------6926---6941--
usbprint.sys----2195.6655---6968--
usbscan.sys-----2195.6655
usbser.sys------2195.6655--------------------------------------7006--
usbstor.sys-----2195.6655----------------------------------------------------6773---6871---6934---7009--
=========================================================================================================
---------------------------883528-838771-838921-838989-843503-838417-836111-823086-817765-841880-890202--

Hidusb.sys and Usbser.sys exist only in Driver.cab on the observed Win2000.

#3
pointertovoid

pointertovoid

    Advanced Member

  • Member
  • PipPipPip
  • 466 posts
  • Joined 16-January 09
As a consequence of the version numbers above, and IF I understand it properly, one only needs the following updates to get all latest files:

836111 838417 838989 843503 883528 890202
which supersede
817765 823086 838771 838921 841880

836111 solves a very specific problem and nearly everyone should be able to neglect it.
Similarly, having 841880 instead of the uncommon 890202 should be as good for nearly everybody.

These files aren't easily available at Microsoft, but people running an ENU W2k may get most of them by searching for the file name, like
"Windows2000-KB838989-x86-ENU.EXE"
and so on.

#4
James_A

James_A

     

  • Member
  • PipPip
  • 153 posts
  • Joined 23-December 07
Thanks for this list. I did a similar list some time ago when we actually needed some of these Hotfixes.

However, at that time, I missed 843503 (which seems to completely replace the earlier 829759).

What do you mean by "These files aren't easily available at Microsoft"? Once the numbers are known, all of them are easily available on request by email with just a few mouse-clicks. You've already done the hard part, which is finding the KB numbers.

.

#5
pointertovoid

pointertovoid

    Advanced Member

  • Member
  • PipPipPip
  • 466 posts
  • Joined 16-January 09
Thank you so much, James_A! :thumbup

You are perfectly right, these patches are sent by Microsoft for free. I believed it would require a special maintenance contract after 2005, but my Oem W2k without Wga could receive the patches without any other condition.

I was disappointed that Microsoft had written patches and didn't release them with the planned Sp5, but giving the patches easily and for free improves their image quite a bit. Knowing that, incomplete testing is indeed a credible reason not to release the patches more widely.

-----------------

The contents of several patches differ from the KB descriptions which were the source for my table.

KB838989 has Usbd.sys v6935 and Usbport.sys v6926 - both are more recent than announced. Maybe we shall understand KB838989 as a rather general-purpose refresh for Usb on W2k, though it isn't the latest possible update; Microsoft distributes it more widely, without the "little tested" warning and under Wga.

KB838417 has Usbd.sys v6935, Usbhub.sys v6935 (older than announced) and no usbser.sys (not installed anyway on my W2k).

-----------------

I missed KB829759 just because it put "for W2k Sp3" and this reason was bad. The files it brings are newer than those brought by Sp4 and R1 - but older than KB843503, yes.

-----------------

I've neglected KB836111 but have now the other five most recent ones. I'll try them and tell you what they've installed and if I can eject my CF cards after that.

#6
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,567 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag
Completely (but not much ;)) out of topic :ph34r: , have you benchmarked the FAT32 on USB sticks before and after the updates?

FYI:
http://www.msfn.org/...howtopic=125116

jaclaz

#7
pointertovoid

pointertovoid

    Advanced Member

  • Member
  • PipPipPip
  • 466 posts
  • Joined 16-January 09
Now, I've received from MS all patches I wanted, installed normally since they had the adequate language, and tried them.

A general observation is that the versions and even the number of modified files that ship with a patch (or hotfix) don't always match the description in the KB (knowledge base). The versions seem to have evolved over time without updating the description. This would explain why, for instance, Gurgelmeyer's unofficial Sp5 contains files and files combinations that don't exist now in February 2009.

What does work is that patches install all the files they carry, provided these are of a more recent version than the one in place.

From all the patches I tried (basically, the ones that bring the newest files +841880 as an alternative), none did what I hoped: allow to eject a CF card from a "9-in-1" reader from the user session. Only the administrator can do it. I hoped the patches for Usbstor.sys would bring this extra refinement - no, they change nothing here. Even right-click on the Eject icon from the taskbar, and the the "detailed" option in the subsequent windows, shows all places from the 9in1 and closes them all, whatever I highlight.

More disturbing: with these patches, new instabilities have appeared. One blue screen when hot unplugging the Adsl modem as it was still trying to synchronize on the line; this modem as well as the "9-in-1" reader not always detected when plugged; a user session that doesn't close... Things I hadn't seen in 2 years, using W2k in an often cavalier fashion.

So Microsoft's recommendation now looks reasonable: these patches "aren't fully tested" as they say (are still bugged I say), and use them only if you experience the problem they solve. And a W2k incorporating all these patches isn't necessarily better than without them all, quite the opposite.

I haven't tried each one in-depth, except for ejecting the CF. MS releases KB838989 without the accompanying warnings, so this one could be of higher quality. And to install W2k from a CD drive on Usb, the relevant patches are 823086 (replaced by 890202) and 838417 (replacing 838921).

Edited by pointertovoid, 17 February 2009 - 08:04 PM.


#8
pointertovoid

pointertovoid

    Advanced Member

  • Member
  • PipPipPip
  • 466 posts
  • Joined 16-January 09
Ciao Jaclaz!

Benchmarked the FAT32 on USB sticks: no.
- To go fast, use a CF on a P-Ata adapter or in an Udma reader, not a Usb stick
- I've already seen three broken Usb sticks (from "innocent" users), but none of my many CF (who have experienced heavy and exotic uses).
- I also use two Win95b around me, which work very well and will stay indefinitely, but don't have Usb. They access CF through P-Ata and Pcmcia.
So I have no Usb stick - not a single one.

I've benchmarked a lot, but on CF with a P-Ata adapter. In short:
- Mlc is very slow on small files, Slc is faster there, especially when writing, and HDD are generally better. This corresponds to the experienced speed, and is best measured with Atto, not at all with HdTach nor HdTune.
- Filesystem makes no difference there, PROVIDED THAT cluster size is the same
- CLUSTER SIZE changes speed an awful lot on Flash memory. This favours Fat16. Have a look at Dandu.be if you read French - others exist in German and English.
- Drivers don't change CF speed significantly on P-Ata.

Conclusions with Usb sticks may be different.

Arrivederci!

#9
pointertovoid

pointertovoid

    Advanced Member

  • Member
  • PipPipPip
  • 466 posts
  • Joined 16-January 09
Jaclaz, about Usb sticks slower on Xp than W2k, check that:
http://www.uwe-sieber.de/english.html
Gross Technik mate in Churmany!

#10
pointertovoid

pointertovoid

    Advanced Member

  • Member
  • PipPipPip
  • 466 posts
  • Joined 16-January 09
I've tried separately the various functional patches for Usb. In short:
- Most work without obvious flaws, but what they bring doesn't correspond to my computer
- KB838417 is bugged and should better be avoided.

Not only does KB838417 produce a blue screen each time I disconnect my Adsl modem (even with proper ejection before), it also lets my Cdrom reader make from time to time the same noise as during power up, lets the mouse scroll go mad, and partially closes Explorer plus TClockEx (a better clock for W95-98-98se-Me-2k, very nice). To produce such varied nonsense on a computer, the most probable way is to write at irrelevant locations in the Ram - something a driver is probably allowed to do.

I also tried the Usbhub.sys v7006, which is announced in the knowledge base KB838417 and is integrated in Gurgelmeyer's unofficial Sp5 (the KB838417 patch brings v6935, and also Usbd.sys v6935 which KB838989 and KB843503 already bring). For that, recreating with Cabarc a modified Drivers.cab was necessary. It has similar bugs. So to users of uSp5 who would experience similar mishaps, I would suggest to bring Usbhub.sys back to v6689 in Drivers.cab, DllCache and Drivers.

By the way, I find a bit disappointing that several editions of Usbhub.sys display the same patent bug. The bug probably explains why the patch doesn't contain the file versions announced in the Knowledge Base - but it didn't help. And as the Sp5 was suppressed, there was logically no money left to correct Usbhub.sys. Such bugs explain why Microsoft tell to use the patches with caution and only if experiencing the related problem.

I couldn't find a better version of Usbhub.sys : v6883 from KB838771 doesn't address the issue of installing W2k from a Cdrom reader on Usb, and v6884 from KB838921 isn't publicly available. No other patch for Usbhub.sys seems to exist.

So to people willing to install W2k from a Cdrom reader on Usb, the suggestion would be to find a P-Ata Cdrom reader. Has anyone tried from a S-Ata Cdrom reader?

Edited by pointertovoid, 21 February 2009 - 03:34 PM.


#11
pointertovoid

pointertovoid

    Advanced Member

  • Member
  • PipPipPip
  • 466 posts
  • Joined 16-January 09
And now, an updated version of the table, with the missing KB829759 and more indications.

The table is plain text to help you copy it. In order to display your copy properly, you'll need a fixed width font (like Courier new) where you paste it, for instance an Html document or a text editor (Metapad does it).

Again, 123456 means KB123456 and 1234 means 5.0.2195.1234
PAY is shorthand for "not publicly available", WGA for "no caution warning" and BSOD for "better keep away".

------------------Sp4,R1,------------------------PAY-----WGA----------BSOD
----------------Security---829759-883528-838771-838921-838989-843503-838417-836111-823086-817765-841880-890202--
================================================================================================================
hidclass.sys----2195.6655---6824------------------------6882---6882
(hidusb.sys)----2142.1
openhci.sys-----2195.6675---6824------------------------6882---6940----
uhcd.sys--------2195.6655---6824------------------------6882---6882----
usbarw.sys------2195.1620
usbcamd.sys-----2135.1-------------------------------------------------------6883--
usbd.sys--------2195.6658---6824-----------------6882---6935---6935---7008--
usbehci.sys-----2195.6709---6824------------------------6882---6882--
usbhub.sys------2195.6689-----------------6883---6884-----------------7006--
usbhub20.sys----2195.6655---6824------------------------6891---6891--
usbintel.sys----2134.1
usbport.sys-----2195.6681---6824------------------------6926---6941--
usbprint.sys----2195.6655----------6968--
usbscan.sys-----2195.6655
usbser.sys------2195.6655---------------------------------------------7006--
usbstor.sys-----2195.6655-----------------------------------------------------------6773---6871---6934---7009--
================================================================================================================
---------------------------829759-883528-838771-838921-838989-843503-838417-836111-823086-817765-841880-890202--
NB (by dencorso): When requesting KB838417, make sure to select the so-called "SP5" release, not so-called "latest" release, which contains earlier files and omits usbser.sys, as pointed out by Bristols here. I corrected the tables to reflect the contents of the "SP5"release, but poinertovoid tested the "latest" release, instead, because the existence of two different versions was not known at the time, so perhaps the "SP5" version is useful and does not cause BSODs... This, clearly, warrants testing.

Edited by dencorso, 28 April 2012 - 08:15 PM.


#12
tomasz86

tomasz86

    www.windows2000.tk

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,520 posts
  • Joined 27-November 10
  • OS:XP Pro x86
  • Country: Country Flag

NB (by dencorso): When requesting KB838417, make sure to select the so-called "SP5" release, not so-called "latest" release, which contains earlier files and omits usbser.sys, as pointed out by Bristols here. I corrected the tables to reflect the contents of the "SP5"release, but poinertovoid tested the "latest" release, instead, because the existence of two different versions was not known at the time, so perhaps the "SP5" version is useful and does not cause BSODs... This, clearly, warrants testing.

Actually pointertovoid tested both sp5 and "latest" and both didn't work for him.

Out of all these updates\hotfixes the following ones seem useful:

836111
843503
883528
890202

The rest are superseded by these and the buggy 838417 is omitted. Pointertovoid mentions problems only with Usbhub.sys v7006 but there are three files available in the hotfix:

usbd.sys 5.0.2195.7008
usbhub.sys 5.0.2195.7006
usbser.sys 5.0.2195.7006

Personally I'd avoid using all three of them just in case (one of them is buggy and the two others are connected with it so you never know...). If you're using Gurgelmeyer's USP 5.1 you may want to replace them like this:

usbd.sys 5.0.2195.7008 -> usbd.sys 5.0.2195.6935 (843503)
usbhub.sys 5.0.2195.7006 -> usbhub.sys 5.0.2195.6689 (SP4)
usbser.sys 5.0.2195.7006 -> Usbser.sys 5.0.2195.6655 (SP4)

Replacer is a very good program to replace system files manually.

Edited by tomasz86, 29 April 2012 - 12:21 AM.

Posted Image
Unofficial Service Pack 5.2 for MS Windows 2000 <- use this topic if you need help with UURollup, Update Rollup 2 and other unofficial packages

#13
dencorso

dencorso

    Iuvat plus qui nihil obstat

  • Supervisor
  • 5,944 posts
  • Joined 07-April 07
  • OS:98SE
  • Country: Country Flag

Donator

This resource, albeit somewhat old already, may be useful, so I give it's link here, to keep similar things as together as possible.
List of the latest USB hotfixes for each Windows version (as of Nov 13, 2009).

#14
tomasz86

tomasz86

    www.windows2000.tk

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,520 posts
  • Joined 27-November 10
  • OS:XP Pro x86
  • Country: Country Flag
:thumbup

It may be old but nothing has changed since then so it's still relevant and will probably be relevant in the future too unless someone manages to replace/modify the files in order to make them compatible with USB3.0 drivers.
Posted Image
Unofficial Service Pack 5.2 for MS Windows 2000 <- use this topic if you need help with UURollup, Update Rollup 2 and other unofficial packages

#15
Molecule

Molecule

    Member

  • Member
  • PipPip
  • 190 posts
  • Joined 11-November 05
@pointertovoid ... I seem to remember you are using 2k on ICH10 chipset ... ICH10 handles the USB bus ...
have you had any luck (or problems) trying to boot from a WinSetupFromUSB setup iso from a USB flash drive?

I was wondering where to post this ... this seemed best, because it kind of gets into usb drivers for 2k

I have 2K on top of a ICH10 P43 chipset (msi p43neo3f core2duo)
bios has all SATA hdds read as straight IDE (no hotswap or raid)
intel XP drivers install no questions and fingers crossed ... no problems so far

bios for usb is set to recognise legacy USB (choices are enable or disable)
disable prevents bios from scanning USB bus for flash drives
(if disabled, once loaded 2k will see them fine, but for safety USBs can't selected from a boot sequence)

@tomasz86 ... I remember a list somewhere where Update Rollup2 or UUrollup-v10c had included some of the USB drivers from the SP3.CAB cabfile for XPpro?

usbccgp.sys
usbohci.sys
usbunci.sys

they were on the list, but I think they were removed from the files and you went with the straight 2K version of KB838989
that was the patch for not losing contact with a USB during power cycles (i.e. during loading phase of booting)

the same KB number gives different filesets for XP and 2K, but both sets should address the same issue (obviously)

I'm asking because I'm running a script that will almost restore an image of a working 2K system to a UFD ,,,

when I restore an image of my 2k system to UFD, the UFD boots, 2K loads in text mode, loads vga mode, but bsod's me with a "7D" when it changes over to logon

the techie at terabyte (it's their script) had tested it in 2k and recalled that it worked ... a 2K image can boot from a UFD and run

I'm wondering if it might be the 2k USB drivers and the ICH10

(we usually think ICH10 for AHCI or RAID, but ICH10 also controls the USB bus ...)

so loading the XP drivers in 2K might make a difference for 2K on ICH10 mobos ...

when I boot parted magic from USB it runs fine ... thus, bios plus ICH10 plus linux drivers are "all systems go"

when I try to format UFD using WinSetupFromUSB with 2k, the program doesn't see the USB, even to select it as target for formatting ... yet 2K manager will format it, as will everything else I've tested

thus, I'm trying to get WinSetupFromUSB to work, but I have the feeling it might be the 2K drivers plus the ICH10 ...

any reason you pulled the XP files from the UUrollup2 and the v10c?

how do I install them to use them? (I have XPproSP3 ... they are in SP3.CAB)
I tried registering them but regsvr32 answered with ... file was loaded but could not find initial entry point ... not a dll or ocx ... something like that

do you think it might be the 2K drivers + ICH10 that blocking boot from USB in windows 2k?

Edited by Molecule, 29 September 2012 - 04:02 AM.

can the platonic solids be constructed by gaussian modulation of rotational action, rotational action itself being an artifact of intersection of two sphaeric actions--the tetrahedron for example

#16
tomasz86

tomasz86

    www.windows2000.tk

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,520 posts
  • Joined 27-November 10
  • OS:XP Pro x86
  • Country: Country Flag
@Molecule

I don't remember myself writing about XP SP3 USB related files in 2K... :unsure: Those files are incompatible with 2K and can't be used as they are. I did mention somewhere that it might be possible to use XP Beta ("Whistler") files but I haven't tried them yet. It's pretty complicated because in order to do that ALL of the original USB related files would have to be replaced.

I don't really use USB based backups so I don't know too much about it :( and won't probably be able to help you with this problem. As for WinSetupFromUSB, in order to use it in Win2k you must download the previous beta version (not the newest one), and then open "Advanced Options" and enable displaying all drives there. After doing so you'll be able to select your USB device (use keyboard arrows to switch between them). You also should format the device using the system Disk Management (or just "format" from command line) instead of using the tools from WinSetupFromUSB.

Have you got the drivers for ICH10 integrated in your source? You should use the ones from BlackWingCat (http://blog.livedoor.jp/blackwingcat/archives/813816.html). nLite should be able to integrate them.

Edited by tomasz86, 02 October 2012 - 03:23 AM.

Posted Image
Unofficial Service Pack 5.2 for MS Windows 2000 <- use this topic if you need help with UURollup, Update Rollup 2 and other unofficial packages

#17
Molecule

Molecule

    Member

  • Member
  • PipPip
  • 190 posts
  • Joined 11-November 05
hey thanks tomasz86!

you're right ... I saw that kb838989 was included in UU-v10c but I had inadvertently copied the filelist for XP over into my 2K database ... so when I did a search it came up ... I was getting tired ... arghh

what I'm thinking is that ... we know that XP can be booted from a thumb drive -- so that's a start. If we can tweak the XP script over to 2K (see "USBBoot 2.04 TBS script to enable booting XP from a USB drive" see Additional Items)) then we can get 2K booting from USB.

If we can get 2K to boot from USB, then we should also be able to install 2K into a USB!!

Then we could install 2K from a setup-USB into a system-USB!! That would be nice for hardware testing!

I thought it might be worth an effort. It might be the 2K kernel, or it might be that the script is hardcoded for the XP file set (2K 838989 accomplishes the same thing (recognize USB through power cycles) but it uses different file names.

I'm now trying to build a XP machine to verify that it's not my motherboard. major ARGHHH ... visually XP is like going backwards to Windows 3.111!!! Do you remember that one?? I'm hearing windows 8 will be 30 gig!

2K boots the dos phase of an install (the intial copy files) and on first powercycle, it boots the second phase (640 VDA setting up? or something)

But at the second power recycle, at last reboot, into final logon screen, the system loses the USB nad returns BSOD 7B.

one of the files needed to tweak a XP install to boot from USB is USBPORT.INF

I'm not an inf maven (not even hardly ...) but my suspicion is that file is might be worth a quick look see ... If I read the /comment lines right, that inf is intended to port USB files down to 2000 and ME and 98se. Thus a homeoner who has XP and who wants to share XP-level USB with other machines in a domain or something ...

on an XP install, I think it's found under I386\ or I386\inf\ ?? (I'm on 98 right now)

it might be worth a quick look ... attached is a zip ... if you're familiar with inf-talk, it'll be a read fast (does it port the XP USB files down to 2K? usbohci, usbuhci, ... etc.?

that's why I put the question in this thread for 2K options for USB filesets ...

Part of pointertovoids quesiton was also related to ICH10R as well, since ICH10R southbridge handles the USB bus

AMAZING ... Intel's drivers for AHCI and RAID are XP ... but the Intel drivers for ICH10 USB has a 2K set of drivers. Thus, 2K is flying high for USB side of ICH10R!! It's a standard Intel ICH10R installer ... it's readme.txt file lists 2000 as qualified. It's a few meg so I can gmail if needed, but give me a few days, since I gmail from the library. (I'm on dialup at home). AHCI is nice for servers where 100 clients are all trying to get at different parts of a hdd on a server at the same time. So AHCI queues up all the requests so as to minimize head thrashing and seek time. But the AHCI overhead is useless (or worse) for a single workstation. Where request queue has a depth of all of ... 1) And I don't need RAID so, I don't need ICH10 drivers for RAID or AHCI ... I leave my bios as IDE (just as fast) ... and Intel's ICH10 IDE-to-SATA bridge is straight through 2K as well.

I'd like to try blackwing's kernel with the XP script to see if a USB can boot 2K, but I can't figure out how to get a link ... google doesn't translate his site on my 98se browser very well ... he has this tool with dropdown selections to match OS and chipset to his download links ... but google doesn't translate inside the dropdown boxes for me ... so I can't get to the links ... maybe your 2K site could link to some of his kernels? mine mobo is msi P43-neo3f ... P43-ICH10R chipset with core2duo e7300, with windows 2000sp4 and evolving

If we can get 2K to boot from USB, then eventually, then we are not far from getting 2K to install into USB ... good for quick testing

edit -- forgot to attach zip

Attached Files


Edited by Molecule, 02 October 2012 - 10:56 PM.

can the platonic solids be constructed by gaussian modulation of rotational action, rotational action itself being an artifact of intersection of two sphaeric actions--the tetrahedron for example

#18
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,567 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag

....
what I'm thinking is that ... we know that XP can be booted from a thumb drive -- so that's a start. If we can tweak the XP script over to 2K (see "USBBoot 2.04 TBS script to enable booting XP from a USB drive" see Additional Items)) then we can get 2K booting from USB.

If we can get 2K to boot from USB, then we should also be able to install 2K into a USB!!
....


There are NO issues that I can remember in booting 2K from USB if not that of pagefile not available..
It was done more than 6 years ago.
See here:
http://www.911cd.net...showtopic=14181
the procedure is suitable (and actually reported as working) to Win2K also:
http://www.911cd.net...087
http://www.911cd.net...n2k

Since there was not much interest in Win2K even then (everyone was already on the XP bandwagon, the topic was never deepened much, but I had it working allright.


jaclaz

#19
Molecule

Molecule

    Member

  • Member
  • PipPip
  • 190 posts
  • Joined 11-November 05
@jaclaz the 2nd link you gave lists USB files from XP

that's the reason I posted here ... because these files are not included in 2K, but I believe they are needed by 2K to be USB bootable

according to USBPORT.INF from XP these files might be intended for use in 2K as well, though not a part of any KB patch ... from USBPORT.INF
[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

I'm can't read inf, but it looks like copy all *EHCI, *OHCI, *UHCI, *USB and *HUB20 to system32\drivers

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 a comment on backwards compatibility with Windows 2000:
; =================== 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

for the terabyte script to run, 2K needs
--hccoin.dll to \WINNT\system32\
--usbui.dll to \WINNT\system32\
--all usb*.sys to \WINNT\system32\drivers\
--USBPORT.INF to \WINNT\inf\

the USBPPORT.INF then ports XP drivers for USB down to 2K (and ME and 98se)

so, that's the question ... do these files XP belong in a 2K final?

IF this is a standard MS port down from XP to 2K (which is buried in the XP install and rarely noticed), and if the port makes USB under 2K more powerful ... any reason why not?
can the platonic solids be constructed by gaussian modulation of rotational action, rotational action itself being an artifact of intersection of two sphaeric actions--the tetrahedron for example

#20
tomasz86

tomasz86

    www.windows2000.tk

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,520 posts
  • Joined 27-November 10
  • OS:XP Pro x86
  • Country: Country Flag
@Molecule

Frankly speaking, I've got no idea about USBPORT.INF. In the past I did try to prepare such an installation which would be able to run from a USB memory stick but in the end it didn't work.

At that time I tried to follow instructions from this website:

http://www.techit.pl...h-USB,1125.html

It's for XP/2003 and it's in Polish so you need to use a translator. One important thing to know is that the files have different names in 2K and XP/2003, ex.

XP
[InputDevicesSupport.Load]
usbehci = usbehci.sys
usbohci = usbohci.sys
usbuhci = usbuhci.sys
usbhub = usbhub.sys
usbstor = usbstor.sys
but in 2K:

[InputDevicesSupport.Load]
openhci  = openhci.sys
uhcd     = uhcd.sys
usbhub   = usbhub.sys
usbstor  = usbstor.sys
I'm guessing that:

XP usbohci = 2K openhci
XP usbuhci = 2K uhcd
XP usbhub = 2K usbhub + 2k usbhub20
XP usbstor = 2K usbstor
XP usbehci = 2K usbehci

There's a different number of files in 2K and XP and some of them have got different names, so you can't just follow the guidelines for XP/2003.
Posted Image
Unofficial Service Pack 5.2 for MS Windows 2000 <- use this topic if you need help with UURollup, Update Rollup 2 and other unofficial packages

#21
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,567 posts
  • Joined 23-July 04
  • OS:none specified
  • Country: Country Flag
A lot of time passed since, really cannot remember the details, I will have to look in VERY old backups.
Anyway, this should help:
http://www.infdump.c...iles/U/usb2.inf

jaclaz




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users