Hello.

The idea has entered my mind that a separation between third-party and official driverpacks might be useful for users like me periodically checking to see if new "official" driverpacks have been released. See, nowadays there are like 20 driverpacks there, while in the good old days there were only 10 (which are listed as official in the current base).

Anybody else on the same boat? For whom the only relevant packs are the so-called official ones?

http://driverpacks.net/driverpacks/latest

2

(9 replies, posted in News)

At the very least, torrent-only downloads are fine enough with me. That way, I can donate something without spending money at it. wink

I know you guys still need some cash apart from that, though.

Great work has been done. Enjoy some time with your friends and families, now -- it has well been earned, as far as I can see.

3

(7 replies, posted in News)

Have a nice time with your own people,

New-year's goal: climbing up mountains.

4

(3 replies, posted in News)

Nice idea about the torrenting stuff. I'll try my best to seed as my own personal contribution to this project.

5

(3 replies, posted in News)

Great post. Nice read. Working project. Thumbs up!~ ;)

Great. I liked that release, as it came out just in time for my build. :)

7

(1 replies, posted in News)

BigBrit wrote:

Please don't drink and drive and die.

I had to re-read as I thought I had imagined the extra part. :)

8

(5 replies, posted in DriverPack Graphics)

I haven't tested back but yeah, that should work fine.

Great. That's good news.

Yours,
twipley

9

(5 replies, posted in DriverPack Graphics)

I have 8 minutes to kill due to an encoding.

Why not I'd plug back that old PC in the meanwhile?

-- note that the HWID-tool link from your signature looks down, at least at the moment.
Alternative link to the tool: http://driverpacks.sytes.net/driverpack … eHwids.exe

LET ME EDIT THIS POST IN JUST A MOMENT WITH THE THEN-FOUND HWIDS;

EDIT (WOW, THAT WAS QUITE FAST!):

=========== 
PCI Devices 
=========== 
PCI\VEN_10B9&DEV_5237&SUBSYS_523710B9&REV_03\3&61AAA01&0&90 : ALi PCI to USB Open Host Controller
PCI\VEN_10B9&DEV_5239&SUBSYS_88882020&REV_01\3&61AAA01&0&93 : Standard Enhanced PCI to USB Host Controller
PCI\VEN_10EC&DEV_8169&SUBSYS_816910EC&REV_10\3&61AAA01&0&80 : Realtek RTL8169/8110 Family Gigabit Ethernet NIC
PCI\VEN_1274&DEV_1371&SUBSYS_00014CA1&REV_08\3&61AAA01&0&60 : Creative AudioPCI (ES1371,ES1373) (WDM)
PCI\VEN_5333&DEV_8A22&SUBSYS_888810B0&REV_04\4&415A68E&0&0008: S3 Inc. Savage4
PCI\VEN_8086&DEV_7110&SUBSYS_00000000&REV_02\3&61AAA01&0&38 : Intel 82371AB/EB PCI to ISA bridge (ISA mode)
PCI\VEN_8086&DEV_7111&SUBSYS_00000000&REV_01\3&61AAA01&0&39 : Intel(R) 82371AB/EB PCI Bus Master IDE Controller
PCI\VEN_8086&DEV_7112&SUBSYS_00000000&REV_01\3&61AAA01&0&3A : Intel(R) 82371AB/EB PCI to USB Universal Host Controller
PCI\VEN_8086&DEV_7190&SUBSYS_00000000&REV_03\3&61AAA01&0&00 : Intel 82443BX Pentium(R) II Processor to PCI Bridge
PCI\VEN_8086&DEV_7191&SUBSYS_00000000&REV_03\3&61AAA01&0&08 : Intel 82443BX Pentium(R) II Processor to AGP Controller
10 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\ROOT_HUB\4&15736A3F&0                                   : USB Root Hub
USB\ROOT_HUB\4&20D7427B&0                                   : USB Root Hub
USB\ROOT_HUB20\4&28A33FD&0                                  : USB Root Hub
3 matching device(s) found.
 
============= 
Input Devices 
============= 
No matching devices found.
 
============ 
ACPI Devices 
============ 
ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_8\_0                 : Intel(r) Pentium(r)III processor
ACPI\PNP0000\4&2658D0A0&0                                   : Programmable interrupt controller
ACPI\PNP0100\4&2658D0A0&0                                   : System timer
ACPI\PNP0200\4&2658D0A0&0                                   : Direct memory access controller
ACPI\PNP0303\4&2658D0A0&0                                   : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0400\4&2658D0A0&0                                   : Printer Port (LPT1)
ACPI\PNP0501\1                                              : Communications Port (COM1)
ACPI\PNP0501\2                                              : Communications Port (COM2)
ACPI\PNP0700\4&2658D0A0&0                                   : Standard floppy disk controller
ACPI\PNP0800\4&2658D0A0&0                                   : System speaker
ACPI\PNP0A03\2&DABA3FF&0                                    : PCI bus
ACPI\PNP0B00\4&2658D0A0&0                                   : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0                                    : System board
ACPI\PNP0C02\1                                              : Motherboard resources
ACPI\PNP0C04\4&2658D0A0&0                                   : Numeric data processor
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI Power Button
ACPI\PNP0C0E\2&DABA3FF&0                                    : ACPI Sleep Button
ACPI\PNP0F13\4&2658D0A0&0                                   : PS/2 Compatible Mouse
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : Advanced Configuration and Power Interface (ACPI) PC
21 matching device(s) found.
 
============ 
 HDA Audio 
============ 
No matching devices found.
 
============ 
RAID Devices 
============ 
PCI\VEN_8086&DEV_7111&SUBSYS_00000000&REV_01\3&61AAA01&0&39
    Name: Intel(R) 82371AB/EB PCI Bus Master IDE Controller
    Hardware ID's:
        PCI\VEN_8086&DEV_7111&SUBSYS_00000000&REV_01
        PCI\VEN_8086&DEV_7111&SUBSYS_00000000
        PCI\VEN_8086&DEV_7111&REV_01
        PCI\VEN_8086&DEV_7111
        PCI\VEN_8086&DEV_7111&CC_010180
        PCI\VEN_8086&DEV_7111&CC_0101
    Compatible ID's:
        PCI\VEN_8086&CC_010180
        PCI\VEN_8086&CC_0101
        PCI\VEN_8086
        PCI\CC_010180
        PCI\CC_0101
1 matching device(s) found.

10

(5 replies, posted in DriverPack Graphics)

Alright. Hang on until I post back my HWIDs (might take a couple of weeks).

I am writing (adding) this to my to-do list. smile

Hello hello hello,

Device manager reported missing video-adapter driver,

had to go there: http://www.s3graphics.com/en/drivers/legacy.aspx

to download S3 Savage4 (86c395) drivers (http://drivers.s3graphics.com/en/downlo … gplogo.zip)

    Graphics Processor Properties:
      Video Adapter                                     S3 Savage4 (86c395)
      GPU Code Name                                     Savage4
      PCI Device                                        5333 / 8A22
      Process Technology                                0.25u
      Bus Type                                          AGP 4x @ 2x
      Memory Size                                       16 MB
      GPU Clock                                         110 MHz
      RAMDAC Clock                                      300 MHz
      Pixel Pipelines                                   1
      TMU Per Pipeline                                  2
      Vertex Shaders                                    Not Supported
      Pixel Shaders                                     Not Supported
      DirectX Hardware Support                          DirectX v6.0
      Pixel Fillrate                                    110 MPixel/s
      Texel Fillrate                                    220 MTexel/s

    Memory Bus Properties:
      Bus Type                                          SDR
      Bus Width                                         64-bit
      Real Clock                                        100 MHz
      Effective Clock                                   100 MHz
      Bandwidth                                         800 MB/s

    Graphics Processor Manufacturer:
      Company Name                                      S3 Graphics
      Product Information                               http://www.s3graphics.com
      Driver Download                                   http://www.s3graphics.com/drivers.jsp

Had trouble at first installing them even with the archive file downloaded (maybe because the driver was not digitally signed), however eventually succeeded by right-clicking the video-adapter icon, then choosing to reinstall driver from there (browse to inf folder using the "have disk" button).

So yeah, that was on an WinXP-x86 (SP3) system, OS installation greatly (once again) been helped by the latest driverpacks (slipstreamed using default settings).

Just for your information.

Sincerely,
twipley

12

(6 replies, posted in DriverPack Sound)

Thanks for the links. The server sound files seem to have gone astray again. Those backup links have helped me considerably.

Ok. So, in XP for example, such drivers would be stored in a driver "chest," on the HDD, and then loaded to RAM only when the flash drive (for example) gets inserted? Makes sense.

If that's true then I do not need to worry about the number of devices that get installed to my system -- drivers won't get loaded anyway until those devices get reconnected.

Strange thing Google did not help me much on that one, though.


Thanks mr_smartepants! :)

Hey, this is just a simple question about driver functioning in Windows that I thought of asking here. It has been on my mind for some time.

Each time one inserts a new device -- say, microphone, flash drive, or even wireless mouse -- in a USB port, Windows installs something for you, right? My question is, is those things that get installed remain loaded on every startup, so that, over time, say half-a-hundred different peripherals have been plugged in at least once, would it somehow get to speed down Windows a little bit? Wouldn't all those installed device drivers have to get loaded into RAM on each startup just in case previously connected USB devices get connected back in again -- so as to offer them instant functionality --?

How does that work?

twipley

EDIT: typos.

OverFlow wrote:

BASE internaly exits itself after it writes and calls this script...

This has always worked in the past, and i did not change it... perhaps it is related to updates in AutoIt.

So, have you gave it a look yet to investigate the source of the problem?

I am just curious and in no way would I want to press you in your probings. ;)

OverFlow wrote:

the worst thing of it is I can't go back and update the 8.12.5 code for everyone...

And to the v10.6 build either, assuming it too suffers from the same imperfection.

I have removed specific components from my build using nLite. That might be why clicking the "update button" on v8.12.5 BASE's updatechecker page to update to the next BASE fails to do its job properly, but I am doubting it.

Come on people, please just give it a minute and give me a hand testing!
http://downloads.driverpacks.net/applic … E_8125.exe

EDIT: smile

18

(18 replies, posted in News)

I was just gonna post this link to an interesting April Fools:

http://en.wikipedia.org/wiki/Spaghetti_tree_hoax

Or, else, does this work for anybody? smile

I've tried updating BASE through BASE v8.12.5. Upon clicking the "update selected" button, I think it's supposed to close BASE, delete it, and copy over the new BASE before firing it up. However, the temporarily batch file "inst_upd.cmd" seems to hang on this line: "del /f /q DPs_BASE.exe" -- because, the current "DPs_BASE.exe" fails to close, and a 7-zip diagnostic message displays: "ERROR: Can not delete output file C:\BASE\DPs_BASE.exe." This leaves me with an unresponsive BASE v8.12.5 that has to be closed through task manager's "end process" button.

Has anyone else suffered from the same experience on WinXP x86?

I have opened a report over at the bugtracker: http://bugtracker.driverpacks.net/view.php?id=536


Thanks,
twipley

21

(2 replies, posted in News)

You can always put the fault on a 28.8k modem of yours. wink

P.S.: those are great news. I see this as a kind of "snowball effect," where the time you people put into this creation gets me to put time in the one of my installation CD, the end effect being people at the end of the line benefiting (most of the time for free, isn't it?).

That said, great news. It cannot get any better than this.

22

(37 replies, posted in News)

Works great, thanks.

P.S.: would it be safe for me to download Sound RC? Some friends of mine have bought new machines, I've figured I could as well go on and help them installing XP, if you know what I mean... :)

Well, I heard Major was overhauling the .ini file arrangement... maybe I'll wait a little before going with those, in retrospect.


EDIT: oh, I almost forgot: great job, guys. Graphic driverpacks seem like a good deal of energy went into that. Kudos.

EDIT2: oh sorry, I just realized that Major was working on this from time to time:
http://forum.driverpacks.net/viewforum.php?id=11
/rain-man (it is raining h*ll outside) :)

23

(37 replies, posted in News)

Can't wait to get my fork ready! wink

twipley wrote:
mr_smartepants wrote:

I kinda like this idea.  Having a Third Party DriverPack to cover additional control panels for all the DriverPacks.  That would save considerable space and make it easier for admins who want a stripped OS (like we had at work)!

Exactly! Just because (as a part-time admin) space matters.

I am no longer sure making lots of efforts to save space would be such a good idea anymore, because the graphic driverpacks are now taking about 80 MBs of extra space. I think admins should thus as of current have two different disks in their possession: a CD bundled with drivers up to 2008 to use with computers lacking a DVD drive (thus being somewhat old), and a DVD bundled with up-to-date drivers for newer computers, i.e. the ones that possess a DVD drive and might contain recent hardware.

That being said, good job with the driverpacks, they are becoming really strong now. Long live XP!

cheche wrote:

Unable to download from the site. Seems down.

Works now. smile