Content Type
Profiles
Forums
Events
Everything posted by fdv
-
These are Windows files not nLite. Windows needs them. They are found in i386. Setup would not have started if they weren't there... not sure what's going on. Keep looking I guess is all I can tell you... they have to be there. They are on OEM CDs as well.
-
The GPL license tells people what they can do with the software. It also says that the code can be sold for profit. By limiting to personal use or non-commercial use, that goes against the policy of the GPL. No? No. Where is commercial use addressed at all? According to the GPL, "Activities other than copying, distribution and modification are not covered by this License." The creator is perfectly within his rights to restrict commercial use. Also, do you see a warranty in the preamble? No, because there's not one there. TommyP can restrict the program's use but let's say that you ignore that because after all, he can't be there standing over your shoulder while you violate the added terms of his licensing and install it in a corporate environment. Then something goes wrong. Who knows what. You can't point to him and say 'it's HIS fault! He coded this program and he should be liable!" He did it not to make a fortune, but to provide a personal solution to Windows users. I can't speak for Tom, but he didn't do this to take on the kind of liability that can come with providing an enterprise solution. You mention selling for profit. Yes, you could conceivably do so. But by law and by the terms of the license you have to provide source and the copyright notice. Once people see that they can get this for free -- which you would be required to disclose -- you probably wouldn't make very much $$. Taking GPL'ed code verbatim and publishing it along with the authorship and selling it isn't a very good business model. The GPL doesn't make something public domain.
-
Maybe this could be FAQ'd. The problem is in TXTSETUP under [strings] with the spcdtagfilei variable. The error message is this, right? "Please insert the Windows XP Professional Service Pack [x] CD in drive A:" We need to take the tagfile out of the equation. Open TXTSETUP.SIF and LAYOUT.INF In BOTH files, do a search and replace for ,_x, to ,, (we are getting rid of the _x) In BOTH files, do a search and replace for = 100, to = 1, Find [sourceDisksNames.x86] 1 = %cdname%,%cdtagfilei%,,\i386 Change it to: [sourceDisksNames.x86] 1 = %cdname%,\win51ip,,\i386 Save both, close them, and retry. I might have missed a step but IIRC I have it right. All we're doing is telling XP that all of the files it needs are on the one CD. There is NO reason whatsoever for the 100 on each line, it just means it's a SP2 (or SP3 as applicable) file. By spelling out the cdtagfilei variable, we are eliminating having to fool around with hunting down what that variable has been set to. One less thing to worry about. Setup complains if LAYOUT is modified, but those little _x's after certain file lines tell setup "please check the size of the file, and if it doesn't match, throw an error." So delete the _x's and we can mod LAYOUT to our heart's content. While I am at it, I'll add this. The SourceDisks sections honestly don't matter either. You will see the following sections: [sourceDisksFiles] <--------- these are files common to ALL versions of XP [sourceDisksFiles.ia64] <--------- these are files for the IA64 (an Intel non-Pentium) processor* [sourceDisksFiles.amd64] <--------- these are files for the AMD 64 Processor [sourceDisksFiles.x86] <--------- these are files for only the x86 processor family * The IA64 is NOT a 64 bit Pentium like the Core 2 or Xeon, it is a separate processor entirely. So, what if you have a Core 2 duo, say? Well, that's an x86 family chip. You can delete the entire ia64 and amd64 sections (yes, really) and combine the x86 section into the main SourceDisksFiles section (makes sense, right? If you're running an x86, then you need the common files and the x86 files only). Of course, the XP you create this way won't install on an AMD64. If you have one of those, you'd add the AMD64 section files to the main SourceDisksFiles section. Also, you will see various underscores and numbers in file lines. Those can be deleted too. In other words, you can replace ,_1, and ,1_, with ,, and ,_2, and ,2_, with ,, etc etc etc etc with _3, 3_, _4, and 4_. Why go to all of this trouble? No need, really, I just thought I'd add this info while I was answering a TXTSETUP question
-
"I integrated ... IE 6.0 SP1". What did you do to do it? If you didn't do it right, and you used an IE6 hotfix or two when you used nLite to integrate hotfixes, then that's most likely what's causing the problem. The problem is that Windows 2000 has IE 5 files by default.
-
It's a reg tweak, not a file. Look in nlite.inf after expanding it; it's somewhere in there. It's 3 or 4 lines IIRC...
-
Here is the MD5 of my Windows XP setupreg.hiv A28B4B5E50C5814A3F7FFEAC09065F65 This is SP3 Maybe yours is corrupted? Maybe it's custom Dell and something's gone wrong otherwise.
-
...anyway, here's what you do. From a guy who knows 2000 by heart. Expand both 2000's and XP's SYSSETUP.IN_ file. Go to [infs.Always] See all of those INF entries? Let's compare. wsh.inf,DefaultInstall ie.inf,DefaultInstall secdrv.inf,DefaultInstall mdac.inf,DefaultInstall icwnt5.inf,DefaultInstall mstask.inf,DefaultInstall.NT msoe50.inf,DefaultInstall wab50.inf,DefaultInstall tshoot.inf,DefaultInstall dfrg.inf,DefaultInstall msinfo32.inf,DefaultInstall axant5.inf,DefaultInstall msnetmtg.inf,DefaultInstall mplayer2.inf,InstallWMP64 sr.inf,DefaultInstall fltmgr.inf,DefaultInstall icminst.inf,DefaultInstall apcompat.inf,DefaultInstall shell.inf,DefaultInstall shl_img.inf,DefaultInstall netupnph.inf,DefaultInstall devxprop.inf,DefaultInstall syssetup.inf,SpecialInstall pchealth.inf,DefaultInstall oobe.inf,DefaultInstall sapi5.inf,DefaultInstall moviemk.inf,DefaultInstall qmgr.inf,DefaultInstall au.inf,DefaultInstall skins.inf,InstallSkins drm.inf,InstallDRM wmdm.inf,InstallWMDM wmfsdk.inf,InstallWMFSDK wmp.inf,InstallWMP7 wmtour.inf,DefaultInstall mymusic.inf,InstallWMPlaylist syssetup.inf,WMPFeature swflash.inf,DefaultInstall dimaps.inf,DefaultInstall vgx.inf,DefaultInstall srchasst.inf,DefaultInstall bthpan.inf,DefaultInstall netfw.inf,DefaultInstall Here is the list from Windows 2000, and I comment out those INFs that I personally do not use: ie.inf,DefaultInstall mdac.inf,DefaultInstall dfrg.inf,DefaultInstall rsm.inf,DefaultInstall mpcodecs.inf,DefaultInstall icminst.inf,DefaultInstall agtinst.inf,,DefaultInstall spchapi.inf,,DefaultInstall shell.inf,DefaultInstall ;axant5.inf,DefaultInstall ;icwnt5.inf,DefaultInstall ;amovie.inf,DefaultInstall.NT ;wbemnt5.inf,DefaultInstall ;mstask.inf,DefaultInstall.NT ;msoe50.inf,DefaultInstall ;wab50.inf,DefaultInstall ;tshoot.inf,DefaultInstall ;msinfo32.inf,DefaultInstall ;msnetmtg.inf,DefaultInstall ;mplayer2.inf,DefaultInstall.NT ;rstorage.inf,DefaultInstall.NT ;apcompat.inf,DefaultInstall ;rca.inf,DefaultInstall ;wmpocm.inf,DefaultInstall.NT ;syssetup.inf,SpecialInstall I don't have the time to detail the XP INF files, though I happen to know most of them, but I think Google will help. Also, you can look at any of them easily to see if you "need" them by using "expand -r filename.inf" Hope this helps
-
Make this an INF file and install it [Version] Signature = "$Windows NT$" [DefaultInstall] AddReg = addreg DelReg = delreg [addreg] HKCR,".eml",,,"Microsoft Internet Mail Message" HKCR,".eml","Content Type",,"message/rfc822" HKCR,".eml\ShellEx\{BB2E617C-0920-11d1-9A0B-00C04FC2D6C1}",,,"{EAB841A0-9550-11cf-8C16-00805F1408F3}" HKLM,"SOFTWARE\Classes\.eml",,,"Microsoft Internet Mail Message" HKLM,"SOFTWARE\Classes\.eml","Content Type",,"message/rfc822" HKLM,"SOFTWARE\Classes\.eml\ShellEx\{BB2E617C-0920-11d1-9A0B-00C04FC2D6C1}",,,"{EAB841A0-9550-11cf-8C16-00805F1408F3}" HKCR,"CLSID\{06BE7323-EF34-11d1-ACD8-00C04FA31009}",,,"Outlook Express Mail Object" HKCR,"CLSID\{06BE7323-EF34-11d1-ACD8-00C04FA31009}\Implemented Categories\{40FC6ED3-2438-11CF-A3DB-080036F12502}" HKCR,"CLSID\{06BE7323-EF34-11d1-ACD8-00C04FA31009}\Implemented Categories\{40FC6ED4-2438-11CF-A3DB-080036F12502}" HKCR,"CLSID\{06BE7323-EF34-11d1-ACD8-00C04FA31009}\Implemented Categories\{7DD95801-9882-11CF-9FA9-00AA006C42C4}" HKCR,"CLSID\{06BE7323-EF34-11d1-ACD8-00C04FA31009}\Implemented Categories\{7DD95802-9882-11CF-9FA9-00AA006C42C4}" HKCR,"CLSID\{06BE7323-EF34-11d1-ACD8-00C04FA31009}\InprocServer32",,,"hex(2):25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,25,00,5c,0 0,4f,00,75,00,74,00,6c,00,6f,00,6f,00,6b,00,20,00,45,00,78,00,70,00,72,00,65,00,73,00,73,00,5c,00,6d , 00,73,00,6f,00,65,00,2e,00,64,00,6c,00,6c,00,00,00" HKCR,"CLSID\{06BE7323-EF34-11d1-ACD8-00C04FA31009}\InprocServer32","ThreadingModel",,"Apartment" [delreg] [Strings]
-
Here you go then
-
I want to remove 1394 networking from XP, need comments.
fdv replied to Short Circuit's topic in Windows XP
Expand SYSSETUP.IN_ find [DeviceInfsToInstall] 1394.inf 1394vdbg.inf put semicolons in front of these entries: [DeviceInfsToInstall] ;1394.inf ;1394vdbg.inf This section is the "Please wait while Windows installs devices" phase. Compact it again and put it back. You will need a modified SYSSETUP.DLL or you can use the setup DLL that nLite modifies. I forget which one it is. As long as the INF files that configure the "1394 Net Adapter" aren't loaded during Windows setup, do I really have to elminate the other files, like .SYS or .DLL etc. No. No need. -
Use mine. Download my ZIP and extract SETUPAPI.DL_ and put it in i386. Rename your old one .OLD or something. Also, open LAYOUT.INF and do a search and replace of ",_x," to ",," (comma underscore x comma to comma comma) and save the change. (_x instructs windows to check exact filesize, and if you edit LAYOUT, you need to remove all of these)
-
I have made myself one. Email me and I'll send it to you. It has other edits in it and I don't want to post it here lest others use it and have things go wrong. IIRC you can make edits to HIVE files without the setup complaining.
-
Q1:Are the "Windiz out of service" rumors true? If so, is there another alternative you recommend? Yes, windiz ceased updates. They did not get a takedown order, but from now on it looks like we'll have to patch manually. Q2:Is there a way to integrate a Readme.txt onto the desktop of a new install? Huh... I never thought of that. It's actually quite easy. I am leaning toward doing this in the next fileset. There certainly are things I need people to be aware of. Good idea. Q3:Can the w2k SFC hack be used to integrate a desktop Theme? From what I read -it is needed for a XP theme. Win2k doesn't use digitally signed themes. You can use any .theme file(s) that you find, but good luck finding one for 2000!
-
I maybe can rewrite the partition table with testdisk? I don't think that will help. Looking at the fact that you've XP and 2003 on different drives, I am suspecting more an invalid BOOT.INI entry. Try editing that (using the PE) and see if that doesn't do the trick.
-
The logagent error happens to me too but I just click through it. It won't harm anything at all. I created my own updated WMP9 exe anyway just a week or so ago. The error's totally ignorable. ADDITIONAL: 1). Is there a way to not to have the IE icon shown on the desktop with FDV file set? Yes! Open IE.INF Find [file.copy.dt] and put a semicolon in front of iexplore.lnk 2). Little fuzzy with Fred's site and the purpose of turning off WFP: *Why would w2k users typically do this? You know, that's a good question. For a while it was the Thing Everyone Did, more popular than free money. It speeds up setup by a bit, but then the problem is that your DLLs can be overwritten by old software... No thanks. I find WFP useful... but I just provide people the option if they want it. I think even experts are better off leaving WFP on. *Do you FIX or REPLACE the I386\SFCFILES.DL_(with the hacked(empty)). In the FDVFILES folder, delete the "OFF" in SFC.DL_.OFF and SFCFILES.DL_.OFF. Then, HFSLIP will automatically replace your SFC files with my versions which are turned off. Do not use FIX or REPLACE. *Is anything else needing to be done if I were wanting to do this? Nope, that's all you have to do to turn WFP off. There is a bit of backstory to the whole empty SFCFILES.DL_ and why you could use just that and not SFC.DLL, or use both if you wanted to. I won't get into it though; it's a bit boring Are there any problems with the new Dx9 redist as is in HF folder using FDV? My fileset will not conflict with DX9 integration at all. EDIT While I have you reading, when you're in IE.IN_ in a text editor, find the following lines and put semicolons in front of them: HKCR,"CLSID\{8856F961-340A-11D0-A96B-00C04FD705A2}\InProcServer32",,,"%SystemRoot%\shdocvw2.dll" HKCR,"CLSID\{8856F961-340A-11D0-A96B-00C04FD705A2}\InProcServer32","ThreadingModel",,"Apartment" HKCR,"CLSID\{EAB22AC3-30C1-11CF-A7EB-0000C05BAE0B}\InProcServer32",,,"%SystemRoot%\shdocvw2.dll" HKCR,"CLSID\{EAB22AC3-30C1-11CF-A7EB-0000C05BAE0B}\InProcServer32","ThreadingModel",,"Apartment" I discovered that this section causes an error when installing Adobe CS1 and CS2. It might cause problems with other software that have flash-based installation splash screens. I only discovered this with the Adobe CS installer though, and I use a LOT of software. I plan an updated fileset soon. I'll keep you posted.
-
Hi Gosh, XP and 2k3 have the root rights set by that INF file (I forget the name as well) but MS documentation states that 2000 has no root permissions set because (from MS): "Setup does not change the permissions on %systemdrive% because the Windows 2000 ACL Inheritance model would recursively try to configure all subdirectories of the root. Administrators should configure root directory security according to their own system configurations and requirements." So I thought I'd follow their advice and configure according to my own requirements, but 2000 seems to be more clever than I am.
-
Put the wrapped / new / other DLLs in the EXACT SAME program directory as the executable that needs them. All EXE files will look in their own folder first before looking in other directories.
-
Allright. First, are you sure you have valid CD media with no errors on the CD? Suppose the CD is fine, no scratches, no errors. This can be the result of an error on the disk in the first sectors of the drive. Test the drive with a more reliable tool than chkdsk, using a PE CD. Say the drive turns out fine too. Then, it's possible that some oddball situation is happening where Windows is failing to load a driver to see a drive because of, say, a faulty integrated SATA driver, doesn't see the SATA drive, and so gave you that message. But say you didn't integrate any drivers. Examine the BOOT.INI file for invalid entries. Do this using a PE CD, such as maybe Ultimate Boot CD 4 Windows. There are a lot of variables. Reply with info about your hardware and SP and patch level (in case someone wants to know that too).
-
"Error-Handler" process shows up periodically in task manage
fdv replied to 98 Guy's topic in Windows 2000/2003/NT4
Grab Regmon and Filemon. Put shortcuts on the NT desktop, and either let them run or start them when the disk thrashing starts so you can get some idea about what's triggering this. -
Hi folks, I'd like to keep people from creating files in the root like XP and Vista do. I did some reading at the MS Technet. Then, I expanded and opened DEFLTWK.INF and added a new string. Before I reveal it, here are the strings from the successor OS's: ; VISTA: "%SystemDrive%\",0,"D:PAI(A;;FA;;;BA)(A;OICIIO;GA;;;BA)(A;;FA;;;SY)(A;OICIIO;GA;;;SY)(A;OICI;GRGX;;;BU) (A;OICIIO;GRGWGXSD;;;AU)(A;;LC;;;AU)" ; XP: "%SystemDrive%\",0,"D:AR(A;OICI;FA;;;BA)(A;OICIIO;FA;;;CO)(A;;0x1200a9;;;WD)(A;OICI;FA;;;SY) (A;OICI;0x1200a9;;;BU)(A;CI;0x100004;;;BU)(A;CIIO;0x100002;;;BU)" The problem is that they both seem to do the opposite of what I want... they allow admin users to delete any folder (which is nice for undeletable system folders like IAS, ROCKET, NETMEETING, OS2, etc etc.) But the regular Authenticated Users suddenly can't write to anything. From the Vista string, translating into English: A;OICIIO;GRGWGXSD;;;AU Means A = Allow; OICI = pass ACL (inherit) to all child files and folders... IO = ...but don't apply the ACE to this object, just the child objects GRGWGXSD = General Read, Write, Execute, and list dir contents AU = For all Authenticated Users. I have tried all sorts of permutations to get the XP or Vista strings to work right, the admin rights are always fine but everything else is too restrictive on 2k where the same string works on XP. Anyone conversant in ACL's want to give me some clues? -- thx
-
Make yourself a UBCD4WIN and use some of the NTFS Undelete utilities on it. I hasten to tell you the obvious: do not use the drive until the exact moment you're ready to start recovering files.
-
The following value in the .SIF file used by Setup is Corrupted or mis
fdv replied to Scorpius Maximus's topic in HFSLIP
Okay Scorpius, here's the problem. Windows XP's TXTSETUP file is a total mess and has literally 6 or 7 [sourceDiskFiles] entries in it. So, I have consolidated everything into one section so that you can troubleshoot better. Use this file, but before you do, I want you to open LAYOUT.INF and do a global replace of ,_x, with ,, (two commas). Then use my TXTSETUP, put it right into SOURCESS/i386. This time, setup will give you a line number, and we can go from there. You might also need a modified setup dll, I don't remember, but best to use it anyway. It is titled 2003 but it works for XP also, just delete the "2003-" part. txtsetup.zip -
Not sure where you got this advice, but switching Win File Protection off won't allow you to delete these folders. WFP doesn't maintain them. You'd get an error message and they won't be deletable with WFP off.
-
For the curious, here is the source I used for the file, as well as the DLL itself. (Think of it as a 'fork' of Damian's work in that it works the same way but is a little different.) Long story short, I used to keep SFC turned off, until one day I wasn't thinking and installed a legacy piece of software that overwrote several of my DLLs... So now I keep it on
-
Did not look at the ini, but this is usually a result of DRIVER.CAB or SP2.CAB/SP3.CAB not being on your system (but only on CD). Off hand I don't know how to tell the system to look on the local hard drive rather than the CD, maybe someone else can chime in with how to tell Windows where to look. Maybe you can just copy the file over to the C:\WINDOWS\Driver cache\ directory... maybe Windows looks there first. Worth a try.