76 Reply by TechDud

(4 replies, posted in 3rd Party DriverPacks)

v1410151
Added:
 -H\4\ (dmb5000.inf) Hauppauge DMB5000 WinTV DMB-T USB2 Stick (from wintv7_cd_3.9)
       (hcw17bda.inf) Hauppauge SMS1000 TS Capture
       (HCW723x.inf) Hauppauge WinTV 723x models
       (hcwD1cap.inf) Hauppauge Colossus PCIe capture device
       (hcwD1enc.inf) Hauppauge Colossus Encoder
       (hcwF9bda.inf) WinTV-Ministick 2/PCTV 78e/PCTV 79e/WinTV Duet 2/PCTV 2003e
       (smsbda.inf) Siano Mobile Silicon PCTV microStick (77e)
       (UD252D_happ2.inf) Hauppauge DMB-T MiniStick
 -MS\ (irbus.inf) eHome Infrared Receiver  {DriverVer=07/01/2001,5.1.2535.0} IrBus.sys v5.1.2600.2180
Updated:
 -H\4\ (hcw72bda.inf) WinTV HVR-950q USB2 Stick (NTSC/ATSC/QAM) to {DriverVer=08/15/2014,1.101.32227.0}
       (hcw85bda.inf) WinTV PCIe(x1) CX23885/7/8 AVStream video/audio capture to {DriverVer=09/23/2014,1.54.32266}
       (hcw89.inf) Hauppauge WinTV-HVR-22xx to {DriverVer = 09/17/2014,7.9.1.32260}
       (hcw713x.inf) Hauppauge WinTV-HVR 1100/1105/1110/1150 Capture to {DriverVer = 02/20/2014,1.40.1.32051}
       (hcwC6bda.inf) Hauppauge WinTV-Aero/Dell Digital TV Receiver to {DriverVer=12/11/2012,61.9.7.30346}
       (hcwD9bda.inf) Hauppauge WinTV-NOVA SAT to {DriverVer=07/02/2014,1.34.32183}


v1410141
Removed:
 -*.devicemetadata-ms (nt6)
 -invalid .cat files, incl. .inf references
 -AV\i\CIRCoInst.dll (nt6)


v1410121
Moved:
 -H\0, H\00, H\5 through H\a, H\j, H\l through H\q & H\s through H\z to H\4\
 -H\k to H\
Renamed:
 -H\c to H\0\

for post-Windows Setup utilizing SAD3:
DP_TVcard_wnt5_x86-32_1410151.7z - 60.84 MB   FE3C6C9839B36D8521046B6C00A98182DBA844EB

Go to forum: 3rd Party DriverPacks

77 Reply by TechDud

(8 replies, posted in 3rd Party DriverPacks)

Imported from DP_Chipset_wnt5_x86-32_1409121\D\C\U\M:
-MS\ (SER2PLMS.INF) Microsoft USB GPS Port (Prolific PL2303)  {DriverVer=07/20/2004,2.0.0.26}

for post-Windows Setup utilizing SAD3:
     - potential for exceeding maximum path-length if included in 3rd-Party DriverPacks folder
DP_Phone-Mobile_wnt5_x86-32_1409121.7z - 15.42 MB   4EA613626C67AB59D322EF2D195FC278DEE394CC

Go to forum: 3rd Party DriverPacks

78 Topic by TechDud

(4 replies, posted in 3rd Party DriverPacks)

This pack is based upon DP_TVCard_wnt5_x86-32_1005b1

v1410071
Added:
 -C\7\1\ Conexant 23880 Blackbird from sp26281.exe
		(might need to break WHQL signing in future for drivers in C\7)
 -H\c\1\ Hauppauge WinTV NOVA (usb218c)
 -H\c\2\ Hauppauge WinTV NOVA (pci218)
 -H\c\3\ Hauppauge WinTV-Nexus (dvb218c)
 -H\c\4\ Hauppauge DEC USB Device (dec218c)
 -H\j\ Hauppauge WinTV-Aero
 -H\k\ Tivizen Mobile TV USB (CDC/ECM)
 -H\l\ Hauppauge HD-PVR2
 -H\m\ Hauppauge HD PVR USB capture
 -H\n\ Hauppauge WinTV NOVA-S-USB2
 -H\o\ Hauppauge Nova-DT (Dual tuner DVB-T)
 -H\p\ Hauppauge PVR USB2 AVS Video Capture
 -H\q\ Hauppauge WinTV-CI USB (11xxx)
 -H\s\ Hauppauge WinTV HVR-950q USB2 Stick (NTSC/ATSC/QAM)
 -H\t\ Hauppauge WinTV-HVR 1100 (WinTV-HVR 713X)
 -H\u\ Hauppauge WinTV 418/HVR-1600 Video Capture
 -H\v\ Hauppauge WinTV HVR-19xx
 -H\w\ Hauppauge WinTV-NOVA SAT
 -H\x\ Hauppauge WinTV-Nova-T(D)
 -H\y\ Hauppauge Cx2310x (WinTV HVR-111xxx) Capture
 -H\z\ Hauppauge WinTV-DCR 2650 (experimental CIRCoinst.dll dependancy fix for nt5)
Moved:
 -H\ to H\00\
Removed:
 -C\7\ layout.bin
 -H\1 FILE000*.DAT, PROGRESS.DLL, W32INST.DLL, WISE0001.DLL
Refreshed:
 -H\2\ Hauppauge WinTV 848/9, 878/9 WDM
 -H\3\ Hauppauge Computer Works USB-based device
Restored:
 -H\0, H\7, H\9 & H\a\ Restored folder structure specified in .Infs
Updated:
 -H\00\ Hauppauge CX23885/7/8 AVStream video/audio capture (PCIe x1) to {DriverVer=11/07/2013,1.51.31310}
 -H\4\ Hauppauge eMPIA USB 2.0 Video Devices (EM28xx) to {DriverVer=06/02/2010,5.10.325.28153}
 -H\5\ Hauppauge WinTV-HVR-900H to {DriverVer=02/08/2011,1.0.709.29039}
 -H\6\ Hauppauge WinTV (88x) to {DriverVer=11/20/2012,2.126.30325}
 -H\8\ Hauppauge hcw89 PCIe capture to {DriverVer = 07/18/2014,7.9.1.32199}


v1410031
Added:
 -Ad\ Adaptec AVC-1100/AVC-1200/AVC-2010/AVC-2210/AVC-2310/AVC-2410
 -Ad\1\ Adaptec AVC-2000
 -Ad\2\ Adaptec AVC-2200
 -AV\1\ AVerMedia AVerTV USB
 -AV\4\1\ AVerMedia AVerTV Video Capture/PCI Analog TV
 -AV\4\2\ AVerMedia AVerTV Video Capture/PCI Analog TV
 -AV\9\ AVerMedia 23885 AvStream Video Capture (XCeive)
 -AV\a\ AVerMedia H826(D) USB Pure ATSC/QAM
 -AV\a\1\ AVerMedia A827 USB Hybrid DVB-T/A827A(C) USB Pure Analog
 -AV\a\2\ AVerMedia A816 USB Hybrid DVB-S/AVerMedia Ethernet Adapter for MPE
 -AV\a\3\ AVerMedia R889 USB DVB-S2/AVerMedia Ethernet Adapter for MPE
 -AV\b\ AVerMedia A700(DVB-S/Analog)/AVerMedia Ethernet Adapter for MPE
 -AV\b\1\ AVerMedia SAA713x
 -AV\c\ AVerMedia AVerBDA6x
 -AV\c\1\ AVerMedia AVerBDA6x
 -AV\c\2\ AVerMedia AVerBDA6x
 -AV\c\3\ AVerMedia AVerBDA6x
 -AV\d\ AVerMedia USB Polaris Series Capture
 -AV\d\1\ AVerMedia USB Polaris Series Capture
 -AV\d\2\ AVerMedia USB Polaris Series Capture 
 -AV\d\3\ AVerMedia USB Polaris Series Capture 
 -AV\d\4\ AVerMedia USB Polaris Series Capture 
 -AV\e\ AVerMedia 7231 capture
 -AV\e\1\ AVerMedia H968 Hybrid Analog/DVB-T
 -AV\f\ AVerMedia USB Video Capture Family (A868/E509/E882/HC80/M038/M039)
 -AV\g\ AVerMedia USB 2.0 Plus Video Capture
 -AV\h\ AVerMedia A855 II USB DMB-TH
 -AV\i\ AVerMedia A852 USB DMB-TH
 -AV\j\ AVerMedia DVB-T BDA Video Capture
 -AV\j\1\ AVerMedia DVB-T BDA Video Capture
 -AV\j\2\ AVerMedia DVB-T BDA Video Capture/A805 (USB, DVB-T)
 -AV\k\ AVerMedia A820 USB DVB-T
 -AV\k\1\ AVerMedia A836 USB DVB-T
 -AV\k\2\ AVerMedia A835(B) USB DVB-T/A918R Express DVB-T
 -AV\k\3\ AVerMedia A867 USB DVB-T
 -AV\l\ AVerMedia DVB-T BDA Video Capture (A300/A808/E568)
 -AV\m\ AVerMedia A855 USB DMB-TH
 -AV\n\ AVerMedia C027 PCIe HD Capture Device
 -AV\n\1\ AVerMedia H727 PCIe Hybrid DVBT HDMI Capture Device
 -AV\o\ AVerMedia H777 Hybrid DVB-T
 -AV\p\ AVerMedia C873 USB IR Blaster
 (XP-MCE encoder/plugins supported in new DriverPack_TVcard_wnt5_x86-32.ini)
Removed:
 -AV\8\ duplicated in AV\


v1409251 - TechDud
Added:
-Ad\ Adaptec AVC-3610/3310/3210
Moved:
 -A2\ through A6\ to A\2\ through A\6\
 -AV2\ through AV8\ to AV\2\ through AV\8\
 -C1\ through C9\ to C\1\ through C\9\
 -D2\ to D\2\
 -G1\ through G6\ to G\1\ through G\6\
 -GE2\ to GE\2\
 -H0\ through Ha\ to H\0\ through H\a\
 -K1\ through K8\ to K\1\ through K\8\
 -L1\ through L4\ to L\1\ through L\4
 -LI1\ & LI2\ to LI\1\ & LI\2\
 -P0\ through Pa\ to P\0\ through P\a\
 -T0\ through Ta\ to T\0\ through T\a\
 -TH0\ through THa\ to TH\0\ through TH\a\
 -V2\ & V3\ to V\2\ & V\3\
 -Y1\ through Y3\ to Y\1\ through Y\3\

for post-Windows Setup utilizing SAD3:
     - potential for exceeding maximum path-length if included in 3rd-Party DriverPacks folder
DP_TVcard_wnt5_x86-32_1410071.7z - 56.44 MB   38999F41150C9CE72EB8F6CD2FBA2D6FF87344CF   smile

edit:  link removed - updated below

Go to forum: 3rd Party DriverPacks

79 Reply by TechDud

(10 replies, posted in 3rd Party DriverPacks)

v1410141
Updated:
Ap\ Apple iSight camera to {DriverVer=10/25/2007,2.0.1.0}

v1410041
Added:
Rt\3 Lenovo Realtek Integrated Camera Driver {DriverVer= 05/16/2014,6.2.9200.10277}
Updated:
A\A\1 Alcor Lenovo EasyCamera (LiteonVGA-016F) to {DriverVer =04/30/2013,2.22.23.107}
Sp\3  Lenovo SunplusIT Integrated Camera (LiteonHD-119B) to {DriverVer=06/11/2013,3.4.5.11}
Sp\B\0 (SPSPbv.inf > SPUVCbv.inf) Lenovo SunplusIT Integrated Camera to {DriverVer=02/10/2013,3.4.7.31}
V\23 Lenovo Vimicro USB2.0 Digital Camera (BisonVGA,ChiconyVGA,LiteonVGA-023A) to {DriverVer = 04/30/2013,1.13.430.3}

for post-Windows Setup utilizing SAD3:
     - potential for exceeding maximum path-length if included in 3rd-Party DriverPacks folder
DP_WebCam_wnt5_x86-32_1410041.7z - 84.49 MB   1E2BDA62BB2A5FD87B4BB4556DF9504B061B8569   smile

Go to forum: 3rd Party DriverPacks

80 Reply by TechDud

(525 replies, posted in Windows 7 tools)

That would appear to be a variety of hybrid graphics known as Optimus.
The drivers are simply missing from the pack, and might require manual installation via nVidia's associated setup program.  Sadly, processing exceptions are not yet supported.  Discussing that might be relevent in this topic, though am not certain.

It doesn't appear to be a bug per se with SAD3.
  Please start another topic to continue this discussion with more info.  (32/64bit? HWIDs??)

Go to forum: Windows 7 tools

81 Reply by TechDud

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

This should be resolved now.
Lenovo released a new "LenLan" driver shortly after the previous conversation here.
It is included in the latest DP_LAN_USB pack in Testing.

For now, an updated experimental Wdf plugin pack is available
here --> http://forum.driverpacks.net/viewtopic. … 302#p58302  smile

Go to forum: BartPE - UBCD4Win - WinPE

82 Reply by TechDud

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

updatum:
Test Packs:
USB3-Controller-Hub-Wdf_NT5_BartPE-UBCD4Win_Plugins_Test.7z - 432.76 KB   C853A8053F4399C399116B7EDF245F3CD2220FC9
USB-LAN-Wdf_NT5_BartPE-UBCD4Win_Plugins_Test.7z - 316.16 KB   20425665F14C0B674C6EB7DCFABC6B99914A33B4

Go to forum: BartPE - UBCD4Win - WinPE

83 Reply by TechDud

(43 replies, posted in DriverPack Graphics)

for DriverPacks folder:
DP_Graphics_A_wnt5_x86-32_1401181.7z - 117.45 MB   BB24C55735A704701862DE1B00A9E9AD6C006D69
DP_Graphics_B_wnt5_x86-32_1409243.7z - 215.17 MB   3BFF2B20929B0EBC2079AA1FF96318499A10E579
DP_Graphics_C_wnt5_x86-32_1409242.7z - 186.48 MB   67D8CD7A1EF2083A966688C92A90CD92C5613449

for 3rd party DriverPacks folder:
* DP_Graphics_ATi_Runtimes_wnt5_x86-32_1310151.7z - 21.0 MB   81b4fcc8e3d2f112b780fc82b38377bc0a1314ba*
DP_Graphics_ATi-Hydravision_wnt5_x86-32_1401181.7z - 12.71 MB   11506C801884F6F8BF4DC9EC4AEDF456A04497F2
DP_Graphics_ATi-Legacy_wnt5_x86-32_1312081.7z - 118.71 MB   a8d189246d1b0d48dd3c0ce7e1785629b54089d2
DP_Graphics_ATi_OpenCL-vc2k10_wnt5_x86-32_1312081.7z - 10.39 MB   4cd10c4ac8ff83995b759584afb9afb8e1d97d6b
DP_Graphics_ATi-TV_wnt5_x86-32_1310291.7z - 8.45 MB   e40bba47ecd213387f8fe6e71825ae78b8ebccd7
DP_Graphics_D_wnt5_x86-32_1409241.7z - 146.75 MB   89A3A9FA3FEABFB9D9491053D6D923BF9861C66F
DP_Graphics_Intel_Runtimes_wnt5_x86-32_1312071.7z - 34.32 MB   860b02399667d7eb81a18d2197e064723118c275
DP_Graphics_Languages_wnt5_x86-32_1409241.7z - 78.58 MB   465D8976447A9B6979137FC1916B1007B1A54149
DP_Graphics_nVidia_GFxp-upd-NET4_wnt5_x86-32_1409241.7z - 111.81 MB   1A783B3B041221671C178D97E638CFD78B9A9D03
DP_Graphics_PhysX_wnt5_x86-32_1409242.7z - 56.43 MB   7719F81583E18410A41B3EE1FE0BC85494ADB04B
DP_Graphics_PhysX-Legacy_wnt5_x86-32_1310271.7z - 18.5 MB   7e5df14e2c44335ed3a60e5591ea68f07175b730

for post-Windows Setup utilizing SAD3:
DP_Graphics_USB_wnt5_x86-32_1411241.7z - 32.49 MB   9CDA9874ECFFDCE038F9E57A1CBC22F0B814D225

* note:  not backwards compatible with Official Releases or previous ATi-related Graphics nightlies previous to July 12, 2013

Deprecated: obsolete = delete
DP_Bluetooth
     - superseded by DP_Bluetooth_MS-Misc_wnt5_x86-32_1xxxxxx.7z
DP_Graphics_3dfx-ATi_wnt5_x86-32_130xxxx.7z, DP_Graphics_External_wnt5_x86-32_1xxxxxx.7z,
DP_Graphics_nVidiaUpdaters_wnt5_x86-32_130xxxx.7z + DP_Graphics_nVidia_GFxp-NET4_wnt5_x86-32_130xxxx.7z
     - both combined into DP_Graphics_nVidia_GFxp-upd-NET4_wnt5_x86-32_yymmdd#.7z


Test Archive (not a DriverPack, yet unofficially useful for non-ATi-AMD OpenCL-CPU - SSE2.x{min}):
Ati-AMD_OpenCL_Test.7z - 85.24MB   9b7c6808816f9a4329becfe57d323a5741680376
updated (2013-11-16)

Haswell Graphics/Sound Test pack:
4thGenHaswell_Graphics-HDAudio_NT5_TestPack.7z - 14.65 MB   6F3E80C2C015ECB6E2AE70A57B028168F0441879

Go to forum: DriverPack Graphics

84 Reply by TechDud

(8 replies, posted in DriverPack LAN)

OverFlow wrote:

"Perhaps people with XP have been reading your thread?"

478 views of this topic reveals it to be purely coincidental.  How was my timing?  (prolly 6mos too late, durnit)

Go to forum: DriverPack LAN

85 Reply by TechDud

(11 replies, posted in Vista / 7 DriverPack LAN)

Had mentioned those nVidia Chipset packs because they contain Ethernet drivers.

The driver included in DP_LAN_wnt6_x86-32 restricts installation to Vista only for that particular HWID (etc).

Editing the included driver included in DP_LAN_wnt6-x86_1208.7z/x86/All/L/Nvidia/1/nvfd6x32.inf  {DriverVer  = 11/11/2009, 73.2.0} or that within  nVidia Chipset v15.56 (v73.3.0) (linked above) should yield at least one working driver because there is a [NVENET67_WIN7.NDI.NTx86] section within either .Inf file.  The same modification should work for both revisions of Ethernet driver.

Am assuming that it is better to modify that Ethernet .Inf file within Chipset v15.56 (v73.3.0) first, and then manually update it with devmgmt.msc.

Note that you most likely will have to manually update it via Devmgmt.msc, as edits break WHQL signing.  At least you are using Win7 32bit which is less restrictive than 64bit for modified drivers.

Had mentioned the Chipset packages, as those officially support your hardware according to nVidia's website if i remember correctly, athough it would appear nV lists that in error.  After downloading, i was unable to view the contents before my first reply as linux's Archive Manager isn't as flexible as i had hoped.  At least the license is free, so i cannot complain.

I hope this clarifies the situation.  Your Mileage May Vary.

Go to forum: Vista / 7 DriverPack LAN

86 Reply by TechDud

(11 replies, posted in Vista / 7 DriverPack LAN)

Have you tried manually updating the driver from nVidia Chipset v15.56, v15.49, or v15.37?

If none of the drivers above work, then you might try manually editing the existing driver to add your HWID.

DP_LAN_wnt6-x86_1208.7z/x86/All/L/Nvidia/1/nvfd6x32.inf
under the line "[Nvidia.NTx86.6.1]", add the following, then manually update driver.

%NVENETFD.DeviceDesc%  =  NVENET67_WIN7.NDI,          PCI\VEN_10DE&DEV_054C
%NVENETFD.DeviceDesc%  =  NVENET67_WIN7.NDI,          PCI\VEN_10DE&DEV_054D
%NVENETFD.DeviceDesc%  =  NVENET67_WIN7.NDI,          PCI\VEN_10DE&DEV_054E
%NVENETFD.DeviceDesc%  =  NVENET67_WIN7.NDI,          PCI\VEN_10DE&DEV_054F

Please let us know what works for you, so it may be added to upcoming [Nightlies] & releases.

Added [REQ] to topic name, & moved topic to Vista-7-8 LAN...

Go to forum: Vista / 7 DriverPack LAN

87 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

That is understandable.  It makes no sense to risk vital equipment.  I have a couple of boards with Si3x12's, and an expansion card or two. (CMD640, Si0680)  However; that is the limit of my current Silicon Image Mass Storage repertoire at the moment.

It would be nice if somebody reading this whom has a Silicon Image SATA adapter would itegrate the current DP_MassStorage_wnt5_x86-32_1411031.7z (updated by Symbios24) to their XP disc using DPs_BASE and do a test installation with a spare hard drive, so as not to risk existing data.

Any help that leads to corrections or solutions gets credited in changelogs
(and to be publicly thanked in this forum by myself at least).

Go to forum: DriverPack Mass Storage

88 Reply by TechDud

(4 replies, posted in Other)

Time Zone Updates should be the first place to look, if i have that correct.
  If you have included POS updates, it could be either KB2981580, or KB2998527.

Maybe the text for Greek had been changed lately, or some time previous.
Check the .Inf files within.  Extraction is easy via command line.
KBxxxxxxx.exe /passive /norestart /extract:C:\newfolder - also see:  http://support.microsoft.com/kb/262841

Notepad++ & the "compare" plugin are good tools for comparing .Inf file contents.  Even the updated "compare" plugin isn't perfect, yet works well for the majority of incrimental update .Inf files.  Have been meaning to try WinMerge, which is purportedly another good tool for comparing .Inf files.  There are likely more available from their respective Authors to choose from.

I thank you for starting a new topic for this question.  smile

Go to forum: Other

89 Reply by TechDud

(8 replies, posted in DriverPack LAN)

Title:  "Windows XP market share FELL OFF A CLIFF in October"
http://www.theregister.co.uk/2014/11/02 … n_october/

Go to forum: DriverPack LAN

90 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

@OverFlow - Have you still the hardware?

@Symbios24 - Ah, those two aforementioned HWID's could be in a variety of hardware, including Lenovo G405/G505 series, by the way .

Go to forum: DriverPack Mass Storage

91 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

PCI\VEN_1002&DEV_7001&CC_0106 & PCI\VEN_1002&DEV_7004&CC_0106 are the HWID's that need verification.  As you can understand, it gets a little complicated when Chipmakers reuse the same HWID in different drivers for incompatible products.  nV was bad for that years ago.

  At least we were able to use "Sherlock Holmes" methodology.  That is "deductive reasoning".
We have a good theory to test now.

Sometimes "crisis" can translate as "opportunity".    smile

Go to forum: DriverPack Mass Storage

92 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

Nice work! 

That should have read "rcraid2", yet it matters not what the driver is displayed as, as much as it matters that it doesn't bluescreen again.  Now "ahci886" should be driver name in pre-partitioning textmode.
(Noting some drivers show as "unknown" on Win2k, & i don't yet know why, though it matters not for your XP.)

Do we have confirmation yet if DP_MassStorage_wnt5_x86-32_1411031.7z fixes the problem, or does it bluescreen, and where does it bluescreen if so?

Thank you again, Symbios24!     smile

Go to forum: DriverPack Mass Storage

93 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

Symbios24 wrote:

"i added with nlite the v3.3.1540.33 in the same windows source, and now it detects the controlled but when the windows setup is finished there is another driver installed in the Scsi-raid controllers section in device manager ämd raid controller 13/9/2013 v6.1.2.5"

So, the driver actually works for that HWID?  That's an easy fix.     smile

Move "PCI\VEN_1022&DEV_7801&CC_0106," from [AM-a-2] in DP_MassStorage_wnt5_x86-32.ini to [AM-8] (two sections above it)  under ms_1_hwids.  If using MS' Notepad, ensure "Word-Wrap" is off before opening the file for editing, so as not to corrupt the file.
Then use 7-zip v9.20 (7-zip settings LZMA,256,32k,512M) and call it DP_MassStorage_wnt5_x86-32_1411031.7z.  Link it here, if you would like.

Please try to confirm the fix works.  I will thank you in the changelog.

Can you make any sense out of the disparate info i have in there concerning partitioning compatibility?
I need all the help i can get to finish this long running branch of this volunteer community project.

Go to forum: DriverPack Mass Storage

94 Reply by TechDud

(12 replies, posted in Other)

Thank you for that link, compstuff.
It helped during a recent outage.

My humble respect for the pilot of SpaceShipTwo, whom died crashing into the Mojave Desert yesterday.

Go to forum: Other

95 Reply by TechDud

(2 replies, posted in Software)

Well, i might need to include that driver, which is available directly from FTDI as "CMD v2.12.00 WHQL".

FTDI wrote:

from ftdibus.inf:
"; 1.2    In this Licence a "Genuine FTDI Component" means an item of hardware that was
;        manufactured for, and sold by, the Licensor or a member of the Licensor's group of
;        companies. It does not include any counterfeit or fake products.
;
; 1.3    If you are a manufacturer of a device that includes a Genuine FTDI Component (each a
;        "Device") then you may install the Software onto that device. If you are a seller or distributor
;        of a Device then you may distribute the Software with the Device. If you are a user of a
;        Device then you may install the Software on the Device, or onto a computer system in order
;        to use the Device.
;
; 1.4    In each of those cases you may:
;
;        1.4.1    install and use the Software for your purposes only; and
;
;        1.4.2    only use the Software in conjunction with products based on and/or incorporating a
;                 Genuine FTDI Component.
;
; 1.5    The Software will not function properly on or with a component that is not a Genuine FTDI
;        Component. Use of the Software as a driver for, or installation of the Software onto,  a
;        component that is not a Genuine FTDI Component, including without limitation counterfeit
;        components, MAY IRRETRIEVABLY DAMAGE THAT COMPONENT.  It is the Licensee's
;        responsibility to make sure that all chips it installs the Software on, or uses the Software as a
;        driver for, are Genuine FTDI Components. If in doubt then contact the Licensor. 
;
; 2.    If a custom vendor ID and/or product ID or description string are used, it is the responsibility of
;        the product manufacturer to maintain any changes and subsequent WHQL re-certification as
;        a result of making these changes."

Yes, the Terms are included in the .Inf.  It is also apparently only a "soft" brick, as you can download their firmware tool & reprogram the HWID's, providing you know what it was ...

Apparently, a competing product, Prolific's PL2303 drivers simply register "Code 10" for counterfeit devices.


What do you, the reader, think?

Go to forum: Software

96 Reply by TechDud

(294 replies, posted in DriverPack Mass Storage)

Symbios24 wrote:

... "it detected the achi controller as achi886 it should be detected it as achix86" ...

That is no mistake.  If there are any executables in your ..\i386 folder named ahcix86.sy* (or iaStor.sy* for that matter), then that would be an error.

Symbios24 wrote:

"is it possible the chipset driverpack DP_Chipset_wnt5_x86-32_1405191 to have any bug since it installs another achi driver??"

DP_Chipset_wnt5_x86-32_1405191 does not contain AHCI drivers, so that cannot be installing any other AHCI driver.

Bear in mind that when you differ from proscribed (and repeatable) procedure, your results will be very difficult for us to debug.

Symbios24 wrote:

"i did another thing coz i was in a hurry, i added with nlite the v3.3.1540.33 in the same windows source, and now it detects the controlled but when the windows setup is finished there is another driver installed in the Scsi-raid controllers section in device manager ämd raid controller 13/9/2013 v6.1.2.5""

So, you replaced the driver v3.3.1540.33 with the driver v3.3.1540.33 using nLite after DPs_BASE.
  What could go wrong?     hmm

At any rate, your pack of intel drivers did give me an idea.
  That is to include the ????ahci.Inf HWID's with the RST v11.2 driver, like the "Intel(R) Pentium(R) processor N- and J-series / Intel(R) Celeron(R) processor N- and J-series AHCI - 0F23" controller on Floppy's hardware.
  Ref:  http://forum.driverpacks.net/viewtopic. … 202#p58202

  That should add upwards of a dozen HWID's for Win2k/XP/2k3, what with making room for (though not including files from) BlackWingCat's modified-core Intel MassStorage driver for Win2k.

Thank you for the serendipidous inspiration!     smile

Go to forum: DriverPack Mass Storage

97 Topic by TechDud

(2 replies, posted in Software)

Brian Benchoff wrote:

"The FTDI FT232 chip is found in thousands of electronic baubles, from Arduinos to test equipment, and more than a few bits of consumer electronics. It’s a simple chip, converting USB to a serial port, but very useful and probably one of the most cloned pieces of silicon on Earth. Thanks to a recent Windows update, all those fake FTDI chips are at risk of being bricked. This isn’t a case where fake FTDI chips won’t work if plugged into a machine running the newest FTDI driver; the latest driver bricks the fake chips, rendering them inoperable with any computer."
...
"Because the FTDI USB to UART chip is so incredibly common,  the market is flooded with clones and counterfeits. it’s very hard to tell the difference between the real and fake versions by looking at the package, but a look at the silicon reveals vast differences. The new driver for the FT232 exploits these differences, reprogramming it so it won’t work with existing drivers. It’s a bold strategy to cut down on silicon counterfeiters on the part of FTDI."

     quoted from:  http://hackaday.com/2014/10/22/watch-th … ake-chips/

Go to forum: Software

98 Reply by TechDud

(2 replies, posted in Other)

Saw my first pink sky in the morning a couple of days ago.  What is a sailor to do then, take warning of shipmates???  Could part of the color changes be due to Cesium's decay to Barium?  137Cs has a 30-year half-life, and here we are, about 30 years since Tschernobyl.

Quote:  "“A series of qualitative chemical tests and deductions now confirm without doubt the presence of significant amounts of barium within atmospheric samples…."
...
"Citizens with sufficient environmental concern are encouraged to begin this process of sample collection and identification, along with the documentation of the responses of both public and private environmental services."
http://www.carnicom.com/flame1.htm

Reasonable people don't let other people, including their Canadian neighbors, breathe or otherwise internalize uranium hexafluoride &/or hydrofluoric acid, in my humble opinion.
http://hisz.rsoe.hu/alertmap/site/index … -45778-USA
http://miningawareness.wordpress.com/20 … much-more/

Quote:  "It reports only 49 percent of the 26,025 Hanford claims have been approved under the Energy Employees Occupational Illness Compensation Program, established by Congress to support sickened nuclear workers with medical expenses and compensate them for job-related illnesses."
http://www.bizjournals.com/portland/blo … rkers.html
http://www.oregon.gov/energy/NUCSAF/doc … dwater.pdf
It is astonishing to see how much that fund has paid out thusfar.

Of course, our shared "nukular" problems are not limited to N/A.
http://www.theecologist.org/News/news_a … hreat.html

Even Cuba has abandoned one.  http://www.gizmodo.com.au/2014/10/the-a … ed-us-all/

Title:  "Why Are The US & Russia Blocking European Nuclear Safety Upgrades?" ... "to be put in place after the Fukushima Daiichi disaster"
Quote:  "Currently the US has avoided mandating any substantial safety upgrades post Fukushima"
http://www.fukuleaks.org/web/?p=13969

What has all this to do with wildfire, you might ax?  That is because counterintuitively, what falls down could eventually go up with wildfire.

Go to forum: Other

99 Reply by TechDud

(8 replies, posted in DriverPack LAN)

Quote:  "47 percent of adult Americans have had their personal information compromised in the past year. Given the Home Depot breach, as well as many others since, the number is probably even higher now."
...
"“thieves were stealing card data from Home Depot’s cash registers up until Sept. 7, 2014, a full five days after news of the breach first broke.”"

http://spectrum.ieee.org/riskfactor/com … ment-cards

Go to forum: DriverPack LAN

100 Reply by TechDud

(16 replies, posted in Software)

It would appear that others are free to use either project for their own purposes.
It might be best to obtain the packs directly from those that create them.

Where does SamLab.ws recommend obtaining his packs from for use with DP_Solution or Bad_Pointer's SDI?
Where does BadPointer recommend obtaining DriverPacks?

I prefer this project here, yet i dare not to deny the value of competing projects.

(edited to spell BadPointer's name correctly)

Go to forum: Software