operaguy opened this issue on Feb 06, 2006 ยท 21 posts
Dale B posted Mon, 06 February 2006 at 7:19 PM
Opera; Yep! PATA (Parallel ATA) really didn't exist as an acronym until Serial ATA came along. My experience is that having the OS and any needed drivers and codecs on C:, and nothing else, speeds up performance a bit, at least if it isn't a huge drive. One of the things that slows down computers over time is having the swapfile sharing the same drive with the OS install; fragmentation occurs, and you start losing performance due to the access time needed to hunt across the platters (particularly if Windows controls the swapfile size. Many times it can't simply enlarge that swap area, as active apps may be using the adjoining space, so it establishes another swap section). What you -may- want to do is build one box specifically for resource management. One small boot drive, then two large drives set to mirror, and install all your content on the primary drive of the mirror. Once things are networked, if you set that mirrored array as a network drive, you -should- be able to link the various versions of Poser to that drive (I haven't tried it, so I don't know if Poser would get into a fight with its other selves, but this would be the most efficient way to handle things. All your textures, meshes, INJ/REM files, would be in one location, so there would be consistency across all the Poser installs, and managing one runtime set is a lot easier than several. It would also insure that your pathnames stayed consistent for all the rendercondos). If you managed to get the resource server set up, you could install Poser onto the boot drive. Probably the best arrangement for the separated os & swapfile is two 20 gig HDD's on separate channels, if you can still find them. Drive size is getting insane now... You'll also probably find the smaller drives at a reasonable price in SATA nowadays. Just read the box =very= carefully. Unless the SATA drive explicitly says it supports -being- a boot drive, then it won't. It may seem to work, but you'll get a corrupted OS install....assuming it doesn't BSOD during installation. I fought with that for almost 3 months, replacing one bit of hardware at a time, as the symptoms kept shifting on me, before I caught that little blurb on a Seagate drive. My wife got a nifty Athlon 64 3000+ 939 out of the spare parts, but still.....