* reference:  "Hot For Teacher" Video

... To Be Continued ...      ... or not; I'd rather watch "Diamond Dave's" Game Show!   

One could be thankful that Gollum didn't feel the need to write in.

LOL, that was epic!

Precious sample:  http://forum.driverpacks.net/viewtopic. … 019#p29019

Well, with that all behind us, how did it all work out silents429?

I will certainly answer questions and offer any insight i may have, but i am not going to invest serious resources.

If i did have time for a project the first would be updating the finisher for NT6.

Please test and report, we may help each other and a lurker or two as we go. Move mountains... not so much.

Jeff

PS we take great time and invest much thought while collaborating on what we can and cannot provide support for and how we can provide that support. You referred to at least one of those well thought out (by the team) decisions as "stupid'. (implied... you can do better). That is not only giving the messenger (Mr_smartepants) but also the entire team who made that decision "the bird". IMHO

- you are welcome to come onboard and help with development and updates, at which point you will have the opportunity to have your opinion heard. If you are not willing to contribute time or money then you are simply being a troll. (sorry i have been trying not to respond to your harshness, with harshness). 

It's real easy to stand on the sidelines and yell at the players on the field, but unless you are one of the players on the field... you need to just sit back and enjoy the game and let the coaches run the plays.

nobody likes a backseat driver, especially one with no license.

Note: When you want some help... calling the person you want help from stupid is not a good opening move.
to be clear, while you did not call him stupid directly you did call his (our) decision stupid.

Extrapolate... stupid decisions are made by stupid people,
a group of smart people usually don't make stupid mistakes.
YES you called him and us stupid, whether you realize(d) it or not

I hope that helps to explain our collective reaction.

A smart Poster would have stated "Why is this OS no longer supported?"
People never take offense to a good question.
Either you are not smart or you already knew the answer...
assuming you are smart and already knew the answer...
you simply were throwing a temper tantrum to try to get your way?

I know you realize all this because the next day you say that
"not much else caaan really be done for 2000 at this point anyway"
You came to the same decision yourself after you slept on it !

negatively disparaging the character of mr_smartepants et al.

Oh, believe me I've heard worse.  I have a thick skin.  He (or anyone) can negatively disparage my character anytime they like.  I don't care.

I'm a firm believer that everyone is entitled to voice their own opinion...even if it's wrong.

Jeff and I are in agreement that we won't support W2k anymore.  Nobody will be able to convince me to devote any more time to that ancient OS.  Sorry, but I have better things to do with my limited time.  I'm also sorry that upsets you, but ranting won't change my mind.
If TechDud wants to take this on as a challenge, so be it.  But that is his choice.

Since that is the case, why not just restore your Sony back to factory defaults for general usage and run Win2k in a virtual machine (VirtualBox, VMware, HyperV, etc.)?
You'll be much happier.

I choose IT over XP because it was older. Just prefer 2000 and below.

    It would seem that i am not the only one to interpret your comment as such.

  Perhaps you might agree how such a comment might be interpreted as negatively disparaging the character of mr_smartepants et al.  If i was to venture an educated guess, it would be that this is not the first time that you have entreated negative feedback for unfortunately worded commentary.
  Live and learn.  A short apology might be in order.  We are not looking for anyone to "kiss our behinds" though, that would be degrading to you and ourselves.  If you do not believe an apology is in order, then do not.

One thing i do wonder, why is it you have not chosen XP for your VAIO?

At any rate,  the USB2 issue has been solved with the inclusion of some drivers from both Official Chipset & MassStorage packs, as the Official Releases do not suffer from this particular bug.  The corresponding "USB 2.0 Root Hub" has been installed now as well.
  However; there are other issues that i have uncovered that effect XP & w2k3 concerning usb drivers.
    Those involve wptusb, ich6usb, ich5usb, patusb and DH89xxCC-usb for differing reasons.

These potential issues need be addressed before any public offering can be made.

One interesting note is that Intel switched from using UHCI for most drivers to using OHCI.  This doesn't seem at first blush to be in error.  Perhaps someone can comment on this.

Installs now work on my Inspiron 1525 with ICH8-M & Core2Duo, and my HP Media Center with N10/ICH7-GR/GH & P4-D.

  Funny thing is that the controller is listed as "Unknown" during the partitioning phase on the Inspiron, yet "iastor2k" is listed in non-PnP as it should.  The Media Center properly states that the controller is "iastorEk" during partitioning, yet when i achieve the desktop, it is v7.0.0.1020 that is installed and "iastorEk" v5.7 is in the non-PnP section.
  When DPsFnshr  starts, i am greeted with "new hardware installed, restart now?", so i wait for DPsFnshr to complete and the Desktop to load before restarting.  This doesn't occur on the Media Center PC.
  For both, i have to manually enable DMA transfers for the CD/DVD drives.

People act like I gave you the finger or something.

..."that is why we have the disable flag to prevent memory saturation."

I have made generous use of the "DisableIfOS="w2k" flag, especially for RAID & SAS.

Good to know.

I would bet dimes to donuts that Sony did not put such an option in that particular BIOS.
  "Is there a BIOS update?" would be another good question, yet one risks "bricking" hardware.  Also, it may not be possible if a battery is damaged.  Tough to risk a flash if there were any potential problems with an RTC battery.

Well ... actually, the chipset drivers have changed.  As you know, they are somewhat interrelated in MassStorage.  I have stumbled upon one bug in the latest chipset drivers regarding Win2k specifically.  Go figure.

The "Yellow Bang!" is indeed a long-standing intel bug.  Is it the only long-standing Intel bug?

From chipset {DriverVer=08/05/2009, 9.1.1.1016} (ich78usb.inf) aka "tried and true":

[Intel]
%PCI\VEN_8086&DEV_27C8.DeviceDesc%=INTEL_USB_2K,PCI\VEN_8086&DEV_27C8
%PCI\VEN_8086&DEV_27C9.DeviceDesc%=INTEL_USB_2K,PCI\VEN_8086&DEV_27C9
%PCI\VEN_8086&DEV_27CA.DeviceDesc%=INTEL_USB_2K,PCI\VEN_8086&DEV_27CA
%PCI\VEN_8086&DEV_27CB.DeviceDesc%=INTEL_USB_2K,PCI\VEN_8086&DEV_27CB
%PCI\VEN_8086&DEV_27CC.DeviceDesc%=INTEL_USB2_2K,PCI\VEN_8086&DEV_27CC
%PCI\VEN_8086&DEV_2830.DeviceDesc%=INTEL_USB_2K,PCI\VEN_8086&DEV_2830
%PCI\VEN_8086&DEV_2831.DeviceDesc%=INTEL_USB_2K,PCI\VEN_8086&DEV_2831
%PCI\VEN_8086&DEV_2832.DeviceDesc%=INTEL_USB_2K,PCI\VEN_8086&DEV_2832
%PCI\VEN_8086&DEV_2834.DeviceDesc%=INTEL_USB_2K,PCI\VEN_8086&DEV_2834
%PCI\VEN_8086&DEV_2835.DeviceDesc%=INTEL_USB_2K,PCI\VEN_8086&DEV_2835
%PCI\VEN_8086&DEV_2836.DeviceDesc%=INTEL_USB2_2K,PCI\VEN_8086&DEV_2836
%PCI\VEN_8086&DEV_283A.DeviceDesc%=INTEL_USB2_2K,PCI\VEN_8086&DEV_283A

Latest chipset {DriverVer=07/09/2013, 9.1.9.1004} (ich78usb.inf) aka "buggy newness":

[INTEL]
%PCI\VEN_8086&DEV_27C8.DeviceDesc%=USB_2K,PCI\VEN_8086&DEV_27C8
%PCI\VEN_8086&DEV_27C9.DeviceDesc%=USB_2K,PCI\VEN_8086&DEV_27C9
%PCI\VEN_8086&DEV_27CA.DeviceDesc%=USB_2K,PCI\VEN_8086&DEV_27CA
%PCI\VEN_8086&DEV_27CB.DeviceDesc%=USB_2K,PCI\VEN_8086&DEV_27CB
%PCI\VEN_8086&DEV_27CC.DeviceDesc%=USB_2K,PCI\VEN_8086&DEV_27CC
%PCI\VEN_8086&DEV_2830.DeviceDesc%=USB_2K,PCI\VEN_8086&DEV_2830
%PCI\VEN_8086&DEV_2831.DeviceDesc%=USB_2K,PCI\VEN_8086&DEV_2831
%PCI\VEN_8086&DEV_2832.DeviceDesc%=USB_2K,PCI\VEN_8086&DEV_2832
%PCI\VEN_8086&DEV_2834.DeviceDesc%=USB_2K,PCI\VEN_8086&DEV_2834
%PCI\VEN_8086&DEV_2835.DeviceDesc%=USB_2K,PCI\VEN_8086&DEV_2835
%PCI\VEN_8086&DEV_2836.DeviceDesc%=USB_2K,PCI\VEN_8086&DEV_2836
%PCI\VEN_8086&DEV_283A.DeviceDesc%=USB_2K,PCI\VEN_8086&DEV_283A

Note that in the newer driver, there is no "USB2_2K"; it is missing.  This may effect all Intel USB2 chipsets.
  This bug is also present in v9.4.0.1017, v9.4.0.1014, v9.3.0.1026, & v9.3.0.1025.
    Chipset v9.2.2.1034 (aka "tried and true") appears clean though.

Also, with the latest chipset drivers, a virgin 2K disc sees all chipset drivers by Intel (at least), as non-WHQL.
  That is possibly an issue with root certs.  Either that or possibly Win2k doesn't like the latest format with nulls between every character.  Note that between the latest Chipset package, and v9.4.0.1017, every .Inf file is twice the size of previous .Inf's.

This will indeed delay any public release to sort it out.  Wednesday yes.  Which Wednesday?  Dunno.

I have to agree that you reacted harshly

Cutting off support for those people seems unneeded and plain stupid to me.

Thank you for calling us "stupid".

http://en.wikipedia.org/wiki/Usage_shar … ng_systems
Windows 2000 usage is so low it doesn't even beat the "all others" category (less than 1%).

Try to look at it from our perspective.  We are trying to support the mainstream OS's because that is what the bulk of the users are using.  By comparison to any OS, Windows 2000 usage is insignificant.  That ship has sailed.
Now if you're looking to Win2k for a learning experience, then that is fine, but don't take your frustrations out on us.

None of the old Win2k drivers in dpms have changed.  Only the .ini structure has changed.  If I were you, I'd start with dpms 12.09 and work backward through the older DriverPacks until I found one that worked, then report those findings here (with your HWIDs).
At that point, someone with free time (of which I have precious little) can assist.

If none of the packs work, then you can set the BIOS to change SATA to IDE (Legacy mode) and it should be fine.

as i stated we will be glad to assist within the confines of the existing program and packs. We have no magic wands. we do have some experience and a couple hours to invest. Just as you have invested yours. Perhaps we have some success.

Help us to help you  (I miss Jaak)

Jeff

@TechD Yes the ram for loading drivers is severely limited in 2k it grows with each OS version. that is why we have the disable flag to prevent memory saturation. in this way one can simply edit the txtsetup.sif file and deledte a few semicolons and add a few without re-slipstreaming the drivers. If you get the ntf.sys error to many drivers are enabled. At least Wim made it easy to change and retest. couple of semi colons in a text editor and burn and test. Core files may be missing to get SATA to spark (a hotfix / KB that was never written). as an alternate perhaps not SATA mode will work just fine .