raskren

You install the vmware display adapter driver. Not the Intel driver. The vmware driver is installed along with the vmware tools.

Even build 4074 is a "PRE-ALPHA" build. As in, before Alpha. Rumor has it they're working on 5xxx builds now. 4xxx builds were the new Longhorn kernel, while 5xxx are the Server 2003 SP1 codebase. It is likely that Windows Whatever-It-Is-Going-To-Be-Called will not look like the current builds or concepts that we've seen. Remember what the beta builds of Whistler looked like?

Only if you consider Windows XP to be a Service Pack for Windows 2000.

What a joke. Not if you want to use the latest hardware and software. Nowadays many professional apps refuse to install on 95/98/Me and for good reason. No SMP support, SATA RAID, 512 MB RAM limit, etc. The Win 95 kernel is unstable and inefficient compared to NT. Try doing some serious desktop publishing on 98 and you'll quickly notice the poor color management systems and lack of out-of-the-box support for OpenType fonts. Microsoft scrapped the 95 kernel for good reason. If it really were "cleanest, fastest, and most stable..." Microsoft would still be marketing and selling it today. But no, everything new MS produces is built on the NT kernel which truly is the most stable, fastest, and cleanest. I could quantify this statement, but in this forum, I doubt I need to. And to the original thread starter: I have done ZERO 98 installs for friends/family. For a low end machine I always install Windows 2000 Professional simply because I don't want to hear about constant blue screens. Oh, and please grow up. The company's name is "Microsoft" not "Microshaft" or M$. Thanks.

There's an option in Control Panel>Display>Screen Saver called " On resume, display Welcome screen". Make sure that is unchecked.

That was called "tounge-in-cheek" humor. Maybe someone should close this thread.

Like this one... (sfc_os.dll, shell32.dll, themeui.dll, termserv.dll, uxtheme.dll, tcpip.sys...)

So what! Its just hacked files! Why report this dude? I post my "hacked" Windows Xp all the time Sure, I don't claim its Longhorn or Windows 2006 but its hacked just the same.

Its spelled MS not "M$", btw.

If you're not going to integrate the driver... 1.) Install to RAID array with f6 driver install 2.) Install to PATA drive with fully unattended CD Pick one out of two.

The only way to load your own textmode drivers and have the $OEM$ folders copy is to integrate your drivers into the install source. oh look:http://www.msfn.org/board/index.php?showtopic=13173&st=0

When OEMPreinstall=Yes you can't load drivers from a floppy.

The file appears to be inside a restore point so it is probably safe to delete outright.

Hi, this one has been bugging me for a while. I've got a whole mess of driver files scattered in lots of directories. I'd like to compress all of the appropriate files with makecab to end up with "file.ex_" type files. The problem is that makecab doesn't accept wildcards so makecab.exe *.* doesn't work. I'm aware of the driver compression script that someone made but these folder structures are so complex that it just makes a mess and I'd rather do it manually.

Wow, so the vast majority here are under 18? I'm 24, living in an apartment with a roomate that has absolutely no business telling me to get off of anything!

Pretty tasteless.

LMAO again.I got it from your post, smart guy. To me this says "page file usage equals ram plus page file usage" (which is wrong).

Ooops, double post.

Don't forget "up to date" doesn't mean "secure." Do you have any anti-spyware apps installed? MS Antispyware? If you're running XP SP2 check the Windows Firewall exception list for anything you don't recognize. Do you currently use any ad supported software? Finally, check msconfig for suspicious non-Microsoft services as well as suspicious startup items. P.S. The data for Add/Remove programs is in the registry. I'll see if I can dig it up.

LMAO. Ok, let's take a look. Image Name "firefox.exe"; Mem Usage (RAM)=23,092K; VM Size (Page file)=14,604K. if Page file = RAM + Page file 14,604 = 23,092 + 14,604 Eh, doesn't balance, does it? RAM + Page file usage = Commit Charge I'm not going to bother running the app you linked to. I'm pretty confident the numbers in Task Manager tell me what I need to know.

The pagefile will most likely fragment if it expands. Typically, since the pagefile does not move, the next available chunk of hard disk space is located at the end of the disk. The expanded portion of the paging file goes to this [slower] area resulting in two or more fragments. When set to automatic, the last thing you want the paging file to do when it expands is fragment. A full commit charge condition causes Windows to expand the file. By fragmenting it, you're further slowing down an already overburdened system. False and false. Windows 2000 and XP default to the %systemdrive%. I'm running Firefox, Windows Media Player 10, Microsoft Outlook, a command window, Calculator and Photoshop on a system with 512 MB of RAM and Windows XP Pro. I'm currently using about 305 MB of my 1GB paging file. Not used much? Have you looked at Task Manager lately?

Is the state "Listening" or "Time_Wait"? You probably visited a website with an ad that was hosted on ads.rediff.com. Restart the computer and run netstat again to see if ads.rediff.com still exists. If it does, or the state is "Listening" then there could be something there.

I wanted to DL and try these for the first time but it seems the site is down. Can anyone verify?

Did you bother to read what you posted?

The best defragmentation utility is the one that defragments every file on your hard disk and creates ample contiguous free space for new files. ...oh wait, they all do that. ...oh wait, the built-in Windows defrag app does that. Defragmentation utilities CAN NOT make your hard drive faster. Defrag utilities CAN NOT increase spindle speed or buffer size. Defrag utilities CAN NOT reduce latency or seek times. Benchmarking utilities are flawed by their very nature and DO NOT reproduce real world access usage. BTW, I use O&O Defrag because of its useful command line tool that I can easily set as a Scheduled Task on client machines in the middle of the night. Follow up: Don't bash someone because he uses XP's defragmenter. Not everyone wants to pay extra for a utility that only consolidates free space. That's really the only useful thing all the 3rd party tools do: consolidate free space. Fragmented files hurt performance, that's a fact. Look at the logs before and after an XP defrag. I've never seen a fragmented (unlocked) file after using it. Occasionally, the paging file or the MFT data can become fragmented which can also negativey impact performance. There's a free tool for that though. Google for pagedfrg. I added it to my Unattended CD.