fdv

The good news is that from your post I assembled the following below and it looks correct. I theorize that you should do the following: unplug all USB or other legacy removable media devices from the system. Go into the BIOS and make sure you have just two devices to boot from: CDROM and HDD (if you have more that's okay, they just need to be internal devices). Check the settings on the RAID controller in the BIOS. Make sure it has the exact number of devices specified, etc etc. Hey, you never know -- glitches happen. Once all this has been squared, try again. In my experience, acpitabl.dat stops are from boot device confusion on the part of the PC. [SourceDisksFiles] percsas.sys = 1,,,,,,4_,4,1,,,1,4 [SCSI.Load] percsas = percsas.sys,4 [HardwareIdsDatabase] PCI\VEN_1028&DEV_0015&SUBSYS_1F011028 = "percsas" PCI\VEN_1028&DEV_0015&SUBSYS_1F021028 = "percsas" PCI\VEN_1028&DEV_0015&SUBSYS_1F031028 = "percsas" PCI\VEN_1000&DEV_0060&SUBSYS_1F0A1028 = "percsas" PCI\VEN_1000&DEV_0060&SUBSYS_1F0B1028 = "percsas" PCI\VEN_1000&DEV_0060&SUBSYS_1F0C1028 = "percsas" PCI\VEN_1000&DEV_0060&SUBSYS_1F0D1028 = "percsas" PCI\VEN_1000&DEV_0060&SUBSYS_1F111028 = "percsas" [SCSI] percsas = "DELL PERC5 and PERC6/CERC6 RAID Controller Driver (Server 2003 32 bit)"

You didn't nLite anything, did you? What does "SHIFT 5 TIME JUST MAKES A SOUND" mean -- is there a hardware error going on? Does Win + R bring up a runbox?

Bah! It doesn't work! Nevermind. **** it.

ok, I think I know what the problem is. give me some time to make some fixes hopefully by weeks' end.

Common error, unrelated Okay, this is a start. I have a file called OFF2007.INF for program compatibility. Maybe adding it there will work. I will see. Strange that it works in a VM. Not an XP file, it's an Antivir file No I mean delete it from MY fdvfiles folder prior to running HFSLIP to INCLUDE languages Sorry about the confusion on that! Will check out Procmon later

It is doable. I forget the specifics, and it's stupidly difficult. You have to make registry edits to the Internet Explorer Zones (changes that the IE security control panel applet would not normally permit you to make). By manipulating Zones, specifically the LocalZone, you are telling Windows that your local network is essentially like the Internet, and can view media files (just like IE) but CANNOT drag and drop them from the network to the local machine (again, just like IE). I hope this makes sense. I would guess it's intuitive if you know about Zones. I ran into this once with settings I found and copied out of the REGINST section of SHDOCLC, I think. A few changes later, I had an INF file that allowed me to access and open files on the network, but drag and dropping was not permitted (it had one of those 'action not permitted' mouse cursors). Sorry i can't be of more help remembering the settings I'd discovered, but now you have a method whereby you can give it a try (instead of wasting time going down the file and network permissions road, which is indeed fruitless as VideoRipper noted). Edit: more detail. Zones all have numbers. 1, 2, 3, and 4. look in the HIVE files and you'll see allowed extensions for dragging and dropping for IE and the zone 4, which IIRC is the Internet. If you essentially copy the IE setting to the zone number of the LAN (is it 3, maybe? I forget) then you'll have a machine that treats files on the LAN as if it were IE looking at a website.

I had a look and didn't see much. Just one or two small things, and something that might have been a path error to a dll, but nothing that stood out. The service doesn't need to run all the time; Windows is smart enough to start and stop it as necessary, but I have it on auto. Be sure you are using this hotfix here, 893803 Here is a revised fileset for whatever it's worth. Like I say, I don't know if the few changes will make things different, but its worth a shot. http://www.vorck.com/windows/data/fdvfiles9b.zip

Sorry about that, man. The only reason that should come up is having a Compaq SCSI controller dating back from about 1998. You could uncomment the file in TXT... and LAY... I was pretty careful when I made these, way back. I even put in a file called FILES-SRVR.TXT to check against. It is possible I somehow missed something, but if it does NOT copy, and the system calls for it, then the installer wants to see it, and the only reason that I can think of right now is if it's actually needed by a device.

Thanks for the comments Chefken Can you run filemon and regmon logs when trying an install? I don't have a live system to test on yet, just VM. I am assuming your system installs AVira 9 personal just fine on an unmodified XP. I made the path change btw. There is one entry in HIVESFT for running defrag on the C drive that I don't know how to change. (Search for "defragpath") This is something that so far has baffled me. Some services install externally from the HIVE files and it's a real bit*ch finding them. Like RSOP... it had it's own INF and get this, it installs just like a driver. Talk about maddening. I found it by accident. I have service shutoffs in AXANT and for a while I thought that setting a reg key, even to off, would "resurrect" a service that should not show up, but that's not it either. Although I continue to look into this I have freaking scoured the files looking for some of these and some are quite elusive. The Avira thing puzzles the heck out of me as to why it works in VM. I use AVG personally and plan to deploy it so I will stay on top of this. Maybe I'll test tonight by installing and trying the free Avira and seeing what's what. A BSOD would... I'm thinkig out loud here... would probably signal a missing file driver, like a SYS file. If it were a DLL it would just error out I believe.

3a, bunch of bugfixes, adobe cs4 works now. non-US languages restored (to use, delete MY intl.inf file) have yet to test with camera. no one testing? someone give it a shot. be sure to read the readme file.

what happens when you type MSIEXEC in the run box what is the status of the MSI installer service in the Services contsole

From a fix standpoint, it looks like too many IE hotfixes in HF... I think many of those are obsolete. But the main problem: what happens when you type a URL into an explorer window? Is SHDOCLC.DLL on the system? The server fileset is very old, and it may have left an IE icon on the desktop. (Which should not function). Try this mod This will require some work on your part: inside you need to: 1. delete the existing two TXTSETUP and LAYOUT files that are for workstation (pro) 2. rename the TXTSETUP.server and LAYOUT.server files to remove the "server" 3. proceed from there I thin you see what I mean. I just modified TXT... and LAY... and threw them into the existing set 9. See how that works. I did this just now. Aren't you lucky

Can you run a filemon on it to see if there are fails? I don't have 2000 in a fresh install ATM. I do not have this problem on my fileset 8 machine. Let's plug away at this. Let me know if the MSI service is installed. It should be set to auto.

1. Infrared Device is not recognize in the device manager. Drivers are missing. On purpose. It was commented out in SYSSETUP under devices to install. Easy to add back, or copy that INF to the windows INF directory and through control panel, select add hardware and go that route. 2. The caps lock function doesn't work anymore. On purpose. I got tired of it so I made it a regular SHIFT key. Can be adjusted in AXANT5.INF 3. I have 2 notepads C:\WINNT and in C:\WINNT\system32 is it safe to delete 1. On purpose. This was done to always be able to open a file in that program even if there are path errors. You may indeed delete one. 4. ADMINPAK.MSI does not install. It might be missing some core files. Do other MSI install? I am not sure why this would be. You say 'pro server' but isn't adminpak for server only? I totally cannot recall. 5. Direct X 7 is installed. Is it really needed since, I want be using it for media. This computer will only store media not run it. It is not needed if it's storage only, but I do not know how to uninstall DX anything so I am no hgelp here. 6. A lot of empty folders are present, can I delete them? Yes. But I never was 100% sure what can do, so it might be best to change the name first and see if Windows still boots ok. (This has been addressed in my XP fileset) 7. How do I use the original Windows 2000 icons instead of the NT4? See AXANT5.INF 8. C:\WINNT\MUI\fallback has the same files different languages. Can I delete the obselete ones? Yes but not durectory 1033, IIRC 9. NMAPI.DLL is needed to run netmon.exe Add it manually to SYSTEM32 or if installing edit TXTSETUP to add it. 10. How can I delete the list contents to text file extension. See AXANT5.INF 11. How do I install unofficial updates, not sure what folder they go in? When in doubt, SYSTEM32

Fileset 3 up. The changes are not big, just numerous. Mostly to registry edits. A new custom keyboard for US users has been added (see the JPG for new characters). Right now I am testing with US keyboard and fonts only. I will componentize non-US shortly. I did this to isolate non-US for testing -- that's the only reason. This needs rigorous testing. It has already been tested with Office 2007 fully. Ambassador, your request has been implemented: userpasswords gone, userpa sswords2 now in place. Known problems after I tested this: my webcam didn't install (only the microphone worked) -- probably a missing video codec Adobe CS4 full suite installation halted with an error -- not sure of the cause yet

Hi all, I am including .jpg wallpapers in my XP fileset. For the regular one I am doing an original photo of purple lightning taken on my porch during a freak storm summer '09. I want to include a logon wallpaper (the default when you see the CTRL ALT DEL logon prompt). You will receive full C credit and in exchange I must have your permission to redistribute it with my fileset. There must be no conditions attached. I am posting this request here because I want users here to do the voting. Second and third placers will go into the fileset as alternate desktop wallpaper choices. Please try to keep size to a minimum. Resolution is up to you. My lightning jpg is 1024 x 768. If you specifically want to offer your own work as a wallpaper choice and NOT the logon screen, say so (after all, there will be a big logon box right in the middle of it). It is interesting to note that XP can display jpg wallpaper even without "Windows Picture and Fax Viewer."

Jaclaz, your first list is all boot-stuff. But your second one is new to me, so I stand corrected that bootland is singularly focused. I've only ever used it for PE stuff which is my limitation not theirs. 5eraph, no offense taken. There's only been one individual in my history of using this site that I didn't get along with (actually he had a problem with several of us here) and he's pretty much never around. I hereby purchase a virtual beer for you both

I'm actually comfortable with that: my celebrating MSFN isn't meant to convey either one. I don't really think other sites should shut down and turn out the 'closed for business' sign. I do, however, believe that MSFN is the cream at the top. You don't need to call me out; I'll specify for you. Go ahead and list for me those other sites that have Windows component removal projects, hotfix slipstream projects, post installation projects, making changes to windows prior to installation by editing setup and HIVE files, etc, all in one site. Then I'll agree my comparison is not justifiable. Caveat: singularly focused sites like bootland would obviously not apply. I didn't mention any, actually. But I won't call you out on them specifically, I'll just figure that when I go to techsupportforum, pchelpforum, computerhelpforum, techguy, geekstogo, tek-tips, etc. that any such site could have been set up by someone from here. I don't doubt it at all, but I still don't see others covering the breadth of ground that MSFN does. We've got a nice place here, and that's nearly the whole of what was meant. Don't deep six an entire novel-length post for a sardonic, throwaway remark at the end that's 2 lines long.

See my thread in the nlite forum where we address this very topic toward the end. No specific solution is offered but I think this will get you up to speed EXTREMELY quickly.

Someone help an old man's memory (hey, 38 is OLD! lol) Putting microsoft.com in HOSTS will not work, because MS hard-codes its own domain in... some DLL that it can always phone home unless you block it at the actual hardware firewall or by using specialized DNS service. Does anyone remember the name of that DLL? I was having this exact debate (XP phones home, no it doesn't you're just paranoid) the other week and it's driving me nuts!

Well, we have taken a left turn and probably we have veered into non-nlite area but I will loop around and address nLite at the end of the post. That having been said, the whole reg process takes experimentation. Is your system currently changed how you want it? Then do a search in your current registry and export the keys, then convert the REG files to INF (I have been doing this for over a decade so I am very, very good at it; I do recognize that it takes some fiddling) and then search for the same strings in the HIVE files. If they exist, change them, if they don't, add them. Make sure the HKU, HKLM, HKCU etc match. In other words, HIVEDEF is full of HKCU keys. It populates that whole branch in one big "explosion" and putting a bunch of HKLM or other keys will work, but results in a fragmented registry (which can of course be solved by a Winternals utility). I have run into this CurrentControlSet versus Set001 several times -- you need to see your current registry to know if it's smart to add it to the HIVEs. (Don't worry too much, adding keys that don't belong rarely causes a problem, it's the deletion that causes problems). Your absolute best bet of all? Install the OS on a totally clean system like a VM. Then install registry and file snapshot software. Set everything how you want it to be, compare before and after snapshots, and you will know precisely which reg settings need to be added or changed and which files have to go where, which you can adjust in TXTSETUP and LAYOUT. (Note that nLite edits SYSSETUP.DLL so that TXTSETUP and other files can be changed. You DO need to do this, or to take this edited file and put it into your original XP i386 folder so that you have it forever.) Finally, when removing languages, note that there are something like 3 or 4 lang files that Windows requires to boot (nlite keeps them automatically). The rest can be eliminated. nLite actually leaves a few Japanese and Hangul language files, as well as Croatian (for Nuhi himself of course) even if you select all languages for removal, so to really take everything out, you sometimes have to make changes manually.... Yes, there really are things that nLite leaves that it doesn't have to! Open up SYSSETUP.INF for example and you'll see the files that go into SYSTEM (not32, just system). You can delete them all and leave that directory empty. And if you set permissions on it by manually editing DEFLTWK.INF and denying system, you could conceivably delete SYSTEM. This DEFLTWK file can also be used to prevent the prefetcher from even being created by denying system permissions on that directory.) Like so: "%SystemRoot%\Prefetch",2,"D:PAR(D;;FAGAGRGWGXWD;;;SY)" ; DENY system Any hard-to-delete directory can work the same way, for example: "%SystemDirectory%\1025",2,"D:P(A;CIOI;GA;;;WD)(A;CI;GA;;;WD)" ; allow world so it can be deleted without deny access I'll stop before this post becomes "Fred's one million undocumented windows tricks that he's kind of pi??sed he's never seen anywhere else because not enough people read MSFN" ABout that last point: it seriously puzzles me why 'competitor' sites even bother carrying on considering by comparison they are literally in the dark ages, with users scared to death of editing system files, which the MSFN crowd got over years and years ago...

Yep. More specifically, since you just want the files and probably don't need all the information: grab here Buried therein you will find many dozens of settings. Not necessarily commented -- sorry!! But some are. And of course some are easy to spot. Open HIVEDEF for example and search for "ActiveWndTrkTimeout" and you will see a huge block of reg edits. The files are most notable for what they rip out... a lot of obsolete stuff and media crap. See also AXANT5.INF for many tweaks. I am making changes all the time these days. I just added but did not yet upload a tweak to have explorer always in view details mode because I got so sick of changing it. Anyway. 95% of the tweaks are well known, and just slipped into the HIVEs. There are some gems that are not very well known but I usually do try to post my findings in the right threads. The problem is that in my HIVE files I am trying to repair XP by getting it back to how Windows NT is supposed to be, so it has fixes like using CTRL ALT DEL for logon rather than... whatever the heck that other account pictures thing is. So you'd have to find that tweak and comment it out to change it, or run a second tweak later in the install process to undo it. (Which is what nLite's tweaks essentially do -- many of those values you see start out in the HIVE files and the nlite tweak INF simply changes them.) I suppose you could simply try renaming your HIVE files and trying mine to see how you like the result I guess.

ok now that I know what you mean. The file is MSHTA.DLL dependent. I do put that with IE.INF but by default my XP fileset actually leaves IE -in- (see the line in SYSSETUP.INF). If you copy that over to '32, expand it and register it (if it even needs registering -- probably it does) will that, alone, allow this userpasswords applet to work? I wonder. I'll test it when I'm at my VM on Tuesday.

See all of those lines with byte counts in LAYOUT that have an _x on the same line? That is Windows saying "Hey, install process, if you see a line with an _x in it, check the byte count against the one listed here. If it does not match, abort the installation." So you merrily change the byte counts for HIVE files to change them... but the LAYOUT line itself has a _x, so to make things easy and totally eliminate all of the self-checking, simply delete every single _x in all of the file lines in the entire file by replacing ,_x, with comma comma. Nuhi made nLite so that it would delete files in TXTSETUP, presumably for a faster installation. But oddly, nLite never modifies LAYOUT. To make your install go really fast, you can copy the file list from TXTSETUP right into LAYOUT. That way, LAYOUT won't waste a lot of time copying files that TXTSETUP doesn't even use. The best way to explain this is to download my fileset and compare TXTSETUP and LAYOUT. As long as the _x and byte counts are gone, Windows treats the files the same -- it's just that LAYOUT copies from media to one directory on the HDD, and TXTSETUP copies from this one directory to final destination on the same HDD. Editing HIVE files is the best way to put tweaks into your base install permanently. For example, why not fix the time zones permanently? They're in HIVESFT. What's the point of leaving all of that incorrect information? (Rhetorical, not asking anyone in particular). Sure, you can slipstream a timezone hotfix, but all you're doing is writing wrong data, then overwriting it with correct data. Same with everything else -- colors, icon spacing, file associations, network settings, service settings (manual, autostart, etc, you can even remove them, like indexing for example), and tons of preferences -- all of that is in the HIVE files. There is a wealth of data in these things that very few people seem interested in (speaking generally, not at you). nLite does edit these files to some degree, but does not scrub them completely. Check out HIVECLS, for example... the amount of junk related to windowscodecs.dll alone will shock you. It's a HUGE chunk of the file. Not an issue if you always use the proprietary Microsoft Photo format or do not care about registry size (and in XP, it's not really an issue like it was in 2000), but something that you could probably do without.

Just a quick bit of info that might be helpful, I don't know. These two keys control whether WFP is on or off. Simply use an invalid path like Z:\ to shut WFP off. These keys do NOT exist by default. HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","SFCDllCacheDir",,"z:" HKLM,"SOFTWARE\Policies\Microsoft\Windows NT\Windows File Protection","SFCDllCacheDir",,"z:" To turn it back on, point the path back to dllcache.