Windows 7 install problem

[MitchSchaft]

Hey folks. I put together a new machine after my MCE2005 box finally bit the dust last month. I've installed Win7 Ultimate and installed the latest Sage media center exe. When I try to start the service, my computer freezes. I have to hard boot to bring it back.
Has anyone had this problem?

Win7 Ult
Geforce 7600gs
2GB ram
AMD be-2350
Avermedia Purity 3D MCE 500 PCI

[gplasky]

Ultimate also has Windows Media Center built in. Make sure you disable or uninstall Windows Media Center services.

Gerry

[koan00]

I have no problems with Windows 7, but I do not run service mode.

What is in the Event logs and SageTV logs?

[MitchSchaft]

I had WMC all disabled and there was nothing in the any of the logs to speak of. I got it working by running the sage exe and service exe in compatability mode for winxp sp3.
Is that a normal thing to do?

[HelenWeathers]

I'm running on Win Pro 7 32 bit in service mode without any problems. Have been for about 3 weeks now. Had a problem with java 6u17 and rolled that back (will try again in case it was a bad java install when I get a chance).

[MitchSchaft]

Oops, I guess I should mention I run 32-bit, too.

[davephan]

Is it better to use 32 bit than 64 bit Windows 7? I was thinking about using Windows 7 64-bit on my next system. If there aren't any serious problems, I would rather use 64-bit.

Dave

[gplasky]

Originally Posted by davephan

Is it better to use 32 bit than 64 bit Windows 7? I was thinking about using Windows 7 64-bit on my next system. If there aren't any serious problems, I would rather use 64-bit.

Dave

For a Sage client I use 64 bit Win 7. But for a Sage server you need to be aware of the hardware devices you are using. Consider if they're new (and therefore may have 64 bit signed drivers) or a little older and may not have 64 bit drivers, let alone that they are signed (WHQL) In the Sage server case it may make more sense to stick with the 32bit OS and have better hardware support for hardware you already own.

Gerry

[davephan]

I plan to use Windows 7 64-bit for the SageTV server. I use a HD-200 and MVP extenders. I will replace the MVPs with HD-200s in the future.

As far as I could determine, the HD-PVR, 2250, and HDHomerun will all work with Windows 7 64-bit server. I don't think the old PVR-350 will work with Windows 7 64-bit. However, I could easily move that card to an older computer, since it is only used for ripping old VHS video tapes now.

Are there any other possible problems using the 64-bit version of Windows 7 verses the 32-bit version as a SageTV server?

Dave

[gplasky]

Currently there is no 64 bit firewire driver so no firewire channel changing on Win 7 64 bit.

Gerry

[MitchSchaft]

64-bit is all hype. You won't notice a difference. Now go start your own thread.

[Fuzzy]

Originally Posted by MitchSchaft

64-bit is all hype. You won't notice a difference. Now go start your own thread.

You will if you intend to use 4GB or more RAM. And seriously, most hardware people are already using IS supported in win7-64. The Sage Process itself can't use more than 2GB, because of the Java limitations, but having 6GB or so would allow plenty of RAM for some a few comskip jobs, a separate client process, and some transcoding (conversion/mvp/placeshifter), all without hitting swap space. (That's not even counting the improved IO access that more memory provides, by running larger disc caching.)

Basically, if the hardware you are using works in 64-bit.. you might as well run it... if nothing else, it would allow you to more easily add RAM later, without having to completely reinstall.

[MitchSchaft]

[koan00]

Originally Posted by Fuzzy

You will if you intend to use 4GB or more RAM. And seriously, most hardware people are already using IS supported in win7-64. The Sage Process itself can't use more than 2GB, because of the Java limitations, but having 6GB or so would allow plenty of RAM for some a few comskip jobs, a separate client process, and some transcoding (conversion/mvp/placeshifter), all without hitting swap space. (That's not even counting the improved IO access that more memory provides, by running larger disc caching.)

Basically, if the hardware you are using works in 64-bit.. you might as well run it... if nothing else, it would allow you to more easily add RAM later, without having to completely reinstall.

http://www.tipandtrick.net/2008/how-...r-more-memory/
You can pretty easily enable PAE on 32bit vista and windows 7. Its just an artificial MS limitation. You still have the same per process memory limit, but you can use all 4+ GB with a little hacking.

Edit: Nm I realized it was a vista only hack. Oh well.

[MitchSchaft]

I'm wondering if it has to do with my older tv tuner. I should try running it with the card out of the machine.

[SHS]

Originally Posted by Fuzzy

You will if you intend to use 4GB or more RAM. And seriously, most hardware people are already using IS supported in win7-64. The Sage Process itself can't use more than 2GB, because of the Java limitations, but having 6GB or so would allow plenty of RAM for some a few comskip jobs, a separate client process, and some transcoding (conversion/mvp/placeshifter), all without hitting swap space. (That's not even counting the improved IO access that more memory provides, by running larger disc caching.)

Basically, if the hardware you are using works in 64-bit.. you might as well run it... if nothing else, it would allow you to more easily add RAM later, without having to completely reinstall.

Only becuases Java 32Bit has a 2GB RAM limitations but from what I read there is no Java 64BIT RAM limitations now we need is 64bit ver of SageTV to make used of 64bit Java.

All the system in my house 4 in all are now on Windows 7 64Bit in fact I just finsh upgrade+clean install the SageTV media server.
Boy that way fun I manage get backup data up and runing with out having re-setup all the tuner etc, etc, and keeping min years which is at all most 2000 days I would have had more but due bad backup didn't go well back then so start more more then one backup.

[ccsmoke]

Mitch,

Did you run prime 95 to see if this isn't a ram issue?

[MitchSchaft]

I ran orthos all night with no troubles.

[ccsmoke]

It could very well be your tuner card, I read some people had to reseat the card for it to recogize in windows 7 beta version. It also could be corrupt file in sage download. One way to test your card is unistall sage and try media center see it that hangs also.

I made a little cheat sheet of what works for me when I install sage on fresh stable machine. I successfully install sage on 8 different computers but I'm no expert by any means. I also use HD PVR Rev E for my only capture device and have been stable with no lockups, or lip sync issues. I am also using 6u16 java version on server, haven't tried the latest java. I also use onboard audio. I usually shy away from codec packages but shark007's just plain works for me with no hassel. I also don't use 64k clusters.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-Install windows updates, only critical updates.
-Install mobo chipset, and audio drivers from mobo manufacturer. (ex realtek drivers from mobo manufacturer instead of the realtek site)
-Install latest video drivers.
-Install java.
-Install 7 zip
-Turn off UAC (under users in windows 7 using slider)
-Download and install shark007 codec package.(64 bit also download component addon)
-Config sound in codec package. (2.0, 5.1 etc.)
-Install HD PVR software with latest drivers. (with windows 7 beta I had to set acrsoft as DEP exception)
-Test videos in windows media player.
-Set up file sharing
-Disable Window Media Center services.
-Download sagetv and full version of sagemc
-Install sagetv and do setup (adjust properties HD PVR magic to false, also use arcsoft video decoder)
-Close sagetv and disable services etc
-Install sagemc keeping file structure in tact.
-Start sagetv and load 16X9