fdv

Actually Acheron, we're ... being serious. We know that the RyanVM has been adopted and is being worked on by a new volunteer but the dilemma is that MSFN -- and we -- are all about official MS binaries. There's nothing wrong with using an Update Pack but we do want to maintain a standard XP list. Tom has 2000 covered. I have 2003 covered. We really do need a volunteer to maintain an XP list for us. Using Tom's XP list will help someone get up to speed very quickly -- so it won't be too hard to take the work over. I will host it at Vorck.com. This is an open invite to whomever will have the time. We don't mean to "beat up on Acheron"

Without IE, you'll have no add/remove control panel. You can grab a version from the ReactOS distribution. You want APPWIZ.CPL Or my fileset.

Cleaned out file installs do work but I have to say "sometimes" because depending on the file, you'll get a blank screen with only a mouse on first boot. It's been a loooong time since I tried and I don't remember which ones, sorry. Cache folders, several ways. In my fileset depending on the phase of the moon WIndows will just let you delete them. Or you can deny system permissions (that is to say, deny the system permission to read or write to them) and of course booting up with a PE disk and deleting them works too.

1. Not sure. Try it. You could point to SYSTEM instead of Z:, and that would also get by reg cleaners. 2. It does disable SFC completely. In a live system. 3. Second part: this applies to LAYOUT, yes. I personally did it ALSO to TXTSETUP. 4. First time setup only. 5. A live system, no, because Windows only uses LAYOUT one time in its life: during setup. 6. Yes, it is totally independent from SFC. 7. A finished nLited folder can indeed be both pre- and post-processed. Tip: did you know that TXTSETUP and LAYOUT can use the SAME file list? After you have run nLite, you will see that the file list under [sourceDisksFiles] in TXTSETUP is changed. You can copy this entire list and paste it right over the same list in LAYOUT. I will say this differently: Windows copies files two times during setup. Once with LAYOUT and once with TXTSETUP. nLite only changes TXTSETUP. If you put the same [sourceDisksFiles] list in both places, setup will go much faster because LAYOUT will not bother copying files to the disk that TXTSETUP won't even use. 8. Windows 2000 and XP are the ones I know of. Never tried it in NT4.

Hi all, I don't think I posted this here and really, it does belong here. I discovered this accidentally in Windows 2000. If you want WFP shut off, just specify invalid paths in the registry, like so: HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","SFCDllCacheDir",,"z:" HKLM,"SOFTWARE\Policies\Microsoft\Windows NT\Windows File Protection","SFCDllCacheDir",,"z:" Make your own INF file, etc etc etc. If you inset this into a HIVE file*, it will work at boot time. I wish UNC paths could be used, but MS says they don't work (and they don't, I've tried) *You must do the search-and-replace ,_x, to ,, (that's replace comma underscore ecks comma with comma comma) in LAYOUT.INF and save it, so that Windows doesn't throw an error... the _x tells Windows setup to check the filesize against the filesize number in layout. If you just remove the _x from the HIVE lines, you have still changed the size of layout itself, so you'd have to change that line too, so just replace every ,_x, with ,, and save yourself the work.

The HIVE entries are entered linearly. Microsoft wrote them out of order so that in effect the registry is populated non-linearly. (Does that make sense?) So, not that it really matters, in other words, when Windows executes a HIVE file the entries in the hive file are entered into the registry as they appear in the hive file, but MS wrote the hive files in a messy way). ANYWAY! Back on track with your question! You can add this key of yours to any HIVE file that has entries beginning with HKLM. That would be either HIVESFT.INF or HIVESYS.INF. Your choice. Add your line to the top, bottom, or middle, it doesn't matter at all. (Believe me, I have VERY HEAVILY edited HIVE files! I put all of my tweaks into them.) You cannot simply edit a HIVE file without removing it's _X in LAYOUT however.* *I have typed how to do this 300 bajillion trillion times on this board and of course now I can't find any links to my explanation. But perhaps you don't need a lot of text, so here it is: the secret of modifying the LAYOUT file. True black magic. Something not even nLite does, who knows why. Open LAYOUT and do an edit/replace: ,_x, to ,, (That's comma underscore ecks comma replaced with comma comma) Save and done. The _x simply tells Windows "check the file size and if it doesn't match, throw an error." (Why people treated this like the biggest mystery of all time still baffles me). HIVESFT is a nice place to put corrections, by the way. You will find timezone data in this file. I have deleted all of mine and replaced it with correct 2009 timezone data. Incredibly easy to do. Just export your current TZ data and convert it to INF format. For example: HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Alaskan Standard Time","Display",,"(GMT-09:00) Alaska" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Alaskan Standard Time","Dlt",,"Alaskan Daylight Time" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Alaskan Standard Time","Std",,"Alaskan Standard Time" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Alaskan Standard Time","MapID",,"30,31" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Alaskan Standard Time","Index",0x00010001,03,00,00,00 HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Alaskan Standard Time","TZI",1,1c,02,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0b,00,00,00,01,00,02,00,00,00,00,00,00,00,00,00,03, 00,00,00,02,00,02,00,00,00,00,00,00,00 HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Alaskan Standard Time\Dynamic DST","2006",1,1c,02,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0a,00,00,00,05,00,02,00,00,00,00,00,00,00,00,00,04, 00,00,00,01,00,02,00,00,00,00,00,00,00 HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Alaskan Standard Time\Dynamic DST","2007",1,1c,02,00,00,00,00,00,00,c4,ff,ff,ff,00,00,0b,00,00,00,01,00,02,00,00,00,00,00,00,00,00,00,03, 00,00,00,02,00,02,00,00,00,00,00,00,00 HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\Alaskan Standard Time\Dynamic DST","FirstEntry",0x00010001,d6,07,00,00 And yep, it works perfectly. If you want my timezone INF to put in, just PM me. I won't attach it here since you didn't explicitly ask for it so it would kind of be off topic. Happy editing!

Not a bad idea. Can you ship me all the code? I'll do some needed revisions as well such as linking the new binary and other crucial things TommyP wanted to get done.

Drink shoots out nose LOL Only you, tain, only you

MartinH is quite right, you're more immune to MSHTML exploits, but you're not 100%, and you cannot be careless or stupid. And I was stupid -- here's the story. Part 1: I had recently re-installed my system and had no malware software on it. I had a USB key from a friend that I plugged in (not that it matters but he'd said it was "acting weird" so I told him I'd take a look and just reformat it). Bam! Conficker. Don't let anyone tell you that just having autorun off solves your problems. I didn't know I had it right away, of course. But wait, it gets better. I was also looking around for some software that allows Win2k to boot from CD. It exists but the parent company was sold. I don't mind saying that I was scouting for the demo version of the software on some seedy websites since the legit site was loooong gone. I used links from forums, from the wayback machine (internet archive) etc and didn't really use Google, so I would not have seen any malware warnings. I was using Firefox 2.0.x and visited a poisoned site; I got hit with a Javascript iframe exploit. That's when the computer really started to go to hell. I know Conficker did more damage as it is an FTP password capturerer and the next thing you know, vorck.com has a bunch of new code in it -- iframe crap. I don't know if the second iframe trick got into Firefox 2, but I do know that Conficker REALLY screwed me up -- I should have made a malware install right away. BUT WAIT! THERE'S MORE! Yeah... I upgraded a hard drive to back up everything to one place and scan it with about 10 different malware and antivirus scanners on a PE disk (Ultimate Boot CD 4 Windows). Well, it picks up 590 files (literally -- not joking). So I go about rebuilding what I had from other backups (ultimately, nothing is lost, but you know how much it sucks to have to rebuild what was on a volume by having to get data from 50 other places, from CDs, 20 odd hard drives all mixed from SATA to IDE to SCSI, USB drives, etc). So I get it all built and restored, in ONE place. All my data back, virus free. And today that Seagate drive failed. ARRRRRGGGGGHHHHHHHHHHHHH Anyway, like I said, nothing at all is lost, but I'm not out of the woods yet because I have to collate everything all over again from a LOT of the same old sources. Old unlabelled CDs, a stack of aforementioned hard drives, etc etc.

Mim0, PM Tom and he'll make the code change and then I upload it.

Have you tried KB835221? Worth a shot

Might be an opportunity to try this: http://www.msfn.org/board/index.php?showtopic=135082 Non-DLL method of shutting WFP off

So I assume the problem was solved? Sorry -- yes, it was, thanks

July 31, 2009 In case you all had the vorck.com bookmarked, I changed the domain due to code injection. I think it's probably the hosting company's weakness. See the first post in the thread for the new links. It's temporary until I can get this sorted out.

Thanks GH Here are three things to do to solve this intermittent problem: 1. Change the restrictanonymous value as in GH's link 2. Launch secpol.msc, go to Security Settings, Security Options, Network Access: Sharing and Security Model for local accounts and change to "classic" 3. Don't access a server from 2 different machines with the same set of credentials (think about it: when you're installing software on a few machines, you might login as admin from all three at different times to access a shared folder with the program you're installing). fdv

A botched hotfix or a virus can do this. This simply should not occur. BTW, I just dealt with a virus that not only corrupted my Win2k directory (and changed file dates back so it was not easy to see) it also corrupted 90% of the binaries in my HF folder.

Thanks for the alerts, guys. I went into the site and removed a bunch of IFrame triggers. I must have had a Trojan that sent my FTP credentials to someone who had some fun at my expense. Oddly, this has only happened to me at IX Web. Honestly I am not sure if THEY get hacked and then I visit and get a Trojan, or if I get the Trojan first. I'm sure it's me. Hard to tell after it's happened a few times and I seemed to have a clean system. Anyway, I have requested a site review from Google and we'll go from there. Thanks again for this alert, guys.

The topic descriptions says it all. One of the reasons I never wanted to move to XP was because -- randomly -- an XP workstation will fail to connect to other Windows computers. 2000, XP, 2003, whatever. Hardware irrelevant. Driver irrelevant. Network adapter irrelevant. I played with XP SP2 a while back. I noticed that the same problem persisted. In Windows 2000, you go to Network Neighborhood, click on other machines, get a password dialog, enter credentials, and you're in. SP2 still hadn't solved XP's intermittent "you might not have permission to use this network resource" error message. So I stuck with Win2k. Now I need to upgrade a machine to XP to run some Adobe software. It's SP3. It's a different machine. Different processor, NIC, drivers, the whole deal since that old machine I'd tried out with SP0. I have no doubt most here will know exactly what I'm talking about. Bottom line, despite supplying correct credentials, XP simply Will. Not. Connect. to some computers sometimes, will connect to all of them sometimes, will connect to none of them sometimes. How do I circumvent this?

All are expanded into \WORK, and dupes are eliminated (or kept) via individual file date stamp. So, if MS has dates on the files in the KB .EXE right, HFSLIP will always get it right. There are a few KB's that have wrongly dated files, and HFSLIP is "aware" of these exceptions and oddities.

Your own risk, no production systems please, comes with no warranty and no support from us, etc etc. This forum really isn't "for" this software, it was a one-off made as kind of a technical challenge. We didn't intend for anyone to use it outside of a core group of about 10 of us fiddling with NT. It's got some HFSLIP code but don't expect us to offer help since it wasn't intended for wide release. So -- hobbyists only, please. There is other slipstreaming software for NT out there too, but this one overcomes several key issues that others miss. (For example, though I forget the name, there is a SP6a driver file that has the same name as an NT system file. This program is "aware" of this and streams correctly. Others don't.) So, this will create a working NT, but I encourage switching to Win2000 at the very least. Many bugs and exploits cropped up -after- support for NT was discontinued.

If you are extremely detail oriented, you can follow this process I wrote for Win 2000 for manual integration. It's dead easy if the Windows installation process makes sense to you. If you are unfamiliar with how Windows loads device drivers at install time, though, it's probably not for you. Also, dual booting XP and Linux is going to cost you a bit of effort, just so you know. Neither installer is "aware" of the other, so although it is do-able, it is not an automatic process. (I'm guessing you probably knew this)

Do I understand you right? You're creating a full slipstream using HFSLIP, installing that full slipstream, then going into the virtual PC, and RE-downloading all of the patches a second time? If yes, then you don't need to do it twice(?). Just put the MS-issued patches in HF. As TommyP revises his XP list (see stickied thread), delete the obsolete fixes he lists, and download each month's new ones every month. Sorry if I'm not getting what you're saying.

Bugs so far: - put fltmgr.sys in the 'system32/drivers' directory instead of just the system32 directory - free-av says "rollup must be installed" but it -is- so I'll have a look into what it thinks it wants at some point

1. Edit SETUPAPI.DLL http://www.vorck.com/windows/edit-setupapi.html 2. Edit SYSOC.INF by commenting out: netfx=netfxocm.dll,UrtOcmProc,netfxocm.inf,,7

You might be missing the needed files in HFTOOLS. The files you need are at a minimum mkisofs.exe and boot.bin, a 2000 boot sector. Not supported That's why the missing files. I'd have to gut the DOSNET file and I never wanted to tackle a character mode setup. CD booting is the only supported method. You'll want to smack me when I tell you: it's simply included wallpaper. Sorry you went looking Retry with an ISO of course, as noted above, and you'll be okay, but normally this is a topic for the HFSLIP forum, and they'd ask you to post HFSLIP.LOG. But this happens to be an easy fix. I wouldn't be surprised if this thread got moved, but I can also see its relevance here in this forum too.