Jody Thornton

I would love to use Win2k, but some stubborn programmers decided to stop supporting it Real shame. I like my W2k much over my WinXP. In Win7 i feel like I'm locked in my own computer, so this OS is only for gaming computer. WinXP there and *loving* them almost like I loved W2k SP4. Sadly... modern GPU-Z, FFMPEG and few **** games need WinXP Up until I used XP x64 Edition, Windows 2000 was my all time favourite version of Windows. I do wish I could have used it longer, but it's amazing what it will even run. You could be still fairly productive on it.

I posted this over on the Vista Forums web site, but I thought you guys might be a much better source of assistance. Whenever I try to remove Internet Printing Client using Turn On/Off Windows Features OR using OCSETUP, my system errors out, likely because I have removed components with vLite. The system runs REALLY well, and the Event Log is clean (other than when I try to defeat a feature). The errors come from trying to set packages to either a staged or installed state; likely because their missing. When I used Turn On/Off Windows Features, I receive the error: An error has occurred. Not all of the features were successfully changed. Does anyone know of a good guide as to what registry components would need removal so that I could get this functionality back? The usual SFC, reinstall options are not what I'm looking for, since I wish to keep the lighter installation. I have corrected a lot of stuff with the System Update Readiness Tool, so that's been a BIG help. Thanks all.

Well I brought over the drivers for the Standard Floppy Controller, and it installed. Then it detected a phantom floppy drive. The only way to make Device Manager happy was to feed it the drivers for the Floppy Disk Drive. Mind you, the controller is disabled in the bios, there IS NO drive, and the previous installation of Vista (from the same vLited DVD) never asked for it. Nor did Windows XP x64 Edition. Device Manager is happy, but it is indeed strange.

See I did that. What I think happened is that I vLited the Floppy Controller out of the install.wim file, since I turned off the Floppy Controller in my Bios. So I'd have to go to the original DVD and load the floppy driver to install it. For now it keeps redetecting the unknown device. I'm just stunned that the floppy controller was never detected on previous OS installations.... hmmmm. I enabled the controller in the Bios, so I'll have to grab the original DVD. Thanks Jaclaz.

Is that the same as disabling in Device Manager? (Luckily, I had the XP x64 support tools on hand, which are compatible)

I read that somewhere too, but I think they dismissed that in the thread. My floppy controller is disabled in the BIOS. And it's interesting because on previous installations of XP x64, XP x86 and Vista, it was never detected. But I am now wondering if it wouldn't be a smart idea to try the standard floppy controller driver and see if that cleans things up a bit.

I was missing a driver for an Unknown Device, and the Hardware ID showed up as: ACPI\PNP0700 *PNP0700 It's parent device was the Intel 82801EB LPC Interface Controller. So I figured I was missing the Power Management Controller. I look in the drivers included with Vista and all that was on hand was the Intel 82371EB Power Management Controller. I attempted to use this driver, and there are no errors, but I really don't think that's correct. Interestingly, my last Vista installation did not exhibit this issue. I wonder if anyone who has an HP xw8200 (with ANY OS installed) can tell me what driver is used for this device (most likely the power management controller). Any assistance is GREATLY appreciated. Thanks.

OK here's the link to the themes. Whew! https://www.dropbox.com/s/z02xmt6ngt70cng/Theme%20Backups.7z?dl=0

Me too. I also have Windows Search and Indexing removed on Vista, using vLite.

My Vista screen. A bit customized with smaller basic buttons and a lighter blue basic Win7 style menu.

Please share. I need your PM. In 7-zip format, I've got it down to 5 mb.

Here a few visual styles that I used. I modified them somewhat (smaller caption buttons or start button replacement, etc). Use as you like. I may have more. (Actually, it's too big to attach. Send me a PM or if someone knows another way, that would be great.)

I think ever since XP, the OS has become LESS dependant on Internet Explorer. During the early 2000s, apps like Music Match Jukebox relied on IE6 libraries to be present, in order to run. It's not so much that Windows needs .NET Framework. But application developers have found it easier to work with, so it's here to stay. Mind you (when not in use) I don't find .NET to impact performance at all. I dunno; I used to hate Vista when it cam out, and even Windows 8. But I'll tell you, Windows 8 (when used with Classic Shell applied) really can be a stable desktop OS. It runs exceptionally well.

Yes but Windows Server 2003 updates extended XP x64 by a year (same codebase) And Windows Server 2008 "Classic" could extend Vista to 2020 because it shares the same codebase as Vista. We're not expecting Microsoft to step up at all. We just keep hoping that some person will attempt hacking the updates to make them compatible.

We also now know that YES Microsoft will push updates. I think slow ring users (business editions) will get updates later than fast ring customers (home users), but it seemes updates are forced. So much for being able to stick with a particular build of Windows 10 if you like how it works.

Hi Folks: I vLited my Vista installation back in Feb 2014. I integrated IE9 and all updates to that point. SP2 was already part of the source. And I've removed such goodies as Indexing, Remote Assistance, System Restore, Simple TCP, Terminal Services and lord know what else. It runs great and really lean. And no event log errors. Now I recently had to fix up a bunch of .NET and Windows Update issues. So I'm back to running well again. As a final step I ran The System Readiness Tool. When I look at the CheckSUR.log that it creates, I find references to files in the Component Store that appear orphaned, or else the payload/file is missing (and most of it looks like it's from the junk I removed with vLite) So here's my question: would it be fair to say that if a line in CheckSUR.log reads as: Checking Package Watchlist (f) CSI Payload File Missing 0x00000000 mshwkorr.dll amd64_microsoft-windows-t..reinkrecognition.ko_31bf3856ad364e35_6.0.6001.18000_none_600bc58be4a7864a ... that I could delete either the WinSxS folder that corrresponds with it, or the registry entry that matches it, without doing damage to the system?

I was pleasantly surprised at how well 75 renders sites. I really never thought I'd see K-Meleon rise from the dead, but I'm glad to see it has. Now just to wait for more themes, and for them to solve the icon size issue on toolbars and bookmarks (apparently, you can't change one without the other)

What features were missing on Windows Server 2008 that Vista had? (I'm also wondering if Server 2008 updates will be portable to Vista, but there's no news on that front.

By the way, the link I provided for the GAT at XIN appears to be down. One more month of updates too. I hope to get 'em. (Edit (on July 12th) It's Alive! LOL (site's back up)

All I remember is that my LSI Logic controller required a driver to be added (F5 needed to be pressed up on setup so I could provide a floppy). but both Windows Server 2003 (and it's renamed modified sibling - Windows XP x64 Edition) both included the SCSI drivers for it.

Well I ended up completely turfing the Microsoft.NET folder under Windows, after taking ownership of the entire tree. Then I restored the folder tree from the installation DVD. .NET apps all work now, and my Event log is devoid of those pesky errors. But now the services are not lited in the Services snap-in. Oh well it works now without complaint.

Well that would work, and that would be OK since the only .NET app that I use is CD Burner XP. It uses .NET 3x binaries though. Of course I wanted to try to fix it nonetheless...lol I tried SFC and even all of the cleanup tools (but the latter isn't really a vailid option, since .NET 2 and 3 are integrated with Vista). Still over the last couple of days, I tried several things that I read on the web. None of it helped. So I'm using your solution Dencorso, and disabling .NET Optimzation Services. Thanks for your help guys.

Hi Folks: Recently I began seeing some errors upon startup in Event Viewer. It shows an Event ID of 1111 and here's what the error says: .NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Service reached limit of transient errors. and a second error shows .NET Runtime Optimization Service (clr_optimization_v2.0.50727_64) - Service reached limit of transient errors. When I start both ngen services, they start and then stop almost immediately. Then the errors show again. Now when you Google this stuff, mostly the solution offered is that you need to reinstall Windows Vista, because .NET v2x and 3x are integrated with the OS. However, I can't believe that there's not a way to repair .NET by grabbing files from install.wim off the installation DVD-ROM. Besides, my system works great in most other respects. I have attempted removing about four or five recent .NET v2x updates, and reinstalling them. I figured that might re-register something. But no go.

That's right, I still have another batch of updates to await. What I plan on doing a bit down the road is moving my server to a new box. At which point, I'll just nLite an install disc of Windows Server 2003 with all of the updates built in, so it may be a moot point by then. We'll see. Thanks for the help guys!

I'm with jaclaz on this one. I tested my Vista and XP x64 installations by running simultaneously the most applications I could possibly want to run at once. I did it with two 1 gb page files (one on each drive), and without paging at all. Without paging I still had a hard time going beyond 5 gb or RAM usage. I loaded up my audio editor with dozens of wave files, opened two browser instances with about 50 tabs each, office apps with four or five docs and spreadsheets, you name it. Performance was nearly the same. I will say that my workstation still seemed to run faster without paging, but I had less free memory of course. I'd probably be "safer" with a page file, but I'll never near the limit. Apparently, paging can make meory use more efficient by placing memory address and data pointers in the page file for quick acccess. But I figure, if it places that in RAM too, all the better. And I really agree that a memory dump will only be useful to a handful of people, and I don't know any of them. .