426

(42 replies, posted in Hardware)

The strictly fictitious semi-biography of Gollum:

He was just a regular hairy-footed IT worker heavily invested with IBM Networking (involving untold man-hours of research and development) until one fateful day when he was ordered to deploy a new networking environment in it's stead.
  In a fit of madness and uncontrollable rage, he grabbed his "Tolkien Ring" console, disabling the network in the process, and stormed out of the building yelling "My Precious!" frantically and repetitively as he ran, trailing hermaphroditic connectors behind him.
    His employer, an IT wizard in his own right, was so disgruntled about the theft and lack of civic response, that he organized an action committee - a Fellowship if you will - led by a hairy-footed junior intern to reclaim company property and eventually see it properly recycled in the fire caves where it's evil reign began.

When the group finally caught up with him, the gear and it's arcane concepts had changed him startlingly into a physically gaunt and bitterly divided man.
  They fought like h*ll to get it away from him and finally succeeded, risking their own lives in the process from that madman.  Some were hospitalized for their wounds, one was seriously injured.


Thankfully, like Eddie Van Halen*, Gollum is today recovering in Bellevue, and purportedly "making progress".
  Sadly though, nurses say he can still be overheard angrily mumbling incoherently to himself once in a while.


* reference:  "Hot For Teacher" Video

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

427

(42 replies, posted in Hardware)

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

http://forum.driverpacks.net/img/avatars/5558.jpg

Gollum wrote:

"And leave things like religion and age, and general insulting out of your messages, otherwise i turn up, and then you dont get as measured a response from me as this one  smile"

     Quoted from:  http://forum.driverpacks.net/viewtopic. … 531#p39531

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


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

428

(19 replies, posted in BartPE - UBCD4Win - WinPE)

edit:  updated DP_Lan Nightly here --> http://forum.driverpacks.net/viewtopic. … 692#p52692

Remove the "old" LenLan.inf and files before installing the "new" LenLan.inf on an existing system.
  LenLan.sys should be removed from Windows\system32\drivers\ and the corresponding OEM##.inf from Windows\Inf first.

Let me know how it works out please.

One other issue you may experience is the violation of 8.3 file naming conventions in ax88179_178a.sys.
  If true, they can be renamed for the next nightly.


Now one should only need integrate WdfCoInstaller01009.dll instead of "1009" and "1007".


From http://forum.driverpacks.net/viewtopic. … 727#p49727:

"After integration with DP_BASE, XP was installed on non-USB3.0 hardware (without a BSOD).  Unfortunately, the wdf01000 non-PnP driver was installed and the Errors previously mentioned exist in EventViewer.

I think the final solution for Fresco/VIA USB3 textmode support (and other KMDF 1.9 drivers) was to slipstream the files & registry entries in the source, as you have noted.

Jim D. wrote:

"Microsoft does not support coinstallers in WinPE.
Vishal kindly listed for me the steps required to get KMDF installed in my
WinPE image. These are:

1) adding wdf01000.sys to the WinPE image,
2) adding wdfldr.sys to the WinPE image, and
3) Adding a couple of registry keys in setupreg.hiv.

We have implemented these steps, and are now able to successfully boot WinPE
with a KMDF PnP driver."
  from --> http://www.winvistatips.com/winpe-wdf-w … 91658.html

"

Note that those files and keys are extracted from "Microsoft Kernel-Mode Driver Framework Install-v1.9-Win2k-WinXP-Win2k3.exe" contained in "WdfCoInstaller01009.dll".

Updated AuthenTec TruePrint AES1610/1660/2501B/2550/2660/2665/2810  {DriverVer=08/01/2011,9.0.9.36}
  (Class=Biometric) in AU2 to prevent "Code 39" & Yellow Bang!
    The included wdfcoinstaller01009.dll was for MachineType=64 only.

DP_Biometric_wnt5_x86-32_1308151.7z - 11.6 MB   5019c4f233db89fd358e662cb7f7bebe5d0cd5a8     big_smile

edit: link removed - latest nightly near last post of this topic

...updated ASIX drivers including LenLan (Ax88760/Ax88772/a/b/c),
added Broadcom Ports & updated unreferenced diagnostic driver.

DP_LAN_wnt5_x86-32_1308161.7z - 10.2 MB   db77c12967cd12da5d56b41807398aedee8fcdcc     smile

edit: link removed - updated in first post

431

(19 replies, posted in BartPE - UBCD4Win - WinPE)

The latest drivers from ASIX use only WdfCoInstaller01009.dll to be included in the next Nightly.

I remember an article from the USB 3.0 textmode support discussion that detailed how to integrate Wdf.
  I will try to find it later.

Attempting to edit "new" LenLan.inf to reflect updated ax88772b driver.

432

(19 replies, posted in BartPE - UBCD4Win - WinPE)

Both of those drivers rely upon their respective WDF coiinstallers, WdfCoInstaller01007.dll & WdfCoInstaller01009.dll.
They may need be integrated into PE.  I don't know how to best accomplish that though.  Open either with 7zip and you will see what i mean.

Could you post a link to the manufacturer's page so that ax88772b USB\Vid_17ef&Pid7203 may be included in the latest DP_LAN Nightly?

Updated --> DP_Misc_wnt5_x86-32_1308021.7z - 23.7 MB   286357a21c024205c893fb2dff313647e5d1c9d3

edit: link removed - updated below

Known issue:
Ricoh "ptsk" CardReader devices cause errors and bluescreen on Win2k.

updated generic conexant driver
here --> DP_Modem_wnt5_x86-32_1308021.7z - 32 MB   f2f0441de1997e5945bc05c527f6e46073566de1

*edit:  link removed - updated below

It's on "the list".     smile

... and updated to support generic/OEM WLAN utilities
DP_WLAN_wnt5_x86-32_1307241.7z - 28.2 MB   2ff5833e7c0f61ba9869b1791b280090c758e77c


edit:  broadcom utilities (DP_WLAN addon - for 3rd-Party folder):
DP_WLANutils_wnt5_x86-32_1307252.7z - 115 MB   e570ebdddf2c90b2f85d49a5cb37ee645993b2e1


edit: link removed - updated below

...Realtek drivers updated yet again.
DP_LAN_wnt5_x86-32_1308021.7z - 10.2 MB   ba5819f1b5dd38799c1d6c62c1537f03f25dbdf3

edit: link removed - updated

Well, how about this one instead?     hmm
  It fixes soundfont synth driver install for Audigy 2/4 ZS Notebook.
here --> DP_Sound_A_wnt5_x86-32_1308021.7z - 154 MB   a1e2aba0d5b3b3d9cbc55d616da04c8552452d18

*  edit:  links removed - updated below

Included from Official Release previous Win2k WHQL drivers.
Included Intel Matrix 5.7.0.1011 for Win2k AHCI/RAID support.
Included Intel iSCSI textmode support for Win2k3.
here --> DP_MassStorage_wnt5_x86-32_1308132.7z - 9.29 MB   451f0bc75252e2c26b8e1d55ad03080871897268

edit: link removed - updated in first post

The latest Win2k-friendly Nightly is here -->  DP_Chipset_wnt5_x86-32_1308131.7z - 7.14 MB   bf9c267c3b215a2d27bfbac685c994c7449ce6e7

edit: link removed - updated

Why do they call it an "eyePhone"? ... OWW!!!  My eye!"  -  Phillip J. Fry

What "automatic iphone driver install" are you referring to?
  As for finding drivers, they are likely included in "eyeTunes".

442

(42 replies, posted in Hardware)

Actually, you didn't qualify your statement.
  When read in order and context, it does indeed read like a "verbal bird".

mr_smartepants wrote:

"Therefore, DriverPacks support for 2000 has ended also."

silents429 wrote:

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

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

OverFlow wrote:

"I have to agree that you reacted harshly"

  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.

DH89xxCC-usb now lacks two HWID's.
patusb now has no UHCI/OHCI support.
ich6usb & ich5usb have had their 2k3 coinstallers moved.
wptusb has reg. entries missing for XP/2k3.

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.

443

(42 replies, posted in Hardware)

OverFlow wrote:

..."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.

"If you get the ntfs.sys error too many drivers are enabled."

Good to know.

mr_smartepants wrote:

... "you can set the BIOS to change SATA to IDE (Legacy mode)" ...

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.

"None of the old Win2k drivers in DriverPack MassStorage have changed."

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.

"If we could see those frequencies with our eyes" ...

It might look something like this:
  http://www.dailymail.co.uk/sciencetech/ … -them.html

No peeking if visualizing such frequencies is illegal in your jurisdiction!

445

(42 replies, posted in Hardware)

I disagree, that did have the tone of disrespect.
  As for " time well spent", so far it seems like time well wasted.


By the by, it is probably just as well that 2k doesn't have a wireless client, generally if an Atheros module is present.
  Any latency gains via NT5 are often more than negated with such "WinModems".

WiFi sucks compared to wired Lan anyway, and not just performance-wise.
   http://www.waldorftoday.com/2013/07/stu … fi-router/
  If you are adamant that there are no biological effects attributable to WiFi, goggle "Microwave Auditory Effect".
    Anybody with a pacemaker may readily testify to other negative effects.

Disable WiFi for your Win2k no matter what you do.
  The drivers are likely horribly out-of-date, certainly if they don't support WPA2.
     I wouldn't doubt that "pwnage" is only a local teenager (or more) away!


BTW, if you need a modern OS, and price sensitivity is of issue, try a linux Live! disc.
  Download, burn, boot from it, try linux!  Don't install yet, it will render a NT5 install non-bootable (more later).
Mint seems most popular, though am not certain if their Ubuntu derivatives are sending search keywords to Amazon.
  http://distrowatch.com/table.php?distribution=mint
   Mint-debian does not behave in such a way AFAIK, though not generally regarded as "newby-friendly".
     The Knoppix (debian) live DVD has long been a favorite of mine as it comes with Wine (Windows emulator).

Dual-boot is certainly achievable, though not immediately intuitive.
  http://newfyworld.hubpages.com/hub/How- … s-7VistaXP


The notebook itself, as most vintage hardware, may have some caveats.

If there are problems with the clock keeping proper time, or "settings" that won't hold, you may need a new RTC battery.
  Many models (especially newer) use a replaceable CR2032 or similar, while others use a non-replaceable "VR" variant.  The units with non-replaceable "VR" variants often have instructions to charge the unit for a day or so in user manuals.  RTM, if effected.

If tearing your notebook apart isn't your forte, then i won't mention anything else about internal maintenance.

  Speaking of batteries, as they age the "internal resistance" grows, as does the risk of fire.
    An older battery pack will tend to get hot during discharge.
      Before recharging an older battery under such conditions, it is best to allow it to cool first.
        Charging might be best done while the notebook is off.
          "Your mileage may vary".

446

(42 replies, posted in Hardware)

Actually, all i had to do was split the [ I] portion of MS.ini with "skipIfOS", add Matrix v5.7 in [IE], then for bonus points included HWID's in a similarly split [I3] folder (supposed to only support Adv. Server) for ICH7/8, etc.

Of course this was after determining that "LSI Logic MegaRAID/Intel RAID II (W2K)" could no longer work after an earlier update (now in [L9-0]).  Several other drivers interfered with "insufficient memory" errors with 2GB (those were fst376kk, fast2k2k, ulsata2k, pnp680, SI3112, SISRAID2, SISRAID, & SISRAID4).
  Ah, the utility of "skipIfOS"!

The ntfs.sys errors may have been related to the driver for "Promise Ultra133TX2/Ultra100TX2/Ultra66/33 IDE", as ultra66.sys is included in the OS.
  There was another possibility that eludes me at this moment.  I believe "skipIfOS" fixed that too.

Whilst i was at it, iSCSI support was added for W2k3 only, and the HWID "PCI\VEN_8086&DEV_2651&CC_0106" was returned to [I3], where it belongs though it may be a "red herring".

It was necessary during integration to use DPs_BASE 10.06.  The newer alpha may have worked without the M2.7z mod, yet i liked the idea of separating the two NT5 branches on my hdd.
  A minimum of packs, Chipset, Lan, MassStorage and the 3rd party Misc seemed to fit with the extreme Path Length restrictions.
However; including the DP_Misc pack resulted in "multiple" bluescreens (or bluescreens for multiple reasons) with the included Ricoh cardreader drivers.  I stuck with Chipset, Lan and MassStorage.

Even that wasn't without issue, as Intel USB2 devices have "Yellow Bangs!"

I still have some testing to do, that does include ensuring that XP is not negatively effected.
  I doubt any negative effect, as the "new" w2k files do not integrate in my XP_test folder, yet will test for sanity's sake.

With or without the Intel USB2 issues, this updated pack could be public as early as Wednesday.

mr_smartepants wrote:

"But I wouldn't waste any more time on 2000 support."

Indeed.  Therefore, any Win2k support from here on in will be strictly unofficial.

Can you remember which packs had the best official support? 
   It would be good to direct prospective users, and properly tell them where to go for support.

silents429 wrote:

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

Easy there, fella!
  If it were not for mr_smartepants, XP support would still be stuck circa 2008.
    To him i reserve a great deal of deference and respect, and not simply for that fact.
  He is patient to the point of long-suffering, talented and gracious yet amazingly not narcissistic. 
I say this not to beam sunshine up his posterior, yet because every word is true.     smile

Please don't take your frustrations out here on any of the many wonderful volunteers.


"I'm free, And freedom tastes of reality," - The Who, Tommy

447

(42 replies, posted in Hardware)

Admin?

448

(42 replies, posted in Hardware)

With the "ntfs.sys is corrupted" errors behind me, i have run into more than one major snag.

"H:\OEM\bin\DEVPATH.exe is not a valid Win32 application"

It would seem that DPs_BASE_1109012 (the version i'm testing with here - with M2.7z mod) does not support Win2000.
The public version DPs_BASE_1006 might support Win2k.

It is working on officially supported AHCI hardware otherwise, though.  Setup completes.
Unfortunately, during initial boot, post-GUI Setup, it bluescreens with Stop $7B - Inaccessible_Boot_Device.

edit:  DPs_BASE_1006 does support Win2k, no bluescreen this time, Desktop instead.

Only integrated Chipset, Lan, MassStorage, & Misc to avoid severely-limited DrvPath.

mr_smartepants wrote:

"Win2k has a 255 character file path limit.  XP has a 4096 character limit."

      Quoted from:  http://forum.driverpacks.net/viewtopic. … 531#p39531

Anyway, Admin says that i am done.  Pity, i've spent a good day of my time on this.

edit2:  I am done.  It works.  XP Setup still works too.  Now what do i do?

449

(42 replies, posted in Hardware)

"the file ntfs.sys is corrupted" errors are plaguing me now, even on "atapi".
Attempting to comment-out drivers in txtsetup.sif.

I note that MS seemingly makes it impossible to report directly to them, concerning others possibly infringing upon their own IP.