-
you have to regsvr32 /s %systemroot%\system32\CLVSD.ax that's all....I think
-
I've used nLite to customize my XP SP2 setup a little, but now when I want to customize my start menu (regular, not the classic), on the advanced tabthe list of start menu items is completely blank. So now I cannot choose to cascade the config panel, or remove my documents from the start menu. When I look in the registry I don't have the key "CascadeControlPanel" in [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] but when I add this as a string with the value 'YES' it still doesn't work. Anybody any idea?? TIA GoeniGoeGoe
-
Ok, Astalavista thanks man it works. It's really strange that my win xp cd contained only the uncompressed winntbbu.dll, so if I just replace that file with a compressed file winntbbu.dl_ it works!! Thanks guys for your help!!
-
ok thanks, I'm just trying Astalavista's latest post, after that I will try yours...thanks for helping me man!!! I was just trying your batch, but it just keeps on looping, I think you forgot an exit somewhere, cause I get the "everything is ok" message from modifype.exe. but after that it goes to the :error and then back to the :start. But no probs I just did: modifype.exe winntbbu.dll -c and I got the "everything is ok" message. I'll try after I see if Astalavista's post is working
-
these are the entries for winntbbu* : winntbbu.dll = 100,,,,,,,2,0,0 ehm ok there is only one entry, the one above
-
He Astalavista, Yes, I downloaded your Christina Boot Screen Setup, because I only had an uncompressed winntbbu.dll, I uncompressed your boot screen file (expand -r) and put that on my disk. I just tried using my own original winntbbu.dll and only editing one bitmap file, and it didn't work, I get the same error again. I also attached an image of my cd, as you can see I don't have winntbbu.dl_. And no my setup isn't OEM, it's just regular from the store... Hope it helps, GoeniGoeGoe Image of XP CD
-
In my SP2 dutch XP setup CD, I do have the winntbbu.dll file, but it is not compressed. It just resides on the disc uncompressed like winntbbu.dll. I also have the file winntbba.dll, also uncompressed. I'm having the same problem (error copying winntbbu.dll) when using your Christina winntbbu.dll file Astalavista.
-
When I use nLite to strip my WinXP setup and add device drivers, I always see some sort of progress bar with the text "Extracting CAB" => "Integrating Drivers" => "Packing CAB". So I think this program is doing what you want to do for your own XP CD, maybe you can ask around the forum of the nLite site (http://nuhi.msfn.org/) or send a mail to the creator of the prog? Maybe it helps...later
-
Hello people, I was following the different guides here for slipstreaming my raid driver into my unattended wxp setup, but I stumbled onto a little problem. The txtsetup.oem file is in another directory as the rest of the driver files, like this: [NT4] <- directory [WINXP] <- directory [WIN2000] <- directory [WIN2003] <- directory txtsetup.oem <- file so all the driver files for the winxp setup are in the winxp directory, but all the guides are saying, throw the txtsetup.oem and driver files in ONE directory. But I was thinking, aren't the driver files in txtsetup.oem referenced/linked to the xp directory. this is part of my txtsetup.oem file: [Disks] d1 = "Promise FastTrak 376/378 Driver Diskette", \fasttx2k, \ d2 = "Promise FastTrak 376/378 Driver Diskette", \fasttx2k, \nt4 d3 = "Promise FastTrak 376/378 Driver Diskette", \fasttx2k, \Win2000 d4 = "Promise FastTrak 376/378 Driver Diskette", \fasttx2k, \WinXP d5 = "Promise SATA378 Driver Diskette", \ulsata, \ d6 = "Promise SATA378 Driver Diskette", \ulsata, \nt4 d7 = "Promise SATA378 Driver Diskette", \ulsata, \Win2000 d8 = "Promise SATA378 Driver Diskette", \ulsata, \WinXP d9 = "Promise FastTrak 376/378 Driver Diskette", \fasttx2k, \Win2003 d10 = "Promise SATA378 Driver Diskette", \ulsata, \Win2003 TIA