tomidis

I have in my winnt.sif NonDriverSigningPolicy = Ignore and everything is installed without warnings or errors

Do you have integrated some drivers pack besides 5eraphs updates pack? I don't have that driver signing warnings But now you know what caused your error @T-13 --> in FullUnattended mode this drivers wasn't installed and that caused error @T-13 once again from ref.chm now you must discover from where are those unsigned drivers, I doubt they're in 5eraphs update pack because I don't get those errors

I was meaning about full unattended mode, if you have all answers in winnt.sif, then installation process don't stop for example at regional settings screen. That's why is the same if you using FullUnattended or DefaultHide, like as I said, I was getting errors with FullUnattended switch.

bartgrefte, this is from ref.chm I suggest you to try with UnattendMode = DefaultHide I was also getting some errors with UnattendMode = FullUnattended Your installation won't stop if you have all answers, no matter if you using FullUnattended or DefaultHide

Can someone explain me some thing about xp mui files? I was translated xp x64 german mui files to croatian (with rc-wintrans) and when installed and switched to croatian everything is translated to croatian But after I get Windows Update some translations are lost So I noticed what's the problem: for an example original winlogon.exe has version 5.2.3790.3959 and after update is version 5.2.3790.4516 my winlogon.exe.mui has version 5.2.3790.3959 and after update winlogon.exe to version 5.2.3790.4516 translations are lost So I changed with XNResourceEditor winlogon.exe.mui version from 5.2.3790.3959 to 5.2.3790.4516 and translations returned This happened with few other files like shell32.dll (6.0.3790.3959 to 6.0.3790.4559),.... I'm now interesting why I must change mui file version so the translations are accepted after windows update, because in original german MUI translations remains after windows update Where and how are mui files version information stored? is it somewhere in registry or does it mui file itself must contain something besides version information about main exe or dll that it translates?

problem solved errors caused Windows Live Messenger true addon created by DarkMadness for XP x86 Well, I modified inf file for install on x64 os, and it installs and run without any error on xp x64, but with nlite it causes mentioned errors I'll try to somehow make it compatible with nlite johnhc thank you for your fast replies

johnhc, can you confirm is it result the same if you run nlite under x86 or x64 os, when processing xp x64 ?? I'm not sure what exactly I do, but last night I get one install without errors (Last Session.ini allways the same), but one update I left for test SVCPACK wasn't installed I'll test it more and post when I'm sure what's the problem

here is my unpacked source iso I have MUI inside $OEM$ but cmdlines.txt is processed after T-13 and errors @T-12 here is rundll32.exe and wrundll32.exe from nlited image but the files are not modified by nlite rundll32.rar I also tried install from original iso and installation finishes normally without errors

My processor and BIOS too, doesn't support hardware virtualization so unfortunately I cannot use VirtualBox to test my images Everytime I burn image to cd-rw and then test "live" install, and this is really painfull process Otherwise I use VirtualBox to test x86 images Source is: en_win_xp_pro_x64_with_sp2_vl_X13-41611.iso downloaded from MSDN nlite language is left croatian, sorry Isključeno means off Yes I use sometimes english xp, and sometimes croatian mui I also tried turn off Uxtheme patch and nothing I use exactly the same Last Session.ini like in nliting x86 XP Pro SP3 Errors starts exactly @T-13 I cannot post screenshot because I don't run image under virtual machine but errors are exactly what hgary1 posted in 1st post C:\Windows\System32\Rundll32.exe : Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item (OK) when I click OK another error appear but with diferrent exe Fixmapi.exe odbcconf.exe mstinit.exe regsvr32.exe logagent.exe unregmp2.exe Cmd.exe and so on... I didn't count how many errors appears, but approx. 20 to 30 errors and then installation continues but after first logon I cannot start anything, allways getting that error message

hi johnhc, now I get this problem also under x86 os when nliting xp x64 sp2 I always use fresh copy of xp files, and use nlite only once I read somewhere about permissions and ownership, so I checked my folder with xp files on d: disk and it was owner by system ?!, so I changed whole disk d: to administrator owner (I'm running xp as administrator) and all permissions to administrator acc, and then tested again but with no success I removed all KB hotfixes and updates only for faster testing but errors remains Last_Session.ini

I also getting exact this error messages I'm trying to integrate hotfixes to winxp x64 sp2, and these errors appears only when I nlited under xp x64 os (administrator acc) when I nlited xp x64 sp2 under xp x86 os, then everything is ok Anyone knows why is this happening??

Last_Session.ini didn't used ryanvm hotfix pack Maybe it has to do something with "N" version of XP Pro, because I figure it out that pop-ups shows for: Audio Codecs Legacy Audio Drivers Media Control Devices Legacy Video Capture Devices Video Codecs

After making an iso with nlite v1.4.8 I get that annoying driver signing warnings even for drivers that are installed automatically at first boot and later for all drivers installed by me, signed and unsigned. I didn't added any drivers to my iso, just used some tweaks, few components removal and I added some KB updates to MSDN VL XP Pro N SP3 iso. I also noticed that nlite adds following lines to HIVEDEF.inf and HIVESFT.inf HKCU,"SOFTWARE\Policies\Microsoft\Windows NT\Driver Signing","BehaviorOnFailedVerify",0x00010001,0 HKLM,"SOFTWARE\Microsoft\Driver Signing","Policy",0x00000001,0 and when i go to control panel -> System -> Hardware -> Driver Signing it's really set to Ignore but with no effect at all I also used DriverSigning.exe from http://www.boot-land.net/forums/?showtopic=3095&st=60 and still no luck. Please anyone can help??

I was searching for many things about windows unattended and reading this forum for a while so now decided to register and here I am!