Lol, wellll.. Many games, bunch of mods for various Civ's, docs that were mentioned earlier, Several movies, stuff like that. >.> Could I do something if I freed up some space? I can gladly uninstall some games if so.

If you could get it down to 40/50GB's, you could Partition the 120 in half. C being partition 1 and D being partition 2. All games, mods, etc go to D and operating system to C. Once you save everything you want to D, format partition 1 with the Vista install disc and install it on Partition 1 (it won't touch partition 2). This thing having one Sata port is absurd. That said, I've seen all the crap eMachines install during recovery....you might very well never get a 'clean' install....but at least it will be on it's own partition and your saved 'stuff' will be unscathed.  

I can probably get it down to 40/50~GB. How would I go about partioning the drive into 2?

And your right, the eMachines format is bloated with crap, but I do have a REAL Vista Ultimate disc.

Excellent.

 http://articles.techrepublic.com.com/5100-10878_11-6170510.html

Thanks. If I do so, and something goes wrong, or I decide I only want 1 partition afterwards, can I merge them together again? If so, will I lose the data on "D"?

You would have to move the data to C and then expand partition 1 to full disk.

DP....sometimes I really hate these Stardock servers..........

I'll remember that. You may have saved me 3 DVD's, lol.

I really appreciate the continual help.

Well, good and bad news. I've had WB disabled the last few days..and not a single crash of any sort. Kinda lame how my favorite app. is the most harmful.

Pardon me for jumping in here, but I've also been experiencing Explorer crashes for quite some time. I was able to finally pinpoint it to a program called Alfaclock that I was using. (I just posted a question about it on the main forum board.) Every once in a rare while, WB would work fine with Alfaclock, but 9 out of 10 times, it would crash explorer and I'd have to 'end task' on Alfaclock and WB, then rerun explorer.exe again. Just wondered if you ever got everything figured out and fixed?

I experienced this problem or something similar earlier this year.

Explorer would crash if a) the taskbar was right clicked in the centre region (but not if clicked in margins defined by skin) or Drop down menus (file, edit, view etc) were clicked in explorer windows.

MSN Messenger would exit cleanly if a) It's status icon in the tray (notification area) was clicked (left or right) or Drop down menus in messenger were clicked.

Windows Media player would crash if a) the video area was left clicked, or drop down menus were clicked.

notice a trend?

All the above problems would be resolved by unloading WB.

All the above problems were also resolved by creating a new skin, not changing anything, and using that. (i.e. using WB to make xp look like xp.)

Messenger and Media player both survived drop down menus when they were excluded from skinning.

All the problems but the media player video left click were resolved in a given skin by altering the use of transparancy, paint methods, margins and intelligent shrinking for the taskbar and per pixel window margins (much trial and error). the use of UIS style window borders also fixed the menu drop problems.

From the above - problem deduced to be due to the way in which per-pixel transparancy was being handled.

I fixed it temporily by using skins which did not include any of the problematic features -(using UIS frames/modified perpixel/non transparent taskbar)- but WMP still crashed if video play was left clicked. Applet written to test overlaying two or more perpixel transparent objects also crashed if three or more were overlaid. New graphics card drivers downloaded. problem persisted. report sent to nVidea. (if it happens when not using WB, just other perpixel transparencies in windows xp, is probably graphics card or drivers fault) WB was just first symptom, owing to much transparency use.

Since then I've altered more of the system, downloaded SP3 and another set of graphics card drivers. recently rechecked the problem, and is resolved. Unsure if this is due to the new drivers, SP3, or the other bits of the user interface, OS, and assorted third party or self written things that have been added, altered or removed in mean time.

I am running a highly hacked, chainsawed and spraypainted version of windows xp Professional (32bit) SP3 on a core2quad Q6600, 4Gb RAm and an Asus 8800GTX 768 graphics card. WB is version 6.4 build 73 x86

When problem existed was running same machine with a slightly more chainsawed version of windows Xp SP2 (with significant chunks of SP3) and same version of WB.

Problem had not occured with demo version of WB, possibly earlier version late last year, when was running H'dCS'd&SP'd windows XP Professional sp1 with most SP2 elements and a couple of SP3 bits.

Advice to others i derive from this:

Step 1) unload WB. problem persists - probably not WB's fault, but I have no further help for you.

Step 2) Update to SP3 if not already using it.

Step 3) Update graphics drivers, especially for nvidea 8 series

Step 4) Check if problem persists, and if it does, tell your graphics card manufacturer, stardock and microsoft.

Step 5) Limit use of per-pixel transparency, and await a solution

Step 6) DO NOT attempt to rewrite your graphics card drivers.

Eserchie...disable nview

That would probably work too. but is working fine with current set up now. post was for anyone else experiencing this.