@OverFlow -Am thinking that is the only reasonable use of IE8 in an NT5 context might be for Windows Update, though that has me thinking that there should be via paid support on DriverPacks as most valid licensees are corporate consumers.

@Outbreaker - please let 5eraph in on this.  It would be cool if he could use whatever he likes.  I look forward to eventually joining that community, but not at this time.  We need some good members of both communities to help weave a greater community.

  I'd love to know what assorted driver/hardware-specific KB updates karkaz has left on his "cutting-room floor", for instance.

I look forward to conversing about testing and verifying network security configurations.

Check the first post in this topic, if you like.
Is there something new there?

I'm on a "need-to-know" basis here, btw.  :lol
_   _   _   _   _   _   _   _   _   _   _   _   _   _   _   _   _   _   _   _   _   _   
I've had no trouble whatsoever with the 9.20.0.2 revision of 7-zip32.dll specifically, even on older machines down to about !GHz-512MB.  Below that, certainly she be slow ... now even s l  o    w     e      r       .        .          .

It's rock solid stable though.  That is what one should be able to expect from any "Release" anyway, eh?

This revision of 9.20.0.2 has multi-core support, iirc, and supports LZMA2, amongst many other bugfixes & improvements.  It was a worthy successor of the 4.65 revision that was in there, iirc.

The packs i post are simply LZMA compressed for widest compatibility, btw.
That doesn't stop anybody from recompressing their own packs to LZMA2, if they have DPs_BASE v1109012b.

I should add that to docs...

harkaz wrote:

"@GH0st Thanks for the new security enhacements you posted I will add a note at the first page and add this as an optional download."
     http://www.ryanvm.net/forum/viewtopic.p … 614#138614

harkaz has noted them on his front page.  http://www.ryanvm.net/forum/viewtopic.php?t=10321
  What i should do is to add a link to his Unofficial SP4 Project in the Changelog-Notes.
That one i will remove for certain.  Also, there are no "undo" reg files.  That cannot be good.


Outbreaker wrote:

... "this should not be forced unto users" ...

  I agree, and that is why those reg files are zipped and optional.  Note that undo files are included.

Outbreaker wrote:

... "the second one is also already included in most of the UpdatePacks" ...

  Reference:  http://www.ryanvm.net/forum/viewtopic.p … 414#138414
I don't see it in user_hidden's update packs, nor OnePiece's or even harkaz's Unofficial XP-SP4.

Note that 5eraph's specific SA3009008 solution appears incomplete at best, and perhaps even erroneous.
Look at the last two lines of that post, where TLS 1.0 is "enabled" with a 0x01.  That is apparently incorrect.

Microsoft wrote:

"To allow this cipher algorithm, change the DWORD value data of the Enabled value to 0xffffffff. Or, change the DWORD data to 0x0. If you do not configure the Enabled value, the default is enabled."
     http://support.microsoft.com/kb/245030   see also:  http://support.microsoft.com/kb/187498 & http://support.microsoft.com/kb/811833

Is this not also true for protocols?

Hermann Wolf wrote:

"I also added the key SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\DES 56/56 with Enabled=1 and rebooted again bit the SSLScan.exe output is always the same"
     http://forums.iis.net/t/1187790.aspx

What of the value ""DisabledByDefault"=dword:00000001"?  I don't know which takes precedence.  RC4 128/128 disabling/undo should be included.  Win2k & 2k3 solutions are also missing thusfar.  Can AES work on XP?

  It does highlight the dire need for confirmation via testing.
There is a program that will test supported ciphers (except TLS 1.1 & 1.2).
  http://code.google.com/p/sslscan-win/
Here is some sample output, thanks to Wayne Zimmerman --> http://www.waynezim.com/2011/03/how-to- … rs-in-iis/

  Are there any UpdatePacks that include the full set of solutions?  I haven't seen any so far.  Correct me if i am wrong, please.

Outbreaker wrote:

... "people won't be able to connect to outdated HTTPS servers."

That is apparently actively being encouraged for servers.

Robert Love wrote:

"I advocate disabling SSLv3 support, which breaks Internet Explorer 6 on Windows XP, but prevents a downgrade attack for everyone else. If we're willing to drop support for all versions of Internet Explorer on Windows XP (Which likely just means the addition of IE 7 and 8), we can accomplish two other goals:
     http://blog.rlove.org/2014/04/the-end-o … p-and.html

  Also see:  http://blog.rlove.org/2013/12/strong-ssl-crypto.html


It's a bit of a sticky wicket, and it seems better to include it here as optional, as nobody other than 5eraph seems to have included any solution for NT5.
  I like to be able to confirm that the NULL cipher cannot be used with TLS 1.0 for instance, in my humble opinion.
  SSLScan seems to make that verification a little easier too.

symc8xx [C] ms_1
- need special case for a single driver that replaces two or more native drivers...
- Fixed, simply assign no HWIDs to one or more (ms_X) section(s)
- combined old ms_2 and ms_3 into ms_1
symc810 [C] ms_2
- see above. replaced.
sym_hi  [C] ms_3
- ms_2 is also replaced
-- see section for example!

See Quote:  "DriverPacks BASE 10.02.19
[BUG] Fix - RE: Index » BartPE - UBCD4Win - WinPE » ="sym_hi" DP_MassStorage_wnt5_x86-32_100125.7z"
http://forum.driverpacks.net/viewtopic. … 199#p36199

Here is the section from the latest Release (DP_MassStorage_wnt5_x86-32_1209):

[C]
ms_count=8
ms_1_deviceName="Compaq HP ProLiant SCSI"
ms_1_tag="symc8xx"
ms_1_sysFile="CPQ32FS2.sys"
ms_1_hwids="PCI\VEN_1000&DEV_0002,PCI\VEN_1000&DEV_0003,PCI\VEN_1000&DEV_0004,PCI\VEN_1000&DEV_0005,PCI\VEN_1000&DEV_0006,PCI\VEN_1000&DEV_000C,PCI\VEN_1000&DEV_000D,PCI\VEN_1000&DEV_000F"
ms_1_isBusExtender=false
ms_1_exc_replaceIfOS="w2k,wxp,w2k3"
;ms_1_exc_disableIfOS="w2k"

ms_2_deviceName="LSI Logic C8100 PCI SCSI Host Adapter"
ms_2_tag="symc810"
ms_2_sysFile="CPQ32FS2.sys"
ms_2_hwids="PCI\VEN_1000&DEV_0001"
ms_2_isBusExtender=false
ms_2_exc_replaceIfOS="w2k,wxp,w2k3"
;ms_2_exc_disableIfOS="w2k"

ms_3_deviceName="LSI Logic C896 PCI SCSI Host Adapter"
ms_3_tag="sym_hi"
ms_3_sysFile="CPQ32FS2.sys"
ms_3_hwids="PCI\VEN_1000&DEV_0012,PCI\VEN_1000&DEV_000a,PCI\VEN_1000&DEV_000b,PCI\VEN_1000&DEV_0012&SUBSYS_001b0e11,PCI\VEN_1000&DEV_000b&SUBSYS_60040e11"
ms_3_isBusExtender=false
ms_3_exc_replaceIfOS="w2k,wxp,w2k3"
;ms_3_exc_disableIfOS="w2k"

Here is what was in a post-7sisters update (DP_MassStorage_wnt5_x86-32_1412115):

[C]
; start of Compaq section
ms_count=9
ms_1_deviceName="Compaq HP ProLiant SCSI"
ms_1_tag="symc8xx"
ms_1_sysFile="CPQ32FS2.sys"
ms_1_hwids="PCI\VEN_1000&DEV_0002,PCI\VEN_1000&DEV_0003,PCI\VEN_1000&DEV_0004,PCI\VEN_1000&DEV_0005,PCI\VEN_1000&DEV_0006,PCI\VEN_1000&DEV_000C,PCI\VEN_1000&DEV_000D,PCI\VEN_1000&DEV_000F"
ms_1_isBusExtender=false
ms_1_exc_replaceIfOS="wxp,w2k3"
ms_1_exc_skipIfOS="w2k"
; original #6 of "7 sisters - 2k" issue
;   included driver missing 2k/xp/2k3 OS HWIDs: PCI\VEN_1000&DEV_0002, PCI\VEN_1000&DEV_0004, PCI\VEN_1000&DEV_0005, PCI\VEN_1000&DEV_0006, PCI\VEN_1000&DEV_000D
;     OS scsi.inf/pnpscsi.inf will handle installation for those
;     w2k should update 1000:0003, 1000:000C, 1000:000F @ T36 as CPQ32F32 is Win2k(min) WHQL

ms_2_deviceName="LSI Logic C8100 PCI SCSI Host Adapter"
ms_2_tag="symc810"
ms_2_sysFile="CPQ32FS2.sys"
ms_2_hwids="PCI\VEN_1000&DEV_0001"
ms_2_isBusExtender=false
ms_2_exc_replaceIfOS="wxp,w2k3"
ms_2_exc_skipIfOS="w2k"
; original #5 of "7 sisters - 2k" issue
;     w2k should update @ T36 as CPQ32F32 is Win2k(min) WHQL

ms_3_deviceName="LSI Logic C896 PCI SCSI Host Adapter"
ms_3_tag="sym_hi"
ms_3_sysFile="CPQ32FS2.sys"
ms_3_hwids="PCI\VEN_1000&DEV_0012,PCI\VEN_1000&DEV_000a,PCI\VEN_1000&DEV_000b,PCI\VEN_1000&DEV_0012&SUBSYS_001b0e11,PCI\VEN_1000&DEV_000b&SUBSYS_60040e11"
ms_3_isBusExtender=false
ms_3_exc_replaceIfOS="wxp,w2k3"
ms_3_exc_skipIfOS="w2k"
; original #4(part1/2) of "7 sisters - 2k" issue
;   included driver missing xp/2k3 OS HWIDs: PCI\VEN_1000&DEV_0012&SUBSYS_001b0e11,PCI\VEN_1000&DEV_000b&SUBSYS_60040e11
;     OS pnpscsi.inf will handle installation for those

...

ms_9_deviceName="LSI Logic C896 PCI SCSI Host Adapter (W2k)"
ms_9_tag="CPQ32FS2"
ms_9_sysFile="CPQ32FS2.sys"
ms_9_hwids="PCI\VEN_1000&DEV_0012,PCI\VEN_1000&DEV_000a"
ms_9_isBusExtender=false
ms_9_exc_skipIfOS="wxp,w2k3"
; original #4(part2/2) of "7 sisters - 2k" issue
;   w2k includes only PCI\VEN_1000&DEV_000b
;     should update @ T36 as CPQ32F32 is Win2k(min) WHQL

I went a different way with that section in DP_MassStorage_wnt5_x86-32_1501041.

[C]
; start of Compaq section
ms_count=7
ms_1_deviceName="Compaq HP ProLiant SCSI"
ms_1_tag="symc8xx"
ms_1_sysFile="CPQ32FS2.sys"
ms_1_hwids="PCI\VEN_1000&DEV_0002,PCI\VEN_1000&DEV_0004,PCI\VEN_1000&DEV_0005,PCI\VEN_1000&DEV_0006,PCI\VEN_1000&DEV_000D"
ms_1_isBusExtender=false
ms_1_exc_replaceIfOS="wxp,w2k3"
ms_1_exc_skipIfOS="w2k"
; original #6 of "7 sisters - 2k" issue
;   included driver missing 2k/xp/2k3 OS HWIDs: PCI\VEN_1000&DEV_0002, PCI\VEN_1000&DEV_0004, PCI\VEN_1000&DEV_0005, PCI\VEN_1000&DEV_0006, PCI\VEN_1000&DEV_000D
;     xp-2k3 OS scsi.inf/pnpscsi.inf will handle installation for those

ms_2_deviceName="Compaq HP ProLiant/LSI/Symbios Logic SCSI"
ms_2_tag="CPQ32FS2"
ms_2_sysFile="CPQ32FS2.sys"
ms_2_hwids="PCI\VEN_1000&DEV_0001,PCI\VEN_1000&DEV_0003,PCI\VEN_1000&DEV_000a,PCI\VEN_1000&DEV_000b,PCI\VEN_1000&DEV_000C,PCI\VEN_1000&DEV_000F,PCI\VEN_1000&DEV_0012,PCI\VEN_1000&DEV_0012&SUBSYS_001b0e11,PCI\VEN_1000&DEV_000b&SUBSYS_60040e11,NCRC710_SCSI,CPQFWS2E_SCSI"
ms_2_isBusExtender=false
; orphans symc810.sys & sym_hi.sys on original install media
;   manual reference removal in dosnet.inf & txtsetup.sif, or RVMi/nLite plugin needed to remove

As the CPQ32FS2.* driver is WHQL, those HWIDs can be directly serviced by that driver (i need to confirm WHQL for W2k).

Win2k is funny in that it apparently replaces those updated files (sym_hi, symc810 & symc8xx) at some point with even older files that exist in DRIVER.CAB (need to confirm, again for sanity's sake).
  Server2k3 is the only NT5 OS that only includes symc810.sys in DRIVER.CAB, not all three files.
    Driver.cab isn't mentioned at all in that topic you linked to above, OverFlow.

From XP-sp3 dosnet.inf (post-DriverPacks-BASE integration):
   reference:  https://support.microsoft.com/kb/814847/en-us

[ForceCopyDriverCabFiles]
viaide.sys
ql12160.sys
ultra.sys
mraid35x.sys
dac960nt.sys
dac2w2k.sys
perc2.sys
symc8xx.sys
adpu160m.sys
DPTI2O.sys

I have no [ForceCopyDriverCabFiles] section in any of my Win2k dosnet.inf files, including the UR1 integrations.
    Is that one reason why i have previously noted the "7-sisters" issue?
  Is that also at least one reason why none of the "replaced" drivers in XP-2k3 get similarly rolled back?

These modifications, among others, prevent the "7-sisters" issue of all those files apparently rolled-back and noted in SetupErr.log on Windows 2000 (image integrated with UR1).  Some HWIDs (those in first section) remain as original in Win2k though.  Skipping the symc8xx driver did not remove any files using the latest DPs_BASE.

I wonder what could happen to those with those HWID's listed above (1000:0002, 1000:0004, 1000:0005, 1000:0006, 1000:000D) should they run sfc.exe /scannow on Win2k with DP_MS Release, as that usage as symc8xx.sys is not WHQL, nor is the file in question signed.
  Could Windows attempt to replace sym*.sys with older versions existing in Driver.Cab?

I think it possible that i have made some incorrect assumptions, perhaps even noted some things others have missed previously.  Please correct me where i err that we can finally move to RC's, and we can respectfully prove GH0st ultimately wrong about XP DriverPacks.
-------------------------------------------------------------------------------------------------------------------------
I see that Outbreaker did attempt to warn us about Virtual SATA mode in VB/VMW way back then too!

OverFlow wrote:

"if you can wrap your head around mass storage then all the other packs will seem simple."

You haven't seen the DAAMiT Graphics drivers then!  (AMD/ATi)  Yikes!
  I need to back 'er up to have enough room to get up to 80 miles an hour to promptly wrap my head around those packs, so that even the Jaws-Of-Life cannot Skip, Replace, or Disable them!   :lol

PS:  I get the following effect when switching to a renamed folder for integration.
       http://forum.driverpacks.net/viewtopic. … 204#p36204

Imported all USB device drivers (not USB controller drivers) from DP_Chipset_wnt5_x86-32.  smile

Braille Reader support is now via DP_Misc_USB & DP_Misc-Utils.

for 3rd party DriverPacks folder (or side-by side for SAD3 installation):
·DP_Misc_wnt5_x86-32_1501011.7z - 16.07 MB   6ACA7E648DC14B59F5FECAC6FCA9535C99D2D114
·DP_Misc-Utils_wnt5_x86-32_1412311.7z - 84.52 MB   18D255076827CC7AB418655F7035719B7C059C1D

for post-Windows Setup utilizing SAD3:
·DP_Misc_USB_wnt5_x86-32_1501011.7z - 8.63 MB   ACF86D722357042A0D8A6A60DDC02B4EF5E6D923

Harden_XP_TCPIP_Stack_by_GH0st.reg has been included.

GH0st wrote:

"Here are some security tweaks I include with every install I do. I have had great success with them! Posting them for you all to consider."
   ... "1) This is a GREAT tool, highly recommended: Seconfig XP" [https://seconfig.sytes.net/?sv=1.1] ". Select the "For home" option, then "Apply", reboot!
        2) Been using this for years, nice security tool Windows Worms Doors Cleaner 1.4.1" [http://go4softwares.com/2013/02/02/wind … ner-1-4-1/] " Select options, reboot!
        3) Then add the following manually in to your registry. Some may already be present."
     quoted from:  http://www.ryanvm.net/forum/viewtopic.p … 92e#138610

You might also like the KB Schannel reg mods included as XP_KB3009008_Schannel_Registry_Mods_by_TechDud.zip
   reference:   KB245030 & KB3009008 http://support.microsoft.com/kb/245030
                          FixIt! available for IE:  http://support.microsoft.com/kb/3009008

·DP_LAN_wnt5_x86-32_1412311.7z - 12.26 MB   B4B7831B8D7E6B7483161D9229F787671FEC6DC3

Harden_XP_TCPIP_Stack_by_GH0st.reg has been included.

5eraph, and others might also like the KB Schannel reg mods included as XP_KB3009008_Schannel_Registry_Mods_by_TechDud.zip
   reference:   KB245030 & KB3009008 http://support.microsoft.com/kb/245030
                          FixIt! available for IE:  http://support.microsoft.com/kb/3009008

"For the Schannel.dll file to recognize any changes under the SCHANNEL registry key, you must restart the computer."
     quoted from:  http://support.microsoft.com/kb/245030


·DP_WLAN_wnt5_x86-32_1412311.7z - 21.84 MB   272D691A598CC887E6994D46628810833C37E6A5

USB device drivers (not USB controller drivers) have been exported to the new DP_Misc_USB_wnt5_x86-32 pack.

·DP_Chipset_wnt5_x86-32_1412311.7z - 4.43 MB   A3BA219E3B5D91FF21C9591BA6A0826574ADC76B


Noting that W2kSP4-UR1_HTT-DualCoreCPU.reg dropped my P4-HT power consumption at idle by about 40Watts.
  That is, from about 110W to about 70W.     big_smile
    I didn't even have UR1 (KB891861 v2) integrated!  It was a plain-Jane Win2k-SP4 disc.

Welcome back!  smile

Hello and welcome to the forum!  smile

I have two OEM folders too!
  It works well for me, though i don't use nLite.

Start with your original XP-SP3 disc and make a new integration.
  Something done during creation of your image may have broken your installations.

If you need more assistance, please start a new topic.

·DP_Graphics_ATi-Legacy_wnt5_x86-32_1501041.7z - 118.75 MB   52840D7E53D157261A8B010D5391769133B8A361

Include ATi Runtimes pack for Catalyst Control Panel installation.  ATi Hydravision pack is also optional.

If Graphics_A/B/C are not integrated,  ATICCC.ins may need be manually added to ..\OEM folder.
     If SAD3 is used for installation, add ATICCC.ins to root folder {example:  C:\}.

Actually, the driver you linked from the lenovo site (CX_90748.inf) is slightly newer than what exists in the Legacy pack (CX_89427.inf).  They are both dated the same and share the same version in the .inf files.
The folder both drivers draw from is the same, so one might expect some differences in what is set in the registry.

Wow, that added a whopping 0.04 MB to the compressed pack size!   :lol

Will post update on DP_Graphics_wnt5_x86-32 forum topic.

If you are using the legacy pack on it's own or are using SAD3 for installation, there are some important considerations relating to the ATICCC.ins file.


PS:  That latest Power Manager Driver (for Vista and up) is WHQL'ed for XP and up.  Have not yet tested, though it's on my list.

How well does openGL work with that updated generic driver?

see #6 (verify function)  http://forum.driverpacks.net/viewtopic.php?id=7041
& check directx 7,8 & 9 via dxdiag.

Note the "*please delete*" topics on WinCert by BrokenZer0.

Some lead to --> http://www.wincert.net/forum/topic/1258 … -oct-2014/
see also:  http://www.wincert.net/forum/topic/1251 … ntry110645

BrokenZer0 wrote:

"Methode Install (HowTo):

1. Download and extract this useful tool: http://www.mediafire.com/download/resi1 … -130825.7z
2. Create folder D in NT6\x64 and extract the content of the DriverPack to the NT6\x64\D\ folder so that the folder heirarchy looks like this: \NT6\x64\D\*.
3. Start DP_Install_Tool.cmd and follow instructions.


I do wish he would credit that tool's creator, whom is mr_smartepants.


It does appear he has made some good progress towards updated Win8.1 driverpacks.
http://www.wincert.net/forum/topic/1257 … ta-thread/

IF (it's only rhetorical, i won't be borrowing his work - OEM download only), and only IF i were to borrow BZ's work, i would at least credit him.

That is a strange effect.

I cannot download.  Filedropper takes me to it's homepage.
  Does it require the use of Adobe Flash instead of HTML5?

Thank you Symbios24!

Will add that driver referenced above, cheche, including the w2k driver.

[OT]  Will also test updated "vista" power management driver(s) on an ole IBM ThinkPad R40.  That will have to wait upon a thurough & successful teardown, cleaning & rebuild.  Preliminarily, the file structure looks the same.[/OT]

Will check versus last Release to be certain.
  "7 sisters" comes to mind as possible time-frame for change (for Win2k though).

Changes have been made to AMD/ATi MassStorage sections here.
  Will re-test, yet so-far VEN_1022&DEV_4391 works flawlessly on an HP g62.
Perhaps Symbios24 meant to say VEN_1022&DEV_7801, in which case i have broken signing on the rcraid driver to avoid it's installation at or about T35.

Also, thanks to Outbreaker, references for those RAID management devices will be removed, as they are meant to use a null-driver.

Will also add support for BlackWingCat's modified driver for his modified Win2k kernel.  As the system files have been modified, i can include support for the files, but not the files themselves.  (Some Assembly Required - though no "machine language"  :lol)

Towards that end, the SB6xx & SB7xx drivers are further limited to XP minimum via the .Inf files to enforce OS support.

Oops, i think you might have accidentally reported yourself.  tongue
  We are all human, and make mistakes from time-to-time.

Delete the HWID's listed in the DP_MassStorage_wnt5_x86-32_1412115.7z section [AM-7] as follows:

,PCI\VEN_1002&DEV_4391,PCI\VEN_1002&DEV_4392,PCI\VEN_1002&DEV_4393

Set "ms_count=1" for that section, then delete the following:

ms_2_deviceName="AMD AHCI Compatible RAID SB7xx"
ms_2_tag="ahcix70r"
ms_2_sysFile="ahcix86.sys"
ms_2_hwids="SCSI\ProcessorAMD_____"
ms_2_isBusExtender=false
ms_2_exc_skipIfOS="w2k"

As Outbreaker previously noted, SCSI\ProcessorAMD_____ should be using a null-driver, as noted in the corresponding .Inf file.

edit:  Also modify the MassStorage.ini to reflect when it was edited.  For instance:

; version 1412291

Since you are experiencing STOP &H7B errata about T36, edit the ..\D\M\AM\7\ahcix86.inf file.
  Comment-out the following lines, like so:

;CatalogFile=ahcix86.cat

...

;%NapaDesc%=Napa_Inst,PCI\VEN_1002&DEV_4392
;%NapaDesc%=Napa_Inst,PCI\VEN_1002&DEV_4391
;%NapaDesc%=Napa_Inst,PCI\VEN_1002&DEV_4393

Note that those aforementioned sections are almost verbatim that of the official release.
  This is not to "blame" them that worked on this pack previously,
but to celebrate them and the fact that it took well over two years to uncover problems!

Please post your resulting pack, and test it with an unmodified XP-SP3 media (no updates, no apps, etc) integration using DPs_BASE with DP_MassStorage, DP_LAN & DP_Chipset only.  Please retain your DPs_BASE log, and post it in code tags if there are still problems.  Also, keep a copy for yourself of DPs_FnShR.log from the machine being tested (only if it actually achieves the Desktop sucessfully).

Check RAID by setting up a single drive, if only one drive is available, as JBOD if possible.

If it does work correctly, keep the image for later testing.  Then move on to creating your "final" image with updates, etc.  DPs_BASE integration is to be the last step.  Note that DPs_BASE is not meant to attempt to update integration of DP_MassStorage, as we had previously discussed.

I hope it works for you, because then it should work for everyone else too.  smile

Also, through this process you may become aware of what exactly caused you characters to not be Greek.
For "Press any key to start from CD" to appear in another language, i so far fail to understand how DriverPacks(TM) could possibly cause that.


Also, I thank you for your continued contributions.  I look forward to learning more from you!

  "Efharisto"  smile - http://www.cretetravel.com/travel_tips/ … -in-greek/

If you want the latest runtimes, they are available from Ricktendo, to whom i am very grateful.

http://www.wincert.net/forum/topic/9790 … le-x86x64/
http://www.wincert.net/forum/topic/1229 … 12-3-2014/
http://www.wincert.net/forum/topic/9154 … 1-25-2014/

¡Muy bien, señor Ricktendo!

"i confirm that the driverpack DP_MassStorage_wnt5_x86-32_1412115.7z it causing the problem after integrating the older driverpack DP_MassStorage_wnt5_x86-32_1411031.7z"

Am wondering what procedure you used to do that.

Have checked differences between the two packs you noted above, and for the AMD sections, there are few differences.  One difference was that a couple of drivers were "disabled" for win2k.  Another difference was in the names "sb8xx/sb9xx".
By textmode updates, note that harkaz included some updates for textmode which might have been english customizations.  Those seem much more likely to cause the issues you have noted in this topic.  You have integrated his Unofficial XP-SP4, have you not?

What HWID was this for?

My thoughts, hopes, and prayers are for the people still on the ferry off the coast of Corfu, as well as those on the as-of-yet missing Malay air liner.

Then i was wrong.  That is good that i am wrong about that.  smile

Perhaps harkaz hadn't included multilanguage support for his textmode updates included in the unofficial XP-SP4 project.
Is he still on holidays?

If and when you post a question at ryanvm forums, please remind them of this project.  I would very much appreciate that.
  Maybe they will like the DP_Virtual_wnt5_x86-32 pack we have been working on this past month.

When you do find out what exactly caused the problem, please share the solution there.

That sounds very much like failing graphics hardware.
  Check with Misha Cherkes' Video Memory Stress Test, linked in my signature &/or the Windows version, available at his home page.
http://mikelab.kiev.ua/index_en.php?pag … AMS/vmt_en

A CUDA Video Memory test for linux is available here --> http://sourceforge.net/projects/cudagpumemtest/

Fanless designs probably shouldn't be used to drive two monitors.
Overheating is a probable cause too, sadly.

Also see http://forum.driverpacks.net/viewtopic.php?id=6750

·UKD_14-20_Beta_Updated_Dec_24_2014.zip - 1.14 MB   91B7112C197DE00C40489BE2FA479FEA1C1F3068

for 3rd party DriverPacks folder (or side-by side for SAD3 installation):
·DP_Bluetooth_MS-Misc_wnt5_x86-32_1412221.7z - 14.99 MB   14FB5822D5943800C1772F9D5A6BFFA613B28771

for DriverPacks folder:
·DP_Graphics_B_wnt5_x86-32_1412261.7z - 217.61 MB   DE6556BC47DBE09153DD127C5B6972AF5EA73530

for 3rd party DriverPacks folder (or side-by side for SAD3 installation):
·DP_Graphics_D_wnt5_x86-32_1412071.7z - 144.63 MB   7D6EBD011758984D24C2E3BE36206F6ADD7FC4DC
·DP_Graphics_Languages_wnt5_x86-32_1412251.7z - 78.58 MB   A777716E3F08B140340883C10192128B253F6589
·DP_Graphics_nVidia_GFxp-upd_wnt5_x86-32_1412261.7z - 25.91 MB   6870685C48D57BF5D5F3E4184495E8D0EAC8BDE2
·DP_Graphics_nVidia_Runtimes_wnt5_x86-32_1412261.7z - 106.82 MB   90AD1A17EECDF3861EB94EB10C76CDA1E14123C6
·DP_Graphics_PhysX_wnt5_x86-32_1412251.7z - 56.44 MB   1405B339EC90637A9069D8542AEB2035EEC1B8CC