Electrician

Oh. Like in "Mar TAiN get yo a** back in the house!" ? You have to excuse me, there was that time as a baby, when I stuck my dad's car keys into the outlet!!

Wait a minute, you mean your real name isn't TAiN? So what does it stand for? I wouldn't stand for that! (Prefer sitting) Are we done in red sector, I vote we go paisley sector next ?!

His web site tell's all; http://www.vorck.com/index.html What a handome mugshot! I like the lampshade look. (on FDV).

I created SYSROOT because it applies to keys that are NOT of the REG_EXPAND_SZ type. You can not use %SystemRoot% in a reg type of REG_SZ it will not expand. It is possible to mod the inf so that it (re)creates keys that are orignaly REG_SZ to be the expansion type - but they do not allways work. To avoid potential problems I stuck with the orignal type for the vast majority of the reg keys. To save myself some typing - and to make it easier to change the "fixed" location for those keys - I used a local variable SYSROOT. So what problem are you having? If you have not (or were unable to) remove a prev ver, delete the xpicons.inf from the winnt\inf folder before installing this newest ver. If your problem is in the slipstreaming then ??? It works as a silent switchless on a running 2k box. ed- btw in your post you said hfsvcpack_SW - this doesn't require switches.

You're welcome. Just trying to contribute. OK. I have sent TAiN the new version (2.20) which does the following; Installs ALL ICL files into c:\winnt Updates the Menu Shortcuts (for all users) for Paint, WordPad, System Information, NTBackup, and Internet Connection Wizard. This means when (if) you uninstall it also restores those shorcuts to their default. If you have removed those programs from your build then you get "pretty" XP icons for programs you don't have (so they don't work) - or if uninstalling - you get shortcuts with the ugly white box that also do not work. On a vanilla system it works for every frappen type I could check before/during/after the install-uninstall cycles. If the menu changes upset you guys, I can remake without - or you can extract the contents and mod the inf yourself. It could be changed to REMOVE those shortcuts when installing. Also, you could change the string var SYSROOT if you install to something other than WINNT.

A quick search on window size got me tip that said if Explorer doesn't remember it's size to try holding the CTRL key while clicking on the "X" button. Probably not related, since your complaint is first time. You could also kill the stored settings by using cmd prompt reg delete "HKCU\Software\Microsoft\Windows\ShellNoRoam\BagMRU" /F reg delete "HKCU\Software\Microsoft\Windows\ShellNoRoam\Bags" /F <typing error corrected. Ignore reg - applys XP. (my bad)>

Hey, FDV, maybe you should update your avatar!!! that really is one funny image.

Would be very easy. I just placed them where Bugs had put them originally. System Directory or it's own (maybe under programs?) which would be preferred? As for not installing - the inf should create the dir's. Looking into it... <back from testing> AH HA! The DIR ID's in the inf do not translate on all machines. Will switch back to older code for Root drive and set path from there. (tested on machine where it failed). now FIXED The machine where it worked (the one where I bothered to check all the files) has had SO many things installed - I do not know where to look. Guess it is moot point since the changed inf works always. Anywho, before I send this one up, can I get a vote as to where the files should go? (I SWEAR I will test this for add/remove on a vanilla W2k install before I let it go)

It may yet require a tweak or two (don't think so but you never know) but unless Bugs Bunny makes updated icl files I don't see why the name would need to change - or even then? I am thinking about making a NON silent version for post installs that would show a description page with credit to those where credit is due. (This ain't my baby, I just helped!) Should I? Bugs? BUG YES, PUTS EXPLORER.ICL IN ROOT NOT WIN DIR, FIXED. UNINSTALL WOULD FAIL (ATTEMPTING REG ADD BEFORE DEL) FIXED. FINAL (ahem) VER2 ON ITS WAY. Sorry about that, but I think it is safely no longer Beta. I have tested several ways on several machines now. Also added comments and ver number (2.10) to info in add/remove.

Quick thought - might be the boot file you use when doing the burn. Check the settings in Nero. 4 sectors, start 07c0, no emulation.

You are ALL abolutely bonkers! Besides, where can I find a duck and some rubber hose at this time of the morning? Naaaaaht! Come on Brain, (hic) I mean FDV, give out some more of that brandy. AHHHH, what a fine girl, what a good wife she would be [sound of someone falling over the bar]...

I said it was BETA, maybe I SHOULD have said ALPHA. There were errors in the inf file (used without checking) The files were copied but the reg entries were not done. It was a rush job... I now have a fixed version with the ability to uninstall, ready and on its way.

Kramy, no offense meant. We appreciate your work and just wanted to help/augment. Besides, some folk like things bundled, some don't, but it's all good. <halway through and changing methodology, bugs bugs {lousy syntax sintax spintax...}>

Do you want it with or without the Uninstall option in addremove? (working on it WITH) should have before weekend is out) Here is one with NO un-install and this is TOTALY beta. Seems to work, (tested on 1 machine only) ---uh seems it is to big-- only 690KB Well, will continue with an un-installable ver anyway...

I do my installs/upgrades/in-place upgrades, etc from a CD. However, I had a similar. problem with the Intel 10/100 NIC (on MOBO). I have all my Intel mobo related files in a cab file, but no matter what I did, the install failed to use the NIC. Short answer to a LOT of testing; the install was using the older file as listed in drvindex.inf and contained in the (SP or Drivers can't remember) cab file. Quick and dirty was to place my list (for Intel. cab) at the top. A better sol would be replace the file in the original cab OR maybe Put the files in i386 on the disk outside of the cab. You could add the inf and drivers to the list in txtsetup.sif. That had worked just fine - I only had the problem after CABing everything. You might find TommyP's slipstream project helpful - though it was designed with a CD in mind. BTW Welcome to the forum. This is a GREAT place for knowledge

Kramy, I have Gurgelmeyers version (patched) it works, and it matches Gas_Heds edits. I suspect your hacked version is being replaced by file protection. Use ResHAcker to change the ver number of the modded one to..6691 (and then run modifype on it). After you reboot check the ver number of the one in winnt. If it is still 6690 then that is why you do not have 256 color.

IMHO Xpize and other shell mods do not belong in hfslip. If I DID want to use that, I could do it on my own - and since the last time I tried it (xpize) on a system it was flakey, AND since all the projects to make 2k like XP are in a mutating-beta state, it seems wrong to add it. Like attaching a chain to another ship that sinking (you both go down). HFSLIP is great, flexablity is great, but there has to be a point where you stop the madness. btw I use a SP4 core USP'd with Gurglemeyers pkg, then modded to add several utilities, then HF-slipped with latest updates and drivers. WORKS LIKE A CHARM!

32 bit color is NOT really 32 bit COLOR - only 24 bit color and 8 bit "shadow" transparancy (on XP) and on 2000, it is 24 bit color with no shadow - just visible or not. TOO MANY FOR HUMAN EYES? Ever hear of subtlety? While a human may have a hard time distinguishing any particular shade from another, the presence or lack of makes a big difference in percieved quality. Which is why an image at 256 colors does not look as good as one at 16k or that as good as one at 64k colors. To quote "Beauty is in the eye of the beholder". That said, 24 bit (color) is fine with me even without the shading.

I had the same problem once. Win 2k would go through and format the drive, copy files to it, reboot and #!* the drive was bad! Even tried powerquest tool to reformat the drive, but same process. Tried another drive (a small klunker I had lying around) SAME problem. SO, I started over on original drive, with a diff motherboard. Format, copy files reboot <shut off and put drive on problem MOBO> boot, windows installed just fine. I chalked it up to something flakey with the AMD chipset. Was doing a re-install for a friend and was p***ed at my wasted time, so no more chance or attempts to test it further. BTW XP uses a slightly diff NTFS format than 2k.

Kiki Regarding your time zone setting in Winnt.sif... It ONLY works if the install is FULL UNATTEND that is just the way the lil' devil works. I once tried setting the value in the HIVE defaults - but even that didn't work. I had an idea that I might try using a program like resource hacker to search thru the various DLL,s and EXE's might find the value that M$ places during install - but never did the 'leg work'. Just seemed like it was more effort than changing the zone after install.

Kiki, Quick note in passing - you said you have boot.INI as extracted by bbie. Probably a typo - but JIC Should be called boot.BIN

I have used both usp 5.0 and 5.1 as the base for hfslip, esp since I wanted IE 6, DX9c, and newer fixes slipped onto disk. THEN I tweak the reg and add my own 'goodies'. Works just fine ! Sorta of my own extreme version.

Have you considered Tclock (posts by WildBill)? Or Search the web for DeskColor prog that give you transparent text on desktop, that and a few other (3,4,dozen?) utils will get you a more XP-like desktop.

I could wait a week. Although if M$ release a ton of fixes, that would require more than a 'bit' of work, you might want to release anyway? I would think just a note that it includes all WU security as of: <date> would be sufficient. Crimeny, a list (EVER growing) of all updates would be a bit mutch. btw Having just returned from an absence myself; Welcome back and Bless you!

There is nothing magical about the polish versions. IF you have access to an XP or win2k3 CD get the two files from there. Though I suspect that those with fast disk systems are not seeing any noticable improvement. The script just tweaks settings to cache more stuff in ram (and turns off a couple of things). I prefer to stay away from such twists (as opposed to tweaks). But as I said way back, I got faster boot times.