Keris

If her copy of Pro Tools is a version tied to hardware (like the M-Powered versions) then no, it will not work in any 64-bit Windows. It has to do with the way Digidesign programmed their hardware communication (ie, very poorly); it seems they're "working" on it, but I wouldn't hold my breath. I'm pretty sure the dongled versions of other [now] Avid software has the same issue. (All my Pro Tools and various Avid video editor experience is with Macs, and even there certain versions will outright refuse to run on certain OS revisions.)Otherwise, baring bad programming practices, anything that runs on Windows 7 32-bit will run on Windows 7 64-bit via WOW64; unless the program goes out of it's way, it can't even tell it's not running on a regular 32-bit OS.

Well, I've found that Windows Live Photo Gallery is a rather good thumbnail maker in this case. Just add whatever directories you want thumbnails of to the library and just kick back and let it work. And, yes, $30 for thumbnails is moronic at best. If more than Windows and a handful of image viewers used the WIC codecs, I could see some value here.

Did your laptop come with an actual Vista OS DVD? If so, it would just be easier to do a clean install from it. Just use ABR to backup the OEM activation before you format. This is a far easier way to remove the huge pile of crap that OEMs slather on. If the laptop didn't come with a Vista DVD, then this would be one of the only times I would suggest searching the internet for a Vista SP1 disc.

I thought I was the only person who cared about that feature, considering how little airtime its removal seems to be getting ...

Well, my own anecdotal evidence shows that burning at max speed on good media yields error-less burns. How do I know they don't have errors? Because when I first open a cake, I leave data verification on for a few burns. It's been a long, long time since I've seen new media in modern drives that fail to burn correctly at max speed.

Another thing to note is the vast amount of extensions to Explorer. If Explorer suddenly went .net, all those extensions would be useless. Microsoft could make a shim that would load the old bits, but that's a app compatibility minefield nightmare. Another concern is that, until .net 4 comes out of beta, there is no way for a .net program to load more than one version of the subsystem. This only matters when you realize that, like programs that lock themselves down to certain Windows versions that are known to work, there are many .net apps that require 1.0, 1.1, or such. It's not like it cannot be done. But it's also not something that's just going to appear without all the groundwork laid out and fully tested to hell and back. While is may seem hypocritical of Microsoft to make WPF, pimp it all over, and then not use it any of their big programs, it's more of a problem of migrating and testing than anything else. The upcoming version of Visual Studio is to have a WPF powered interface, multiple major version after the technology was released. When will we see it in Office or Windows itself? Not in Windows 7 of Office 14. Maybe the versions after. And it's not like Apple is somehow immune to this themselves. It took three versions of OS X before GPU acceleration of the GUI became functional and default. And Apple still have many large programs running on the Carbon API, the API they have been trying to downplay for ages in preference of Cocoa.

Updating from various Windows 7 builds is fully possible and rather painless (what I've done since I got the PDC x64 build). It will probably leave some small bits of beta junk around, but is easier to do than reinstalling everything (curse Adobe and their insane installer). Moving from Vista to 7 should be pretty easy too, due to them being rather close in design. I'd not upgrade from XP, if only due to the minefield of incompatible drivers and such.

Well, due to the magic of WIM image files, you COULD get the original files off the old Vista disc. You would just need to be willing to put in the time and effort to learn how to mount WIM images. I know all the tools are in the WAIK pack, but these tools will make life easier. Once you get the image mounted, the drivers should be hiding out in Windows\system32\DriverStore

Libraries are amazingly cool. For a long time now, I've had my music and movies on my file server. Now, I could always change the shell paths to point there, but that also allows whatever program that decides to take a dump into those folders the directions to do it where I can see it. Now, I can add my things to the library, and just remove the default ones; programs happily dump into the default folders, but now I don't have to see and deal with Adobe, Autodesk, and whatever other folders that respawn if I try to delete them. It's very, very cool. The new taskbar is also rather nice. Mixing Quicklaunch with regular programs seems at first to be messy, but it works in practice rather well. Aero Peak is very handy, because thumbnails aren't enough 90% of the time. I have yet to see the power that Jump Lists portend to have, but at least they make for handy MRU lists for now. My only wish would be that Microsoft allow more than "large" and "small" size icons. Large is a bit much and small is way too small for icon-only use. Overall, the little tweaks and improvements are very nice. There's still a lot of stuff I'd like to see fixed up, but it's unlikely to happen (little snafus in UI interaction, mainly due to the very bolted on approach of UAC). I'd make this my main desktop OS if it wasn't for the hangups of certain programs, Live Mesh being #1 and the broken text rendering in Word 2007 being #2. Oh, and the fact that ATI is being lazy about OpenGL in x64 again.

I haven't tested AntiVir or AVG, but Avast installs and functions without a hitch. Doesn't even complain about the Windows version being wrong or unknown (unlike, say, Adobe CS4).

AllSnap can do this, and it doesn't need anything extra held down to snap.

I would suggest giving madFlac a spin. Works 100% fine for me.

Actually, even the built-in Admin account doesn't have write access to most of the important system files. By default, much of Vista is set up to only allow the TrustedInstaller SID full control. Thus you would still need to take ownership of said files and then grant yourself Full Control permissions. To get things to act just like XP does, copy the code below into a batch file and run it. takeown /F C:\Windows /A /R /D Y icacls C:\Windows /grant Administrators:F /T /C /L takeown /F "C:\Program Files" /A /R /D Y icacls "C:\Program Files" /grant Administrators:F /T /C /L Of course, doing so will negate any security benefits that locking down such files gives you, so do so at your own folly.

I can confirm that you don't need any of the Tablet PC parts for a Wacom to function properly. Just install the drivers and all works just fine. It's how I run my desktop at the moment.

There's always UltraMon, which has more features than most need (for a price, though). But, really now, Windows itself has pretty decent multi monitor support these days; it can't do some things (like span two monitors while cloning one of them onto a third), but if all you want is a discrete picture on each or perfect cloning, just use what the OS gives you.

You can still DL 4.09 from the Daemon Tools page. No clue if this version is now infested with anything beyond the search bar. As for the Pro version itself, the only thing it seems to have over the regular version is more copy protection emulation for games. Oh, and 32 emulated SCSI drives, which is complete overkill (and half of which can't be mapped to driver letters anyways). And emulated IDE drives "someday soon, we promise!" As a side note, the page wistfully does not tell you the cost. You have to register to follow the purchase link. And since I have no desire to actually purchase it, I don't see any need to go through the rigmarole to register just to satisfy my curiosity.

Drivers for the old FireGL cards in Windows XP can be found here. ATI/AMD doesn't list any drivers for FireGL cards on Windows 98 at all (a Google search pops up this, which might work). There also aren't any Vista drivers for FireGL cards of any type yet (you can force one to use the Radeon drivers if you want).

Some of those shops toss in some cheap piece of "hardware" like a molex Y adapter to try to cover the hardware purchase requirement. Technically doesn't cover it, but at least they try to cover their behinds.

My suggestion is to just delete all the folders inside System Volume Information and then just make a new Restore Point in Vista. Another thing you can do to clean up old remnants from the XP install is to go into Recycler and remove everything there (just make sure there'e nothing in the Recylce Bin you want ). This is what I have to do when I reformat my system; I only format the drive with Windows on it, so the partitions that have my data, programs, and whatnot stay, old recycle bins and all. As for the System Volume Information folder, yes, it's important to things, so don't delete it from a Live CD or anything like that. It's used by some things related to the NTFS file system.

Yeah, it was US-only, mainly due to gift tax laws and such. And it was mentioned in the forums here back when it first started a couple months back (you could probably dredge up the thread if you search for it). They "sold out" pretty fast, though. Within a week if I remember correctly.

Mine was in my mailbox today (might have been there for a day or two, I don't check my mail every day). Three cheers for free stuff!

Well, given your really low system restrictions, I don't really think there's any program that fits. But, if you're just looking for something that does 3D and is pretty simple, you can check out either Google SketchUp or gmax (which Autodesk has stopped supporting, but still has a a decent community around it). Both are free and might fill your needs.

It would be nice if you'd listed what you had used that didn't work for you so that people don't recommend things you've already tried. But, even so, I'll take a stab at this. Since you say you're a poor high school student, I'll point you to the freeware Undelete Plus. I've used it a few times, and it does a good job so long as things aren't really messed up. Personally I prefer using R-Studio as it's not failed me once (even when Partition Magic hosed a whole drive, it still found everything), but it costs a decent chunk of change; worth it in my opinion, but when you don't have the money, you don't have it.

If I had to choose just one place to put a Pagefile in that situation, it'd be on the RAID 0. If you have the array formated as a single partition, then it's easy; just plop in on that partition and go. If you break it up, such as C: for Windows, D: for Programs, and so on, then stick it on the partition closest to the middle of the drives. This will allow it to be reached fastest from anywhere. But since you can have as many Pagefiles as you have partitions, you can stick another one on the second drive if you wish. Of course, all this piddling about is really pretty pointless. Only in extreme situations will changing the Pagefile positioning give appreciable performance increases. Yes, moving the Pagefile off a clogged and fragmented 5400 RPM drive made last century to a dedicated four disk 15k RPM RAID 0 array will show noticeable improvements when RAM runs out, but more RAM will help in a much larger way. And be cheaper than that super disk array too. However, don't take this to mean the Pagefile only mattering when RAM is filled, thus you should just not use one if you have a lot of RAM. Windows NT is always using the Pagefile to move things that aren't being used at the moment but need to be kept in memory out of RAM so that running programs have access to more high-speed memory space. Pretty much just let Windows do it's thing. Unless you regularly use programs that have stupidly huge working sets that fill all your RAM and then some, there isn't much of reason to worry about the Pagefile. It's there, Windows will use it when needed, and you don't need to worry about it. If you must try to wring out every bit of performance you can from those occasions when RAM is full and you still need more memory space for the program at hand, there's something you can do. Set the small size to something semi-big (like 1-2GB) and then run a Pagefile defrag. You should then avoid the only major performance problem of a Pagefile: fragmentation. Usually Windows sets the small size pretty big on its own, though, so all you'd need to do is just run the defrag and be on your way.

exactly! all it needs is some good flash developers/designers to put some time and effort into it, and this could really take off! Sounds like my sentiments about it when I first ran across it nearly two years ago. It hasn't come much farther since. While the idea is really cool, the problem really is that it's based on Flash. Since there's no cheap/free tools to author Flash material (that I'm aware of), there's a rather high barrier to entry for creating material. Not to mention that some of the long-ask for features (like user icons) still haven't emerged. If they based it upon something simpler and/or created a simple editor for making your own logins (because you really don't need something as powerful as Flash Professional to do a simple login), I think it'd be much more enticing to people. Winamp doesn't have a billion skins because it's skinning engine is super powerful or highly extensible; it has all those skins because its simple and easy to make skins for it with simple tools that come with any Windows PC.