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...

I usually don't even change it to Dutch (done that maybe two/three times, in the early beta... most of the ini I kept in my logs folders show it is left to default (english).

I am doing the first burn on a method 1, including sound a.
It just finished.

(winnt.sif had a couple instances of ;;;;;;;; in the last line of oempath, and a few double;; earlier in the path.)

CU...

It's not an 'old' bug, it's a KNOWN bug... as I've said in another topic of yours, currently I use the 'cmd.exe /c type' command to convert unicode (utf-8, big endian, litle endian, etc) files to ascii (ansi). The problem is that it FAILS whenever you try to convert a little endian file! Hence your corrupted svcpack.inf. I'm working on it!

It realy bugged me that the svcpack.inf did'nt convert the way it should. I also got a corrupt svcpack.inf file. So I gave it one more try. I startet DriverPacks BASE, but before I began the slipstreaming, I changed the language to English (USA) in the language bar. This made the svcpack.inf to convert properly.

I'm not shure if you alredy know this, but I desided to post my results anyway.

Gyppie

edit
next I know I ask a friend over here. BIG endian lover.
I wonder wether he'd be interested. the geezer must be approx my age.
used to be a great code guy on te forae.

as always, I stayed with 888111 until it finished
(HW found will pop over it but I know one process must finish before other))
and when that ended OK, HW found had no issue finding drivers.

I really wonder what would happen if one lets 888111 install when it werent't "needed"
corrupt svcpack inf content  again 57 bytes

svcpack.inf for hotfix 888111 corrupt

improvements, tho.
the GUI walk did not get me the "user errors"