Search options (Page 22 of 99)

IF, by the off chance, that lappy has an ICH9 chip, then there is a possibillity it will not see two hwids (dropped in our chipset pack which has iintel official (I had to place a few in sub folders to get all versions of same named files in), and then I I found two hwids 'cared for' in a HP service pack our chipset pack does not carry..)
(same filename, and version system by HP is way 'off whack')

chipset has a few holes in ich9 caused by intel. Chipset drivers have bus extenders and I caught a few "holes" in those less than 20 hours ago. BUT, I fear the holes I percieve are "fixes" by intel.

The mass storage matrix has been posted at the famous station driver site, but I see no chipset ICH10 posted yet.
That's my cold stopper, so far.
----------------------------------

erm, I never used reatogo .
That limits me.
We work hard to make it work DISC based setup.
And external drives are seldom meant to replace boot hdd.

I bet you can help us.
Your experience in TS is valuable to us

Let us agree that when this pack and fragbert's request gets 'finalised' by the moderator, that we accept new REQuests in NEW topics.

I would not pop a warning shot in the kneecap when they do 'tag a request after final', but I will ask that the topic gets a post when it was put in the sticky. (which is like finalising a pack in third party.) so that the user knows he should start a new topic for a REQ.. (and not tag ..)

When you develop a third party pack, please make our lives easy, and update the supported device list in the changelog.txt.
Some of the 3rd party DriverPacks have been so succesful that I recently  started thinking about requesting that a few of these become main DriverPacks. *
You probably have no idea how the changelogs for those are done, and how much time they take to update.. So it may be better we have 3rd party the way they are.

BUT, a txt about what is in the pack is useful.

( * I started thinking that because we see the need for some "exceptions" in a few drivers here, which means an INI, and 3rd party packs have no INI.)

http://forum.driverpacks.net/viewtopic.php?id=2637

http://forum.driverpacks.net/viewtopic. … 734#p19734
testfile Sound A up from 804a to 804b. (your line added in 804b)

After you post the log, please do not try fix a source that has such weird errors.
Please Start fresh.
Make a clean fresh copy of the CD, and tell us about each important thing you do to it, and in what order.

Hi

PRO "gold", eh?
If this is an english language version, you can first slipstream Service Pack 3 into this.
Then make a copy of that SP3 streamed source, and then work on the SP3 copy.

Jeff mentioned the release candidate for DriverPacks BASE.
This works on SP1, SP2, SP3, and has much better cleanup, and I have NO sil3112r issues with that (I know QSC related errors have been worked on in that RC.)
http://forum.driverpacks.net/viewtopic.php?id=2585

Hi nekote
open the mass storage pack, and edit its INI.
Move the section you want to use below others, and recompress.

see FAQ forum, on mass storage

Hi,
you must have been using DriverPacks BASE 7.05.2 with QSC OFF.

if you can hold your breath for twelve hours, we'll provide a new version with a new intel, and I will check what si3112r.sys does with the old base (QSC ON and OFF), and in the new base RC.

I used to recommend people turn QSC ON in Base705.2 in both Method 2 and 1 for a things like that.

these are test versions I linked to (when you scroll up, you see a link with promise in it)

Hi,

you are the first to report this.. Thank you.
Here is a solution. When it happens, hit escape. Setup will proceed.
The permanent solution is that you edit WINNT.SIF and add  OemSkipWelcome=1 in [GuiUnattended] section.

[GuiUnattended]
       OemSkipWelcome=1

I have no idea why this happens nor why adding the line fixes it, but it happens and this line gets you past this.

Chiefzeke, there was an error in mass***804b_promise

link updated to mass***804c_promise