Does that happen no matter what kind of video adapter or other hardware is in the computer? Knowing what's in there might point to a culprit.
176 2006-06-09 23:51:08
Re: [SOLVED] Windows 2000 Setup Stalls (with Graphics DriverPack A or B) (11 replies, posted in DriverPack Graphics)
177 2006-06-09 03:34:09
Topic: [IMPLEMENTED] Additional Yamaha DS-XG hwid (1 replies, posted in DriverPack Sound)
Request for inclusion in DriverPack Sound B
hwids:
PCI\VEN_1073&DEV_0012&SUBSYS_00011179&REV_00\3&61AAA01&0&60 : YAMAHA Native DS1 WDM Driver
PCI\VEN_115D&DEV_00D4&SUBSYS_24118086&REV_00\3&61AAA01&0&41 : Xircom MPCI Modem 56
PCI\VEN_1179&DEV_0617&SUBSYS_00011179&REV_20\3&61AAA01&0&58 : Toshiba ToPIC100 CardBus Controller
PCI\VEN_1179&DEV_0617&SUBSYS_00011179&REV_20\3&61AAA01&0&59 : Toshiba ToPIC100 CardBus Controller
PCI\VEN_5333&DEV_8C12&SUBSYS_00011179&REV_13\4&415A68E&0&0008: S3 Graphics Savage/IX
PCI\VEN_8086&DEV_1229&SUBSYS_24118086&REV_09\3&61AAA01&0&40 : Intel(R) PRO/100+ MiniPCI
PCI\VEN_8086&DEV_7110&SUBSYS_00000000&REV_02\3&61AAA01&0&28 : Intel 82371AB/EB PCI to ISA bridge (EIO mode)
PCI\VEN_8086&DEV_7111&SUBSYS_00000000&REV_01\3&61AAA01&0&29 : Intel(R) 82371AB/EB PCI Bus Master IDE Controller
PCI\VEN_8086&DEV_7112&SUBSYS_00000000&REV_01\3&61AAA01&0&2A : 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
11 matching device(s) found.
178 2006-06-09 03:24:55
Topic: [IMPLEMENTED] S3 Savage IX/MX (2 replies, posted in DriverPack Graphics)
179 2006-06-06 13:01:40
Re: OPEN: Automatic download function for new/updated driverpacks (28 replies, posted in Feature Requests)
I guess point is that if you are only making an install source for yourself and maybe a family member or two, then all of these utilities are probably overkill. However, if you're using these things as a part of your job, and it makes your job easier, and it makes you look good to your boss/clients, then a small donation isn't too much to ask - even if you do help with the bug hunting.
Believe me, I'm all about open source and freeware, but at some point you wouldn't mind at least recouping the cost of hosting. Anything extra probably goes toward a faster unit in order to be more productive in development (faster test installs in VMware, etc).
I just don't see any reason to be bringing the issue up at all. Bashrat pretty much single handedly brought the DriverPacks to life. Even more, he made it possible to easily assemble your own DriverPacks and use his tools to integrate them without needing to know hardly anything. It's an insanely time consuming project considering how fluid the hardware market is and the ever changing drivers.
180 2006-06-06 11:58:57
Re: OPEN: Automatic download function for new/updated driverpacks (28 replies, posted in Feature Requests)
I'm just wondering how you can sit there and consider the practice that brought us to these forums anyway? I thought we all had a hand in building up these very helpful programs. You CAN'T take drivers made by manufactures and charge ppl for them by the way...
Most of us have had a hand at assisting in debugging and in testing, but when is the last time you contributed any code to the BASE slipstreamer? My guess would be that "pro" members will have access to a "pro" version of the slipstreamer. Obviously nobody can charge you to download device drivers developed by myraid of companies.
ppl should remember why they develop these programs in the first place (or are they just wasting their time?). In either case, I don't feel confortable reading this crap on a forum. I'd rather call your customer service department when I buy your product off the shelf.
You should remember that those of us who provide our projects to others but solicit donations really do this as a labor of love. None of us are so misguided as to believe we are going to get rich from our endeavors. Anybody who has been around MSFN for while probably knows that I do not suffer fools well, so in conclusion, I'm not too comfortable read this "crap" either.
181 2006-06-06 05:23:53
Re: NTC Monitor (3 replies, posted in Hardware)
Generally speaking, monitor drivers are nothing more than a definition of the refresh rates, capabilities, etc and optionally, a color profile. I've been getting a pretty good deal lately on Acer 17" LCDs and they have no drivers of any kind. At first this threw me off because I was pretty used to loading up the drivers for the Samsung and Benq flat panels we had been getting.
182 2006-06-06 04:23:44
Re: SOLVED BUG #69: "Files without extension crash" (8 replies, posted in Feedback and Support - DriverPacks Base)
@Bâshrat the Sneaky, I don't know if this is useful information to you or not, but I believe the DP Modem contains files that appear as though they're cabbed (ex: ending in .dl_), but it is not cab compression. I'm guessing it's an InstallShield cab or something like that.
183 2006-06-05 08:16:26
Re: SOLVED: Virus in cmdow.exe?! (11 replies, posted in Feedback and Support - DriverPacks Base)
It used to be that you could actually trust, with a fair amount of confidence, the reporting from AV software. I'm finding that they all seem to be taking pretty broad liberties on what is considered an "infection" lately.
I use DameWare NT Utilities all the time for some pretty basic network management chores. Among other things that it can do is remote control in to a workstation, much like pcAnywhere. It's way easier to manage and use than either Remote Assistance or pcAnywhere however. Anyway, just about every single AV and antispyware title out there flags the thing with their highest severity rating. It's been a professional net admin product for years on end now (hence the title "NT Utilities"). Makes things a PITA.
184 2006-06-04 15:21:07
Re: Mass Storage and USB Card Readers = No Joy (11 replies, posted in DriverPack Mass Storage)
I've never run into this problem myself and off the top of my head I can think of four different computers I've done installs on recently that use USB multicard readers and none of them have had issues. I do integrate DP mass storage into the install source, however none of those computer has a need for DP mass storage as their controllers are supported by XP natively. I don't know if that's the difference or not.
185 2006-06-04 09:12:18
Re: OPEN: verify DriverPacks' integrity (6 replies, posted in Feature Requests)
7-Zip has had problems in the past with it's "Test Archive" function. Comparing MD5's would be much more reliable.
186 2006-06-04 09:10:35
Topic: SOLVED BUG #65: Could not extract bin\finish.7z to \$OEM$\$1 (0 replies, posted in Feedback and Support - DriverPacks Base)
I received this error today and when I went to inspect the $OEM$ directory there was a file named $1, which obviously is not a directory.
[General]
wizardButtons=no
GUI=yes
[Settings]
type=disc
location=C:\AITmp
DriverPacks=select
DPsMethod=1
finishMethod=custom
[OptionalSettings]
KTD=none
QSC=no
[SelectDriverPacks]
DP_Chipset=no
DP_CPU=no
DP_Graphics_A=no
DP_Graphics_B=no
DP_Graphics_C=no
DP_LAN=no
DP_MassStorage=no
DP_Sound_A=no
DP_Sound_B=no
DP_WLAN=no
DPs_3rd_party=no
DP_MassStorage_textmode=yes
2006-06-03 17:17:59 : <INIT> DriverPacks BASE 6.06 initialized in API mode by AutoRIS.
2006-06-03 17:18:07 : <INIT> Detected settings file.
2006-06-03 17:18:07 : <INIT> Imported settings from settings file.
2006-06-03 17:18:07 : <INIT> Detected Windows XP Professional SP2 in C:\AITmp.
2006-06-03 17:18:07 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (CCC) was set.
2006-06-03 17:18:07 : <INIT> Detected DriverPack Chipset 6.05!
2006-06-03 17:18:07 : <INIT> Detected DriverPack CPU 6.05!
2006-06-03 17:18:07 : <INIT> Detected DriverPack Graphics A 6.06!
2006-06-03 17:18:07 : <INIT> Detected DriverPack Graphics B 6.03!
2006-06-03 17:18:07 : <INIT> Detected DriverPack Graphics C 6.03!
2006-06-03 17:18:07 : <INIT> Detected DriverPack LAN 6.05.1!
2006-06-03 17:18:07 : <INIT> Detected DriverPack MassStorage 6.03.1!
2006-06-03 17:18:07 : <INIT> Detected DriverPack Sound A 6.06!
2006-06-03 17:18:07 : <INIT> Detected DriverPack Sound B 6.03!
2006-06-03 17:18:07 : <INIT> Detected DriverPack WLAN 6.05!
2006-06-03 17:18:07 : <INIT> Detected 3rd party DriverPack(s).
2006-06-03 17:18:07 : <INIT> DriverPacks scanned sucessfully.
2006-06-03 17:18:07 : <INIT> QuickStream Cache directory not found!
2006-06-03 17:18:07 : <SEL> Selected module: mod_wxp_x86-32_disc_m1.
2006-06-03 17:18:09 : <PREP> Removed all attributes from \I386.
2006-06-03 17:18:09 : <PREP> Deleted old method 2 related files.
2006-06-03 17:18:09 : <PREP> Generated \I386\winnt.sif file.
2006-06-03 17:18:09 : <PREP> Created a backup of \I386\txtsetup.sif.
2006-06-03 17:18:09 : <PREP> Created a backup of \I386\dosnet.inf.
2006-06-03 17:18:09 : <PREP> Restored original setup: method 2 was used previously.
2006-06-03 17:18:10 : <PREP> Cleaned up \$OEM$\cmdlines.txt.
2006-06-03 17:18:10 : <PREP> Deleted \$OEM$\DPs_ROE.cmd.
2006-06-03 17:18:10 : <PREP> Created temporary working directory.
2006-06-03 17:18:15 : <SLIP> Extracted DriverPack MassStorage to a temporary working directory.
2006-06-03 17:18:38 : <SLIP> Slipstreamed DriverPack MassStorage text mode drivers.
2006-06-03 17:18:46 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2006-06-03 17:18:47 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2006-06-03 17:19:32 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2006-06-03 17:19:33 : <SLIP> Extracted and deleted \I386\svcpack.in_.
2006-06-03 17:19:33 : <SLIP> Updated \I386\svcpack.inf file to support KB883667.
2006-06-03 17:19:33 : <SLIP> Updated \I386\txtsetup.sif file to support KB883667.
2006-06-03 17:19:34 : <SLIP> Updated \I386\dosnet.inf file to support KB883667.
2006-06-03 17:19:34 : <CRIT> Could not extract bin\finish.7z to \$OEM$\$1.
2006-06-03 17:21:48 : <CLNP> Temporary working directory successfully deleted.
2006-06-03 17:21:48 : Program terminated.
Also note that I selected Method 1. I did this on purpose so that the BASE would not delete my presetup.cmd. Also I only selected to do Mass Storage Text Mode integration. I did this on purpose so that BASE would not try to do anything to my source regarding hotfixes.
187 2006-06-04 06:29:53
Re: SOLVED: Virus in cmdow.exe?! (11 replies, posted in Feedback and Support - DriverPacks Base)
It's possible that there is some malware out there that utilizes cmdow.exe to hide some of their activities. But cmdow.exe itself is not spyware or a virus. It's been used by many people around here for years with none of the typical symptoms of being infected.
FWIW, I've never heard of a security product detecting cmdow.exe as something potentially dangerous before.
188 2006-06-02 15:48:49
Re: Problem with latest DriverPacks, some things still remain "unknown" (7 replies, posted in Feedback and Support - DriverPacks Base)
This is currently in discussion here http://forum.driverpacks.net/viewtopic.php?id=28.
Also there is a sticky thread on the topic over at the old DriverPack forums at MSFN.
189 2006-06-01 02:03:02
Topic: [IMPLEMENTED] Unslipstream DriverPacks function (5 replies, posted in Feature Requests)
An undo feature - to unintegrate the DriverPacks could help to make testing and debugging easier/faster.
- Delete txtsetup.sif, dosnet.inf, etc. and restore the originals
- Clear out any DP related files
- Probably some other things I am not remembering right now
190 2006-05-31 07:00:43
Re: SOLVED: Could not detect any 3rd party DriverPacks (5 replies, posted in Feedback and Support - DriverPacks Base)
For example:DP_Monitor_CTX_wnt5_x86-32_100.7z
@Bâshrat the Sneaky, is it ok to have a _ character between "Monitor" and "CTX" ? I don't know how you are parsing file names, so maybe the extra _ is throwing something off?
191 2006-05-31 02:41:30
Re: SOLVED BUG in DriverPacks BASE 6.05: autoupdate for DriverPacks BASE fails! (7 replies, posted in Feedback and Support - DriverPacks Base)
By the way, do you always have those two rectangles in front of every line in your slipstream progress viewer? That's not how it should be...
I do, but it's only onscreen, not in the log file.