Search options (Page 8 of 99)

mass 809C is up for tests.

via [v1] commented
[NV-5] original commented and jeff's adaptation included

built on 809A I found in nightlies.
(( I had a "B" test here. on older Via.))

go find it.

hi

the code has an error

ms_2_hwids="="

Sandrion?
you are not listed in Bâshrat the Sneaky translations team, and, far as I know, not in any team.

edit....

OK..
Jeff posted while I wrote.

it is not my call.
New helpers are welcome.

apology to sandrion

Hi Krick.
listen...

Jeff can code faster than I can type.
CODE masters usually / do not ever/ explain what they do.

What he wrote sounds gruff?
To ME it sounds like the sweetest possible sundea fudge, and that is because I know he went a long way to explain all this.
Jeff has in essence explained a few not widely known possibillities.

There are a lot of changes in progress @ DriverPacks, and you are privileged to see a preview of the future.
Welcome to the Flux.
The past won't be forgotten.

YOU will look for that. You will be helpful in looking at backward compatibility.

You can help us help you.
We are not GOD.
We brainstormed toward a future, we never forgot older OS. However.. Driver writers do. WE already think about creation of "obsolete driver" DriverPacks and 'incompatible contemporary" (in which selecting one excludes other.).. but we are a handful of people helped by far too few.

hmmm
kickarse does not have access to the DP team topic echoplatoon posted in..
I will repeat a line from a post in that topic.
so, I am interested in any improvement on a scan tool so that we might have standard output and no blind spots..

repeat from this topic.
I would like to mention that utilityspotlight05 (in VBS) has a few really desirable things.
it does not only get all sorts of hardware ID (it gets PCI, usb/audio and so on) but it also collects version (version is VERY IMPORTANT), date, and it will try to get specified OS.

I cannot post all content from the private forum, but the sorting and pruning guru (syspreppers are focussed on no conflicts.) and graphics master, and I, and the old style single machine installer guru..
(disc based releases have to work for all, but we will try tell you how to filter..)
base line for all of us is this.
DriverPacks need a scan tool so that we might have standard output and no blind spots..

I would like to mention that utilityspotlight05 (in VBS) has a few really desirable things.

it does not only get all sorts of hardware ID (it gets PCI, usb/audio and so on) but it also collects version (version is VERY IMPORTANT), date, and it will try to get specified OS.

I've tried to contact the original developer, but got zilch.

hi
it does not scan for SCSI
example
[N-5]
ms_count=2
>> pci. blabla>>
ms_2_tag="nvrd325"

ms_2_sysFile="nvrd325.sys"
ms_2_hwids="SCSI\NVIDIA__Raid_Disk________,SCSI\__NVIDIA_______Raid_Disk,SCSI\NVIDIA__Raid_Disk_20_____,... not PCI

Rats, NV again.

If the silicon hyll battle left us bleeding, what do we say about NV.
The twenty odd download links at LAN is getting us No Volunteers.
(the topic is in lan, but the download links in there.. They all have mass storage drivers.)

in mass, the big problem is that they use and have PCI AND SCSI lines with dupes, and I had to leave out a driver because I don't know how to add one that has a unique PCI hwid with a duplicated SCSI line.

hi
imho, KTD in method 2 is a waste of time.
it puts the present releases in INF/path, but it apparently does not have the capability of switching between ATI and NV installers, because we use exceptions and those poke 7zipped installers in some cases.
(NV don't, and ATI have them. When you swap an NV with a ATI the ATI 7z-sfx is not going to execute, because it was not ran in initial setup.)

We probably discussed KTD and DPinst.
SAD and warmsnow can take the latest DriverPacks releases and do a proper post setup minisetup.
You fire up SAD's dp.cmd (this ought to be more in the limelight) or warmsnow's and get a minisetup with the latest builds you put in the disc, AND SAD uses the exceptions..

fwiw, the super short M1 I made for myself moons ago supports all but the latest chipsets and setup is just as quick..

Hi
LAN 8.05.3 (the released third revision of LAN in MAY) was way after 8.02.2 testpack.
JakeLD mentioned DP_LAN_wnt5_x86-32_806A.7z in this topic

the latest testpack I know of is
DP_LAN_wnt5_x86-32_808a.7z

RichardBenfield
did any of that stuff I wrote make sense?

This is a serious question.
DriverPacks univarsity gets seeded by user questions.
(I hear elementerary school kids in the flanders learn to write proper english. I write my way of Flemish.)

Richard?
Ask for a comment by JakeLD.

I am sure he can whittle down his work on DriverPack MassStorage in a flash. (probably has a couple dozen rollouts sets saved)
He was taught to add drivers per OS.
He knows what syspreppers do.
He was shown our ways and he showed us his ways.

For a customised txtmode.
first do trimming and maybe do load order.
We will ask that you show us how you were adding your own, AND WHY you killed those you killed.

We see people telling us this version/vs/that vs/other, and sometime, they tell us the modi.
in graphs. 70 Hz is not applicable to many widescreen. The driver defaults to 70.

in mass, we like to not allow a non-popular generic being boss.

Hi,

the idea behind KTD was a sound idea but we had no real minisetup running after hardware was changed and KTD had its limitations.
The availability of microsoft's DPinst.exe has made possible new tactics, and DriverPacks BASE actually implements them.
The SAD disc is a possible, and a regular DriverPacks BASE streamed disc has a cmd file to run DPinst.exe which will run the driver install tool and it will use the method the source was streamed with.
To wit, in M2, the packs get uncompressed to hard drive, and a DPinst session runs which is like a minisetup with all DriverPacks exceptions, but it does not do a windows re-install. ((a full launch of hardware detection and driver setup))

in M1, the packs are already semi uncompressed on DVD (in cab format), and copied to HDD, and hardware detection and driver setup then runs.

adding these functions made KTD sorta obsolete. But it will also function when the source was streamed with KTD enabled and the script will perform the KTD inF seeding.
This means you can update a KTDeed drive, to an updated KTDeed. (That is what I reckon it did when I last tried this.)