Windows XP Prof. 64-bit edition

[c.melin]

Hi!

I've been looking at GBPVR for several years but I haven't been able to build myself a media system until now. I'm about start assembling my system in a week or two. Therefore I thought it would be a good idea to sign up. I'll be using an AMD Athlon 64 processor with single or dual core and Windows XP Prof. 64-bit edition. Do you know of any compatibility issues between the 64-bit XP edition and GBPVR? Is there anything else a newbie like me should consider when building and setting up the system? All tips and hints are welcome.

My system will look like this:
AMD Athlon64 3700+ or AMD Athlon 64 X2 4200+
4GB DDR400
2x500GB HDD
iMon VFD display and remote
FloppyDTV DVT-T tuner with CI/CAM
DVD-RW

It will be connected to my 40" HD-ready LCD TV through either D-Sub or DVI-D and hopefully the TV will accept a 1:1 resolution (1366x768)

It may be a bit overkill but I guess I can be fairly certain that the system will not have any performance issues when it comes to HD material. :p

I may be a newbie when it comes to media system frontends but I've been working with computers and software engineering for about a decade so I'm looking forward to start looking at skin and plugin APIs and sooner or later I'll probably start experimenting with my own stuff. I'm sure I'll be needing support during that process.

[stu8080]

4GB mem seems loads, any reason you need so much, to do with HD TV?

[sub]

A few people run on the 64 bit version of XP, but I havnt actually tried it myself. Of course you will need to have 64 bit drivers for your device. I'm not sure if these are available for the FireDTV DVB-T or not.

For now you'll need to install .net 1.1 for it to work, but the next release will work with .net 2.0.

[c.melin]

I guess 4GB is not really necessary at the moment but since I got a good deal I figured I might as well load up on RAM to make sure that it will not be an issue in the near future. I also want to be able to use the computer without having to think about the memory usage.

I haven't thought about driver availability for the 64-bit XP version. That may turn out to be a problem. I guess I'll know in a couple of weeks.

Any prognosis as to when the next release with .NET 2.0 support will be released?

[sub]

Any prognosis as to when the next release with .NET 2.0 support will be released?

Not in the next few weeks.

[stefan]

I haven't thought about driver availability for the 64-bit XP version. That may turn out to be a problem. I guess I'll know in a couple of weeks.

Welcome onboard, old friend! I did a little lurking over at firedtv, and it does not look too good

http://www.firedtv.com/Forums/tabid/311/...fault.aspx

[c.melin]

Welcome onboard, old friend!

Thanks! About time I came around, eh?

I did a little lurking over at firedtv, and it does not look too good

http://www.firedtv.com/Forums/tabid/311/...fault.aspx

Hmmm, well, I guess the purchase of the x64 XP version may have been a bit hasty and, as it turns out, not a very good choice. Bummer! Money not very well spent! Since I have an XP Home Ed. too I may use that instead.

[stefan]

Thanks! About time I came around, eh?

Yep

[Torque]

just doesn't seem to want to work together in a mix Server OS: 2003 Standard, Clients OS: XP Pro and XP Pro MCE 2005.

Was it just HTPC related stuff that didn't work together? I ran it for a while on my desktop at work (A64 3000+) and it worked fine in our AD domain environment (W2k3, with XP and 2K clients as well). Had no problems with it in that respect. We have a few homegrown apps that wouldn't work with it, so I had to go back reg XP Pro.