do you have a link to a 'tested and known to be good' driver (perhaps from Nvida) that works? We will slip it in!

PS... We do apprecieate that you tried to search for a related topic (Yea! He used serarch - Woo Hoo!).

       However the main Topic of this thread is in regards to the UNI to ANSI issue i fixed a couple of years ago

       Let's Do a new thread in Graphics Forum with a title that begins with [REQ] Nvidia RIVA.
       A link to here and a link to find the tested known good driver would be considered most polite.

Thanks for the feedback, it makes DriverPacks better for everyone

another tip I posted long ago was that I use the advanced settings in RVM, and let it do uni 2 ansi.

------

Another thing I look at is when I use NLite.
It changes the setting for OEMpre-install (it is set by default) to YES, which is not the setting DriverPacks normally uses.

Oh, interesting thing is, when one changes it to NO, the nLite.cmd is still processed.

--------

And last, we do have a bug.
I recommend to ALWAYS use QSC.

Edit:
Here's the topic - http://forum.driverpacks.net/viewtopic.php?id=1741

It pleases me to know why it was happening now... 

Beside svcpack.inf problems:

When winnt.sif is in unicode - the output file (winnt.sif) is 0'ed

When DOSNET.INF is in unicode - the output file (dosnet.inf) is 0'ed

When TXTSETUP.SIF is in unicode - the output file (txtsetupa.sif) is 0'ed

It looks like uni2ansi.exe from BASE isn't called in any situation...

PS.
nlite has no problem with svcpack.inf in unicode

-------------
BTW.
One more problem with BTS_base

I have yet to see one instance where
DPsFnshr
called from guirunonce will  finish properly for me.
It in most cases leave D with drivers intact or only partialy deleted
I don't know what breaks it - net 1.1 from svcpack?
first logon as administrator?
It simply quits in the middle of the work.
*Might be the fault of "exit" in one of my cmd* I think - more test....

I think I will try to remove guirunonce call and try to run it manually AFTER 2nd restart right now...

*doesnt't matter*
So it doesn't matter if
- winnt.sif is or isn't pressent
- makecab is newer or older (as in DP BASE)
- expand is newer or older (as in DP BASE)

Also dosnet, txtsetup are modified properly with hdaudio entries

uni2asnsi.exe WORKS if called by hand

It clearly isn't called or is called for bad file
I think it's typo main BS_BASE code
%% insted of %
%2 %1
temp files are mistaken etc.

As I can't see code as I could some time ago when it was .cmd files I can't pinpoit it to single line
Send me source and I will look over it if you want.
anonim1979[AT]yahoo.com

PS.
type method is 'dirty' hack
type might not be present
also some unicode letters might be changed into illegal characters especially that some strange code page might be set...

I have a question.
Did you have a WINNT.SIF in the source before you ran Base?

We've tried to find what makes uni2ansi fail.
(I have no idea how Base is supposed to detect that the svcpack.file is in unicode, but if it is, it should be converted to ANSI before fedit slips the lines in.)
-----------------

My personal solution is that I openend the existing svcpack.inf in notepad, and saved as, where it shows the type of coding, and save in ansi.
Because we knew of the bug, I put an ANSI coded svcpack.inf in the "clean copies" of affected source CDs I have on hard disk.

Mind you, I like the KIS principle.
If we can do it with "type", this should be looked into by a code team member.

DPs_BASE_7052
corrupts svcpack.inf when adding entries for audio DP (any A / B / or both) when svcpack.inf cabed in svcpack.in_ is in unicode insted ansi.

My tests ( 2 computers , clean and modifies sources, checked first newer wersions on expand, makecab before finding problem) on XP PRO *PL* (polish) SP2.

The problem is due to bug in calling uni2ansi ( I'm 99,9% sure ) from main *.exe file ( uni2ansi.exe itself works OK)
svcpack.in_ is properly expanded, uni2ansi is badly called/or is not called at all, fedit corrupts unicode file, makecab cabs it back...

When svcpack.inf is in ansi  (Polish (and probably other international versions) starts with UNICODE coded file)
by using uni2ansi.exe from DP_BASE or simple trick from DOS:

type file_in_unicode > file_in_ansi

then makecab'ed

DP_base procced it correctly and ads 2 entries with KB888111 and KB921401

BUT when svcpack is in unicode - the output file is 0'ed with only KB888111 KB921401 entries left.

That what corruprted svcpack.inf looks like:

"
??[

KB888111.CAT
KB921401.CAT
"

If I'm not mistaken Fedit doesnt work with unicode?

-------------

BTW.
About Garphic Pack C
As I can't find anymore my post (topis)  on msfn (IIRC) (it was in Graphic Pack C topic) with some of this what is bellow.
About support of riva TNT / TNT 2 /vanta
The last _official_ drivers with support for them were (no matter what is written on nvidia page and readme.txt LIES - send then 2 emails years ago and no change)
66.93_win2kxp_international.exe

with nv4disp2.inf

[NVIDIA.Mfg]
%NVIDIA_NV04.DEV_0020.1% = nv4_TNTxClass,            PCI\VEN_10DE&DEV_0020
%NVIDIA_NV05.DEV_0028.1% = nv4_TNTxClass,            PCI\VEN_10DE&DEV_0028
%NVIDIA_NV05.DEV_002C.1% = nv4_TNTxClass,            PCI\VEN_10DE&DEV_002C
%NVIDIA_NV05.DEV_0029.1% = nv4_TNTxClass,            PCI\VEN_10DE&DEV_0029
%NVIDIA_NV05.DEV_002D.1% = nv4_TNTxClass,            PCI\VEN_10DE&DEV_002D
%NVIDIA_Win2KDualView%   = nvDual,                   DISPLAY\nvWin2kDualView
%NVIDIA_MultiView%       = nvDual,                   DISPLAY\nvMultiView

/......../

; Localizable Strings
NVIDIA                 = "NVIDIA"
NVIDIA_NV04.DEV_0020.1 = "NVIDIA RIVA TNT"
NVIDIA_NV05.DEV_0028.1 = "NVIDIA RIVA TNT2/TNT2 Pro"
NVIDIA_NV05.DEV_002C.1 = "NVIDIA Vanta/Vanta LT"
NVIDIA_NV05.DEV_0029.1 = "NVIDIA RIVA TNT2 Ultra"
NVIDIA_NV05.DEV_002D.1 = "NVIDIA RIVA TNT2 Model 64/Model 64 Pro"
NVIDIA_Win2KDualView   = "NVIDIA Dualview"
NVIDIA_MultiView       = "NVIDIA Multiview"

and in GPC first supported is geforce 256 (7x.xx driver serie I think, probably 71.89_win2kxp_international ?)

[NVIDIA.Mfg]
%NVIDIA_NV10.DEV_0100.1% = nv4,                      PCI\VEN_10DE&DEV_0100
%NVIDIA_NV10.DEV_0101.1% = nv4,                      PCI\VEN_10DE&DEV_0101
%NVIDIA_NV10.DEV_0103.1% = nv4_WSApps,               PCI\VEN_10DE&DEV_0103
%NVIDIA_NV11.DEV_0110.1% = nv4,                      PCI\VEN_10DE&DEV_0110
%NVIDIA_NV11.DEV_0111.1% = nv4,                      PCI\VEN_10DE&DEV_0111
%NVIDIA_NV11.DEV_0113.1% = nv4_WSApps,               PCI\VEN_10DE&DEV_0113
%NVIDIA_CR11.DEV_01A0.1% = nv4_Crush11,              PCI\VEN_10DE&DEV_01A0
%NVIDIA_NV15.DEV_0150.1% = nv4,                      PCI\VEN_10DE&DEV_0150
.....

; Localizable Strings
NVIDIA                 = "NVIDIA"
NVIDIA_NV10.DEV_0100.1 = "NVIDIA GeForce 256"
NVIDIA_NV10.DEV_0101.1 = "NVIDIA GeForce DDR"
NVIDIA_NV10.DEV_0103.1 = "NVIDIA Quadro"
NVIDIA_NV11.DEV_0110.1 = "NVIDIA GeForce2 MX/MX 400"
NVIDIA_NV11.DEV_0111.1 = "NVIDIA GeForce2 MX 100/200"
NVIDIA_NV11.DEV_0113.1 = "NVIDIA Quadro2 MXR/EX"

.....