Content Type
Profiles
Forums
Events
Everything posted by fdv
-
I rewrote my driver integration info. Sure it's available around the 'net but I tailored it for Win 2000. http://www.vorck.com/windows/2ksp5.html#drvinteg Feel free to critique. Also, to choose a kernel / hal during boot, when you see the F6 prompt... press F5. (That's FIVE).
-
Furthermore, have a look at this picture. It is a Windows 2000 and XP TXTSETUP file side by side. Why couldn't I copy the text from the XP to the Win2k, and use XP's intelide driver? Couldn't we expand all of the device drivers 2000 uses this way?
-
This one may sound even sillier... but are you using a genuine Microsoft source? Did you use any non-MS hotifxes? Is it possible that there are non-MS files on your system that have been tampered with that disable your security settings? I know the possibility is very remote.
-
This question applies to all NT-based OS's including XP. Let me say this at the outset: I already know how to integrate drivers into TXTSETUP.INF and have Windows detect and install them automatically. In TXTSETUP, driver detection starts at the [HardwareIdsDatabase] section. Drivers that must be installed early therefore get priority by being detected right away. However... open up SYSSETUP.INF and find [DeviceInfsToInstall] You will see all of the INF files for the various devices Windows supports. I use 2000, and since it's an old OS, I comment out display.inf since 2000 would not detect any modern video card and would default to 640 x 480 anyway, and it speeds up my setup. I also comment out tape.inf and netirsir.inf since I don't use tape drives or infrared devices. But what if I were to add my own driver INF here to this section? I am sure that it would work for video drivers. But what about SATA drivers? What about ICH9 chipset drivers? Can they be installed later than devices in TXTSETUP?
-
Ok, for testing purposes, go to the screen you show in your Feb 27 2008, 09:57 PM post. Go ahead and click DENY for deleting. It really is better to leave a box unchecked, I agree, but we're testing here. See if explicitly clicking Deny works at all. If it does not work, then something is wrong on the drive or its filesystem. The only time permissions won't work is if the filesystem is not NTFS, so this is very strange.
-
I'm sure I missed this, but I'm going to ask anyway. You're on an NTFS volume, and not FAT32, right? I know, I know, but I had to ask.
-
Here you go http://www.msfn.org/board/HFSLIP-f129.html Problem 100% solved!
-
1. About wanting to keep IE -- IMO you should avoid any site that uses an ActiveX control to scan the PC; use some freee software to run locally instead. But that's just my opinion. I DO have a fileset that takes out all the crap but LEAVES IE alone. I can link to it once I find it. TommyP tested it out a while back and I think he approved of it (he runs Maxthon) so that might help you. Once you use it, put UNIATA in the FDVFILES folder. Then open LAYOUT and TXTSETUP and find ;UNIATA and delete the semicolons. Also, in TXTSETUP, you will find a new [uniata] section I created. Combine this section with the [HardwareIdsDatabase] section. (by cutting and pasting for example). 2. About Multiproc... Open TXTSETUP.INF and find [specialFiles] Multiprocessor = ntkrnlmp.exe,2,ntoskrnl.exe Uniprocessor = ntoskrnl.exe,2 MPKrnlPa = ntkrpamp.exe,2,ntkrnlpa.exe UPKrnlPa = ntkrnlpa.exe,2 mouseclass = mouclass.sys,4 keyboardclass = kbdclass.sys,4 You will see that it's always the same file name. The trick is to force Windows to load the MP kernel every time. So, you could try an inelegant hack like this: [specialFiles] Multiprocessor = ntkrnlmp.exe,2,ntoskrnl.exe Uniprocessor = ntkrnlmp.exe,2,ntoskrnl.exe MPKrnlPa = ntkrpamp.exe,2,ntkrnlpa.exe UPKrnlPa = ntkrpamp.exe,2,ntkrnlpa.exe mouseclass = mouclass.sys,4 keyboardclass = kbdclass.sys,4 You will make similar changes in sections like [Computer] and [hal]. Change all UNIprocessor lines to whatever the multiprocessor lines day. Finally, look under [DeviceInfsToInstall]. See hal.inf? You guessed it... go to i386, type 'expand -r hal.in_' and open the expanded hal.inf and make what changes you deem necessary. Bonus tip for everyone reading because it's relevant: see display.inf under [DeviceInfsToInstall]? If you have a modern video card made after Windows 2000 came out, why bother having it try to detect it during setup if it won't find it, and will default to 640 x 480 anyway? Comment display.inf out here, speed up the detecting devices portion of the setup process, and have your video drivers on hand when the installation is done. Same with fdc.inf and flpydisk.inf, if you don't have a floppy drive, comment them out. tape.inf, same thing. etc etc. I hope this makes sense. If not, I suppose I could elaborate. EDIT: Get a version of my fileset that leaves IE alone (recommend using IE6).
-
These are referenced in DRVINDEX.INF DRVINDEX.INF is referenced in WINNT32A.DLL WINNT32A.DLL is referenced in WINNT32.EXE WINNT32.EXE is used for floppy installs or installs run on Win32 environment such as upgrading Win95, 98, or NT4. (Right?) If I never install via floppy, would anything in the OS even miss these CAB files? i386 already has all of the files in the CABs, and if the OS needs a driver, wouldn't it just ask me for the CD if it didn't find either CAB in WINNT\DRIVERCACHE\I386?
-
Hey folks, I keep all of my HFSLIP info in one master folder. I sometimes want to make an IE6 configuration, sometimes FDVFILESET, sometimes I want to have no DirectX9 for testing purposes, etc etc etc etc etc etc. Anyway, if I want no DirectX, I rename HFCABS to HFCABS-NO and create a new empty HFCABS. If I want to test just ONE hotfix, I rename HF to HF-NO and make a new HF with just the one file. I just ran HFSLIP and I got all sorts of bizarre problems. It tried to make SOURCESS a file, not a directory. It said it could not access files it parses like TXTSETUP (obviously) because somehow it made SOURCESS a blank, zero byte file. This used to work fine before I started renaming my folders. I just ran again after actually moving these 'do not use' folders... So I answered my own question. I guess the key here is that if you want to run different configs from time to time, you need to proeceed the folder with a lot of XXXXX's.
-
Holy carp I write some weird stuff sometimes. Anyway here some 10 years later is the fileset for Windows 2000 Server. It's a little different than the 2k Pro fileset but it accomplishes the same thing. It does not install scanner support nor codec support. Because hey, it's a Server, why would it. Unnecessary rant: Server products run so little software that it pi**es me off. Simple stuff like Partition Magic or Raxco Perfect Disk can't install or run because they want you to buy more expensive versions. Just had to say that. BTW why is everyone going Ga Ga Ga Ga over Server 2008? I just picked up the Dead Can Dance Selections from North America Tour and it's amazing, WAY more amazing than Server 2008. I got to play with it (and I see it has a core install too) and I was underwhelmed. Give me a flippin' break. Give me the new features with NT 4's low-system-demand interface. I mean, it's a server, for crying out loud!! Most people will run it without a monitor!
-
Get the Win2000 hotfixes here. Forget Microsoft, you're never going to get much worthwhile trying to find anything on their website.
-
Wait, what? What did I miss? See here step 9 If you view README and then look into TXTSETUP you will see the areas all set for putting UNIATA in place. (You must DL the binary and put it in FDVFILES and modify TXTSETUP and LAYOUT).
-
My apologies if this is already known. All of those files in your SYSTEM (not system32) directory? They can be deleted. I didn't know this until recently when I was experimenting with NT 4. In fact this directory doesn't even need to exist. Open TXTSETUP.INF Find [Files.UpgradeWin31] Every file listed under this section can be deleted In the main [sourceDisksFiles] section, all files with a ,5, (that's a comma five comma) should be removed because they are assigned to directory #5, the SYSTEM directory. For example, in Windows 2000, that would be the following two useless files: setup16.inf = 1,,,,,,,5,3,2,setup.inf stdole.tlb = 1,,,,,,,5,0,0 I also found, but see Gosh has beat me to it, that commenting out drivers under [sCSI.Load] can make setup appreciably faster. Use cautiously however since VMWare "tells" the OS that certain devices are present that really aren't. For example, you could comment out the cpqarry2 = cpqarry2.sys,4 line because chances are you're never even going to find a Compaq computer that still has the custom Compaq SCSI Array, which was hardware included in Compaq servers a long, long time ago.
-
Thats what I get for not mentioning this to the HFSLIP devs Yeah, after a gazillion installs I realized that SFC is really a good idea, not a bad one. In addition, it save some time at installation in the Pentium III era. Now, though, it's worth the extra 5 seconds. Sorry about the lack of mention! (BTW since I edit LAYOUT as well as TXTSETUP, and since I comment out some device drivers in TXTSETUP, Windows with my fileset installs faster than an nLited install. Not that that's a big deal since it only happens once, after all.)
-
I don't have that much to add other than I run hacked up OS's in VMware workstation and on a dual core Pentium, I can run several OS's at the same time with no system slowdown. I use 2Gb RAM. I can't run simultaneous VM's on my Pentium 4 without the system slowing to a near-stop. So, if you have running several machines at the same time in mind, I'd say, go for it, given you're running at least a Core 2 Duo.
-
If you ask Bearwindows I'll bet he'll have a solution. The guy knows NT4 cold. He pops in at MSFN now and then but you'll probably get better results just emailing him.
-
I agree with the implied premise that things would run far faster. Following this aside... Look at Windows Server 2008. It unquestionably has a lot of components that are necessary or have become necessary. I did not do a minimal Core install (for those who don't know, Server 2008 has a Core install mode where no GUI is installed). The message MS is sending is that the GUI is responsible for a lot of overhead. Down on the bottom row, that's NT Server. I found out, accidentally, when installing NT that if EXPLORER.EXE (not IE, but the actual system file) does not get installed (in my case the file was not found at all during copy, it's a long story) the desktop will still appear, but you can't drag and drop or manipulate any desktop objects. Commit is the same without EXPLORER.EXE on NT4. The point of all of this is that I wonder what tragedy took place between then and now that Server 2008 can't have a very simple, lightweight GUI. It's either all or nothing, and that's unfortunate.
-
OS2fan - OS/2 shots would be great but I think I only need Warp 4 plus fixpack 15 or higher, and eComstation would be great. I can't get NT 351 to work in a virtual PC at all. I just don't understand but that would be appreciated too. Cluberti... I get what you're saying now with the added explanation. These are a pain to build, is there no little applet from anyone that shows the correct info? Or do I have to load the management console and build this metric and do the math? Please tell me someone simplified this with a simple 32 bit binary...
-
In perfmon (start > run > perfmon), you can add the "Working Set" counter under the "Process" object, and select the "_Total" instance. Then, add the "Cache Bytes", "Pool Nonpaged Bytes", and "Available Bytes" counters under the "Memory" object. How far off is commit? This would be quite an undertaking to redo all of this. Is my approach just totally wrong? Is there no freeware app to 'shortcut' the process you outline above? I'm surprised it takes this much jiggering to get an accurate accounting of RAM usage. I'm surprised Winternals/MS never made an applet. Edit: 64.17.159.209 will always get you there, Tain!
-
Hi folks, I wanted to show the world how much memory can be saved without IE, so I created this: http://www.vorck.com/windows/memory.html It turns out, about 20megs of commit. In the grand scheme, with modern machines, that doesn't really make much difference. Dual and Quad core Pentiums are dropping in price. Memory is cheap. You can have a nice machine, really fast, in the $500-$900 range (and that includes building a Xeon-based server with a high-end PCI-X motherboard). So I changed the focus of the page in order to show the memory of all Win32 based operating systems. (Mac OS X and Linux would be hard to compare since they use memory so much differently -- for example, Linux grabs all available and allocates it as necessary.) I think it's very telling that we've gone from 60mb with Windows 2000 to 88mb in XP to 260mb in 2008 Server. I need a new screenshot for Vista (I used something called a "Gamer's Edition") and I need an NT 3.51 SP5. BTW, you cannot even begin to imagine what kind of nightmare it was to get OS/2 running. If you can make me a Vista SP1 or an NT 3.51 SP5 screenshot, and duplicate the arrangement I have where it shows the version in the upper right corner and the available memory in the Task manager (careful not to cut the bottom off) please send me a screenshot. Please, zip or rar it, and make it a lossless image like PSD, TIF, or BMP, not JPG or GIF. I'll pick the one that fits best with the other screenshots. BTW the reason I posted this topic here is because I think the memory savings angle is most interesting to this crowd of tweakers... Thanks
-
When you get this, it means that Virtual Box, or VMWare, or MS Virtual PC, was faking out the OS by using one of the drivers you got rid of. Comment fewer of them out. And IMHO you ought to be doing this in your original source file.
-
Actually, NT4 will see a valid NTFS volume, whether v4 or v5, and offer to let you install on it leaving it "unchanged." It only creates FAT16 and then converts the FAT to NTFS on new installs onto unformatted media. I do agree that preformatting with Partition Magic or Paragon. There's SwissKnife Tools which is freeware which works also. The best approach is to build a PE and do it that way IMO. About the defrag: I looked at the other forum post. It's interesting to note that the author talks about the defrag API maybe being in NT4, which it definitely is. I have recently been working with MS VC++ and the Win32 SDK and any software you write these days is a big question mark as far as NT is concerned, because you can download the Vista/Server 2008 SDK and only the XP and 2003 SDKs (they are separate) if you try really hard to find them (MS hides them, and will soon drop them -- get them while you can. They are free.) Anyway, my point is that when compiling Windows software in the future, it's going to be harder to get stuff to run on NT4 because MS will simply stop offering the tools that would allow you to do it. The same's going to happen for Win2k and XP, I am sure, but I have not looked at the new Win32 SDK, so that's only my guess. Edit: I tried a beta of Firefox 3 on NT4 and it refused to install. Not that it matters but I am very curious and plan to examine the FF3 source to determine if this limitation is fake or if FF relies on some APIs not present in NT4. Somehow I doubt it's real. In related news, I have been playing with the source for FF 2.0.0.12 to compile the mythical ActiveX control, and surprise surprise!! The Mozilla Build Environment 1.2 is FULL of (poorly documented) bugs!
-
RIS? No. You're running Pro, so RIS didn't even make it onto your machine anyway. I have Pro and Server, and to avoid this sort of thing, I manually slipstreamed all 3 or 4 hotfixes into my Server's i386 directory so I could keep Pro and Server in one HFSLIP directory.
-
This might not be HFSLIP's problem. Give this hotfix a try. I got this error myself and the hotfix above solved it.