1,326

(13 replies, posted in Feedback and Support - DriverPacks Base)

Fixed now. I had entered 'about_10', while it should have been 'about_11'. Talk about the consequences of such a minor typo, heh wink big_smile

Sorry again, Siginet wink

KTD is fixed, too wink bugtracker link

Done! smile

Fast heh! tongue

Implemented the change: from now on, EVERY text mode mass storage driver will be named upper case!

You'll have to delete your QuickStream Cache directory Houz74 mentioned though, else the changes won't get applied.

Won't mattter. I'll change it though, just for the looks.

When it concerns RIS, RogueSpear and twig123 are the masters... I'm sure they'll help you out.

Voila, this issue is solved in the next version!

If this problem persists, I'll have to... But it will be included in the regular DriverPack MassStorage.

As of THIS moment, please post HERE the HWID of YOUR Silicon Image SiI 3112r controller, so I can create a list!

You're misunderstanding it, jtdoom...

You should open the svcpack.inf file and save it as a ANSI file. It's NOT related to the DriverPacks BASE's GUI language in any way... wink

1,335

(40 replies, posted in Other)

hehe big_smile

Thanks for your update!!! smile I didn't expect this. My goal is to write a more complete manual though, with screenshots and all wink smile

Your help is appreciated wink

Helmi is correct, I'm afraid.

1,337

(1 replies, posted in Feature Requests)

Well, it will be implemented one day, but definetely not now... It would require me to have some sort of database of all devices, manufacturers etc. A LOT of work, that is wink

Which specific 'problematic' drivers are you talking about? The JMicron one?

Yep, that's a known solution wink Already mentioned it in the Known Issues wink

mp3login wrote:
Bâshrat the Sneaky wrote:

@both: Already submitted the KTD bug to the bugtracker, was already reported by some one else. It's right here.

@mp3login:

this is the HWID of your ATI Radeon Mobility X1600:

And as you can see, it was not detected. I'll change that in the next version: NONE of the X series Mobility GPU's are currently being detected... A flaw in the .ini, you may say. If you'd like to fix that right away, just add these sections to your DPsFnshr.ini:

The weird thing is that it seemed to be working on some of the earlier builds. I'll try it out on some computers with non-mobility Ati graphics and let you know the results.

The older ATI Radeon Mobility cards are supported through a modified .inf file in the D\G\A\1 directory, which is why the older Mobility GPU's will be detected, and the newer ones won't. No need to test that! wink

Ok, thanks then smile

If you want it to NOW, then all you have to do is rename the /I386/RVMPUPPCK.IN_ file to something else before the slipstream, and rename it to its original name upon completion. wink

I don't think I will add a 'fix' for this problem, since these hotfixes are SUPPOSED to be included. I don't understand why they are not. Are you using an old version, perhaps?

The DriverPacks BASE does include them, but only if you're slipstreaming DriverPack Sound A, which you are. And yes, if an UpdatePuck is detected, it won't be slipstreamed either. It's strange that hp38guser's (or is it MeulC's) Dutch UpdatePack doesn't include them... they're well known.

1,343

(77 replies, posted in Site & Forum Issues And Feedback)

McStarfighter wrote:

I'm sorry for this, but I've many many problems about my mother's health and so my soul was and is "overloaded".

I'm very sorry again.

No problem smile Not at all. I'd react the same way if I'd be having a lot of problems in my personal life, I think.

I wish you the best for your mother's health! wink

@both: Already submitted the KTD bug to the bugtracker, was already reported by some one else. It's right here.

@mp3login:

this is the HWID of your ATI Radeon Mobility X1600:

PCI\VEN_1002&DEV_71C5&SUBSYS_00921025&REV_00

And as you can see, it was not detected. I'll change that in the next version: NONE of the X series Mobility GPU's are currently being detected... A flaw in the .ini, you may say. If you'd like to fix that right away, just add these sections to your DPsFnshr.ini:

[wnt5_x86-32__0021__D-G-A-2]
tagFiles    = 2
tagFile1    = "%SystemDrive%\ATICCC.ins"
tagFile2    = "%DPSROOT%\D\G\A\1\ATICCC.exe"
+hwids        = 0
-hwids        = 0
+infFiles    = 1
+infFile1    = "%DPSROOT%\D\G\A\2\*.inf"
-infFiles    = 0
commands    = 4
command1    = "%DPSROOT%\D\G\A\1\ATICCC.exe -y -o"%DPSTMP%"
command2    = "msiexec /i %DPSTMP%\ISScript9.Msi /qn /norestart"
command3    = "msiexec /i %DPSTMP%\ATICCC.msi /qn /norestart"
command4    = "rd /s /q "%DPSTMP%"


[wnt5_x86-32__0022__D-G-A-2]
tagFiles    = 2
tagFile1    = "%SystemDrive%\ATICCP.ins"
tagFile2    = "%DPSROOT%\D\G\A\1\ATICCP.exe"
+hwids        = 0
-hwids        = 0
+infFiles    = 1
+infFile1    = "%DPSROOT%\D\G\A\2\*.inf"
-infFiles    = 0
commands    = 3
command1    = "%DPSROOT%\D\G\A\1\ATICCP.exe -y -o"%DPSTMP%"
command2    = "start /wait %DPSTMP%\Setup.exe /K"
command3    = "rd /s /q "%DPSTMP%"

Odd....

Open the QSC directory and delete the directory in which 'Chipset' is mentioned. Now retry.

muiz just told me that there are new BIOS'es released by Silicon Image. Perhaps that might solve the problem?

I thought it was only an issue for the BusExtender drivers... well, then I'll apply it to ALL mass storage text mode drivers in the next update wink Then it definetely will be solved.

1,348

(7 replies, posted in DriverPack Sound)

What Helmi says smile

You can easily leave out DriverPack Graphics C - very few people actually need support for Quadro or FireGL GPU's. That's already 34 MB less. And actually it's rather towards 300MB than 200 tongue

You could also 'hack' DriverPack Graphics A by leaving out the ATI CCC or the ATI CCP, depending on which one you use. That will save another 20 MB or so.

1,349

(40 replies, posted in Other)

pyroman1 wrote:

@Bashrat -

Did you remove the uAwiki entirely?  I noticed that the changes I made for the GUI version are now gone.  I had pointed people from other forums to that help file so that I wouldn't be posting directions on other forums that could change with file revisions.

If you did, do you mind if I revert back so that people can use it until a new help file is developed?

What exact changes do you mean? Some changes to the DriverPacks BASE tutorial? I'm very sorry, but the GUI is entirely different, so I don't see the use of actively linking to those pages. You can restore it if you want to, but please put a BIG warning on top of it...

@maxximum & sat_disch: thank you very much! I will take a look at both of them.

Hehe smile

Yes, I'm working on the site updates smile I've got a talented designer doing a redesign, and I'll start working on the website itself soon.