$$
Yeah, I've started to collect stuff for mine. I'll probably start building it in the summer
Fuck Compaq
- Thread starter Matt
- Start date
$$
Yeah, I've started to collect stuff for mine. I'll probably start building it in the summer
Ender Rises
Wass sappening?
Mine has a habit of overheating. I usually put a book under it if I think it might do so.
MasterOLightning
Optimator
I had serious overheating problems for a while, where I actually had to sit the laptop on its side to keep it running. I got a replacement fan which helped. Using an aeroduster quite regularly helps.
I have a question (as I've never done this):
For my next computer, I'm going to ruin dual OS's (XP and Vista - maybe ultimate, I plan on having gobs of RAM). Now, I plan on installing both OS's on a single raptor hard-drive so as to take care of the rpm boost, but everything else (programs, various files such as jpegs, peds, mp3's etc. will be stored on a slave drive. Will I have any problems running programs between either of the OS's?
Example: If I have a photoshop CS3 installed on the secondary drive, will there be problems opening saved files in either OS? Will either OS add it's own sub-extension to the file making it OS specific? Will each OS double the program data over on the secondary drive (thus making it appear as if there are two of each program/data installed)?
I just want to know that I'm not going to be fucking myself in the ass with such a project, as it will cost a lot of time and money...
Also, rec me some of the best cases for a comp tower. I need mega cooling...
For my next computer, I'm going to ruin dual OS's (XP and Vista - maybe ultimate, I plan on having gobs of RAM). Now, I plan on installing both OS's on a single raptor hard-drive so as to take care of the rpm boost, but everything else (programs, various files such as jpegs, peds, mp3's etc. will be stored on a slave drive. Will I have any problems running programs between either of the OS's?
Example: If I have a photoshop CS3 installed on the secondary drive, will there be problems opening saved files in either OS? Will either OS add it's own sub-extension to the file making it OS specific? Will each OS double the program data over on the secondary drive (thus making it appear as if there are two of each program/data installed)?
I just want to know that I'm not going to be fucking myself in the ass with such a project, as it will cost a lot of time and money...
Also, rec me some of the best cases for a comp tower. I need mega cooling...
You shouldn't have any problems, but why would you want to do that? with sp1 vista is actually quite a decent OS now, and I can't see why you'd want XP.
as for case towers... depending on personal preference (whether you want an over the top case or not) I'd get:
thermaltake armor - awesome cases, I have one.
antec 900... not as big as the TT armor, and the cooling is slightly worse, but its still a nice case. I don't like the look personally.
antec 1200... the 900, but bigger, and it has 5 fans and slots for 2 more. its expensive, though, and has only just come out, so you might have a bit of a problem finding one. Its also meant to be noisy, and might have dust issues if the 900 is anything to go by.
I'd go for the TT armor, personally. They have quite a few in that range, so you're spoilt for choice. It has excellent cooling, its HUGE, and not too noisy either... plus it looks teh sex.
as for case towers... depending on personal preference (whether you want an over the top case or not) I'd get:
thermaltake armor - awesome cases, I have one.
antec 900... not as big as the TT armor, and the cooling is slightly worse, but its still a nice case. I don't like the look personally.
antec 1200... the 900, but bigger, and it has 5 fans and slots for 2 more. its expensive, though, and has only just come out, so you might have a bit of a problem finding one. Its also meant to be noisy, and might have dust issues if the 900 is anything to go by.
I'd go for the TT armor, personally. They have quite a few in that range, so you're spoilt for choice. It has excellent cooling, its HUGE, and not too noisy either... plus it looks teh sex.
entanglement
Member
Speaking of which, I saw a case of a person's acer notebook stopping to detect the hard disk as a bootable device after merely 2 days of him having bought it.
entanglement
Member
Partition the first drive, install the OS's one in each and use the slave drive as one big chunk formatted partition for storage. I use the exact same setup quite smoothly.
As for installing programs on the secondary drive, its safe enough.. you won't run into many glitches like that, but its rather advisable to have your 'installations' in the same partition as the system partition for rather slicker launching and closing of applications.. just get a bigger disk as the primary if you fear running out of room after your installations.
supseudonymous
&
Most programs will require that you install them in each operating system separately due to registry usage and user specific data stored within OS specific locations.
FerretallicA
HMAS Slagdestroyer
Close, but correction: HP bought out Compaq. Compaq is basically HP's 'budget line' now. As they say, you only get what you pay for.
Jean-Pierre
Son of The Bitch
supseudonymous
&
You should check out portableapps.com, portablefreeware.com, and similar sites that offer programs which aren't embedded into the operating system. You can even run them off of flash drives, portable hard drives, etc. with no problems. They're really completely fucking awesome. I loaded up my flash drive with programs to use on campus computers which don't allow you to install anything.
entanglement
Member
The U3 system on Sandisk drives is what I have for that. Unfortunately, it takes a long time to fully 'load' once the flash drive is inserted.. even if all the errands are just a small file copy operation.
supseudonymous
&
FerretallicA
HMAS Slagdestroyer
Sandboxing is the way to go. Far more flexible and powerful than 'portable apps' on a single PC with multiple OS's installed.
Already posted on page 1. David Lynch fucking rules, hahaha
Man, I have no idea how I missed that. Oh well. Still funny, and yes he does.
supseudonymous
&
Doesn't that prevent saving any program-related data permanently though? Also, doesn't a program have to be first installed into the OS before being run through the sandbox? You don't install programs directly into a sandbox right? And if you do, wouldn't you have to re-install those programs each time you dump the sandbox?
FerretallicA
HMAS Slagdestroyer
Each sandbox application has its own quirks with how it handles the process but generally speaking, any write requests (files, registry entries etc) are instead written to a proxy location. Read requests are first checked against the proxy for existing entries and if found are read from there, otherwise are read from the non-sandboxed hard drive. You can install programs into a sandbox but you don't have to. A sandbox doesn't wipe itself every time you run a program and you can run multiple programs within a given sandbox. If you want to make the data in a sandbox permanent you can 'commit' it to the host environment at any time.
You could, for example, install Outlook on your PC normally. Then run 4 or 5 different sandboxes, each containing different account details, contacts, calendar etc. When you want to get rid of one of them, flush the sandbox and it's as though that particular instance never existed. Meanwhile you can still run Outlook non-sandboxed and, within certain limits, it won't affect the sandboxed copies and vica versa.
Alternately you can install Outlook directly into a sandbox and it basically doesn't exist in the non-sandboxed environment. Once you flush the sandbox, all traces disappear.
Sandboxing is basically, for the average person's intents and purposes, a more flexible and powerful alternative to portable apps. The main advantage is that you don't need an application to be specifically written or modified to support U3/etc. The main disadvantage is that, since the apps don't realise they are being sandboxed or portable, they expect their operating environment to be the same each time and don't handle change (eg- drive letter reassignment) well.
