formtted size 30GB SSD?

I

ilkhan

[H]F Junkie
2FA
Joined
Sep 23, 2002
Messages
13,955
I'd like to try and see if my computing habits would survive in a 30GB SSD. I have plenty of HDD space as is to try it with.

In windows setup, how big of a partition would result in the same as a 30GB SSD (aka a vertex) would provide?
 
No, 32 Gb are really 30 GB.

So, OP, what are you asking?

Go to your current system drive and right clickon it and click on properties. If it says you are currently using more than 30 GB, then you will prolly not be happy with a 30 GB SSD.

Any version of Windows will install fine on a 30 GB drive. It's the stuff you need to install after that that will cause problems.

Don
 
I have plenty of HDD space as is to try it with.
Click to expand...

I'd get an old drive, partition it to 30GB, do an install, and go from there.

I'm using @ 29GB for Vista Ultimate and programs.

60GB would be the smallest OS drive I'd feel comfortable with.
 
So obviously this wouldn't be for gaming, so I tried what you suggested.
C: has 55.8 of 151GB free. 95.2GB used
but games are taking up 71.2GB (steam, EA, THQ, etc)
So non-game folders are taking up 24GB. Maybe 30GB would be OK for me.
 
That would be awfully tight. You need to give the OS a little elbow room, to download and expand stuff for install for instance. Besides, Windows installs generally grow over time.

Don
 
Assuming you are running a recent version of windows... check out the "%windir%\winsxs" directory. This is about 70% of my C: drive, you can't get rid of it, and it will continue to grow.
 
My 120G Vertex in the old firmware was 122GB formatted, it was reduced to 119GB during the new firmware to fix some problems with large files crashing the drive.

Intel still uses the old naming scheme (32, 64)
 
edit: It seems I had my info backward.

I think I'll try living with 30GB for a while, and go from there. Want to try 6.1.7106x64 anyway.
 
Last edited:
buzz
wrong answer

winsxs is the actual files, everything else hardlinks to it. that's why you can't delete it.

All of the components in the operating system are found in the WinSxS folder – in fact we call this location the component store. Each component has a unique name that includes the version, language, and processor architecture that it was built for. The WinSxS folder is the only location that the component is found on the system, all other instances of the files that you see on the system are “projected” by hard linking from the component store. Let me repeat that last point – there is only one instance (or full data copy) of each version of each file in the OS, and that instance is located in the WinSxS folder.
Click to expand...
http://blogs.technet.com/askcore/ar...and-windows-vista-and-why-is-it-so-large.aspx
http://blog.tiensivu.com/aaron/arch...in-Windows-XP,-Vista-and-Server-20032008.html

A common issue in previous versions of Windows was that users frequently suffered from DLL hell, where more than one version of the same Dynamically Linked Library (DLL) was installed on the computer. As software relies on DLLs, using the wrong version could result in non-functional applications, or worse. Windows XP solved this problem by introducing side-by-side assemblies. The technology keeps multiple versions of a DLL in the WinSxS folder and runs them on demand to the appropriate application keeping applications isolated from each other and not using common dependencies.
Click to expand...
http://en.wikipedia.org/wiki/Featur...ication_isolation_.26_side-by-side_assemblies
 
You must log in or register to reply here.
Back
Top