Search options (Page 67 of 99)

I asked, because that is a line that MUST say NO or zero

w\n\f\2 is for 311 and has roughly 170 HWIDs
W\n\f\1 also for 311, and one singe hwid.

thank goodness that this single HWID is still in the other..

Hi Narag, compare D-3 and L-4 INI, and their INF in the folder..
In the 7.04 pack, DELL had a newer version (signed) than what LSI (unsigned) had.

in 7.06.x, LSI is newer and signed, and supports all what DELL [D-3] had (plus one more).
Now, during txtmode, two drivers would "fight" for control, and one gets it.
later on, windows GUI starts, and PnP renumerates,
The OTHER can WIN.
BSOD.
Therefore I think it was wiser to delete D-3 (older signed) because it would compete with the new LSI (not only Newer, but newer and signed).

Do you see what I mean?

EDIT
WHY did I tell you to not delete old DriverPacks?
proprietary.. masks...
That new LSI will MOST likely support that chip you have, but there is always that possibility that it rather likes Dell's own brew.
When That happens, then is when you have to edit the INI and disable [L-4] in the older pack, and tell us about it.

HOOT, HOOT.

you are now officially ours, and first errant is about BSOD.

BSOD will mean 'bring sushi or dumplings' when we are done.

Hi,
Please test this new update asap.
Them drivers do have overlap, which is why the zero was used.

CAN ANYONE TELL ME WHY SEARCH (For Txt) DOES NOT BRING UP Txtsetup.sif IN THE RESULTS.

That was with caps-lock ON on purpose.

hi
do you still have Graphics A 7.04 or 7.05.2?
I ask, because this was stable.

And yesterday a Mass storage controller issue was reported, and it was caused by an LSI update done about fourteen days ago, which happened to have support for DELL.
The Mass storage DriverPacks update is ready for upload.

Hi

I said time will tell, and the time has come, I suppose..

here's a snippet of a long post.
----------------------------------
Because of this finding, we had to make a choice..
In our example, the OEM Dell driver [D-3] has a valid signature unlike the native LSI [L-4].
The same Dell HWIDs were suppored in LSI [L-4].
The Dell driver has also a slightly higher version number (1.21.08.00) and a newer date than the original LSI files.
So? What influenced our choice?
If D-3 is signed, keep it.
If the SYS file size for the one in LSI is different, definatetly keep Dell.
Still more considerations were made.
Is there a choice between unsigned generic versus signed proprietary? Keep signed proprietary.
A choice between Subsys and 'proprietary" subsys? Keep signed 'proprietary" subsys.
The filter (mass INI) must be changed to not use non-signed LSI in [L-4] for hwid signed in [D-3]
One could say that generic HWIDs in signed driver should be kept, and unsigned generics can be tossed away if one has it covered by a signed driver. Then, Dell won. BUT... It actually LOST.
In some cases, one can make an edit to a signed driver's INF, and kill the generic in there, keeping the specified subs. You can do that if this one is proprietary, and the other supports a lot more generic and SUB_sys HWIDs as well.
The LSI driver was not signed, older, and therefore Jaak edited the Mass storage INI for [L-4] so that it did not list DELL's HWIDs.
One "could" go as far as editing its INF as well, but since Dell was newer, it was the DELL's INF that got edited to not support the generic. (Jaak did that because Dell, just like Compaq and other OEMs do, often use proprietary chips. And, the SYS they use, is most likely specific for that proprietary chip. Well, the size was different as well.)
LSI's can most probably handle the generics better than Dell's prorietary sys-file.
Will this be the best solution?
Time will tell.
====================================

When That was written, The LSI was DriverVer=04/12/2004,1.10.00, and everything still worked for you..
And now it has DriverVer=06/13/2005,1.20.18.00, and it no longer works.
So, we'll try fix that..

I already have those, and what Helmi said looks to be true.
HKR,    Ndi\params\Channel, default,    0, "11"

I don't know if that driver has the information for all 13 channels.
I would have to compare..

Hi

dac960nt was replaced in my latest tests on XP source.
and TXTmode would use it

Will now run DPsBase on a win2000 and see what that does.

well, that entry replaced it in win2000
and txtmode would NOT use it

so, the two lines can co-exist

first thing you should look at is WINNT.SIF.
Nlite probably undid the change DPsBase made

when I do something like this for a final build..

X- - nLite - I previously did Unattended settings, and saved the WINNT.SIF file to a folder which has a few variants in it. (for re-use)
copy a source from storage drive to working folder
copy WINNT.SIF into it (if it is not yet in it)

nLite - (SP slipstream, if needed) Remove (Dotnet and little else) components , Options and Tweaks, LANGUAGES (99 Mb), regional settings and keyboards.
RyanVM - Slipstream RyanVM (previously tested and known good Updates) and Addons (dotnet and a few others).

Copy/SAVE that folder to storage.  (example, HOME_NL_OEMgold\XHNL_gold_SP2_LiteRVM\
Driverpacks - Slipstream driverpacks (all packs + some 3rd party)
make ISO (RVM or Nlite) XHNL_gold_SP2_LiteRVM70626.iso
rename the working folder to XHNL_gold_SP2_LiteRVM70626

after test in VPC and live machine tell me this is a good one, I can drop in variants of WINNT.SIF,

If the WIINT.SIF is one that does not autopartition/autoformat.. then I can also add a few lines just before EXIT in presetup.cmd

REM +==========================================================================+
REM |   Make CD usable for XP UPGRADE REPAIR method                    |
REM |   WINNTUPG  folder is needed   for this            |
REM |--------------------------------------------------------------------------|
DEL /F %systemroot%\system32\setupold.exe

Hi

you can help us improving the pack when you tell us which mainboards have not been properly supported, and by giving a link to the drivers you use to install those.