View Full Version : Girder / WinXP Wierdness
Ron
October 13th, 2002, 12:55 PM
I'm soo happy I don't have WinXP, too expensive too crappy :smile:
<font size=-1>[ This Message was edited by: RonB on 2001-12-10 16:38 ]</font>
Ron
October 13th, 2002, 12:55 PM
Win XP is a compromise for sure but it beats the hell out of 95/98/ME's instability.
Agreed,.. No support for spdif ? My computer here (running Win2k) has a spdif out working. Or is that a limitation of your soundcard ?
Ron
October 13th, 2002, 12:55 PM
That is weird,... those 800k is that including the part that Windows swapsout ?
Ron
October 13th, 2002, 12:55 PM
Too bad :smile: That could have accounted for the difference.
Ron
October 13th, 2002, 12:55 PM
I have no idea what that memory issue is. As you can imagine i have no function built in that only releases memory after it has been in the traybar. This is a XP-problem, sorry.
SteveV
October 13th, 2002, 12:55 PM
Can anybody running Girder on a WinXP box confirm if they are seeing this:
I have Girder set to "Launch Girder on Windows Startup", "Traybar Mode", and "Hide on Startup". For some wierd reason XP decides does not allow Girder to be restored or maximized after it has launched. Even if I uncheck "Hide on Startup", Girder will launch and display normally during XP startup. But as soon as it's minimized, it's no longer accessable :sad:
If I ctrl-alt-del to pop up the task manager, Girder does not appear in the task list. Instead, it appears in the process list with no way of activiting it. At first I thought the problem was with XP tray bar "hide if inactive" icon setup. I have Girder set to "Always Show". But it never appears on the sys tray unless I kill the Girder process, then relaunch Girder. Once terminated and relaunched everything behaves normally. BTW, aside from not being visible or accessable, Girder works fine.
Has anybody seen such wierdness or have a workaround?
--Steve
SteveV
October 13th, 2002, 12:55 PM
I'm soo happy I don't have WinXP, too expensive too crappy :smile:
I would have gone with Windows 2000 but the lack of support for custom resolutions (in my case 1064 X 600 @ 60hz for my 16:9 RPTV) and lack of sound card S/PDIF pass through (Dolby Digital/DTS) make it a miserable choice for HTPC use. Win XP is a compromise for sure but it beats the hell out of 95/98/ME's instability.
--Steve
SteveV
October 13th, 2002, 12:55 PM
Agreed,.. No support for spdif ? My computer here (running Win2k) has a spdif out working. Or is that a limitation of your soundcard ?
Maybe. I have an M-Audio Audiophile 24/96-- IIRC, there were win 2000 drivers but no spdif output. I'm not sure where the problem was but suspect all of this was pre-service pack 2. Correct me if I'm wrong, but I believe custom display resolutions are still an issue under windows 2000. This was the ultimate deal breaker for me as my set only support 60hz refresh rates at 600 vertical lines (max). It's a 16:9 display and in order to keep correct aspect ratio I need a display rez of 1064X600. Moot point anyway now that I've taken the plunge with XP.
BTW, despite all the "fluff", I've been pleasantly surprized with XP.
--Steve
SteveV
October 13th, 2002, 12:55 PM
Any idea if this problem will be fixed anytime soon?
nmirza,
The problem isn't all that critical. The only time it's really an issue is when you need to edit your Girder file. In which case you Ctrl-Alt-Del, select the processes tab, select Girder and click the end process button. At that point you can re-launch Girder and it behaves normally.
Ron,
Is there any way to restore Girder from a command line argument? I tried creating a MultiGroup that restored the Girder window, but couldn't seem to get it to work :sad:. I either got an empty window (no tree-view, action pane, etc) or got what appeared to be all the plugin windows (and the targeting window, I think). My hope was to be able to assign a hotkey to the multigroup. Any suggestions?
Thanks -- Steve
<font size=-1>[ This Message was edited by: SteveV on 2001-12-13 22:58 ]</font>
SteveV
October 13th, 2002, 12:55 PM
On 2001-12-17 15:43, nmirza wrote:
I've just finished installing XP and Girder on my system. I am not seeing any issues with Girder shrinking to tray mode. Wonder what is causing the "weirdness"?
What's even weirder is that I've installed Girder and the Slink-e server on another Win XP machine Girder appears in the tray as you would expect it to. Both machines are similar in setup. The only major difference I can see is that XP was a clean install (using XP upgrade) on the second machine whereas it was an upgrade install on the first.
I've tried reinstalling Girder on the first machine to no avail. I haven't tried reinstalling the slink-e server yet but suspect that will do little good.
Nonetheless, I'll give it a shot when I have some free time.
Regarding the XP strangeness jon_rhees reported-I'm seeing similar weirdness. On my second machine with Girder starting up in tray bar/hide on startup mode I'm seeing:
1. Startup Girder : TaskManager reports Girder takes over 6.6MB of memory (6676K)!
2. Restore Girder: 6744K
3. Minimize Girder, now Task Manager reports Girder only takes 1976K
4. Restore screen, minimize, again: 2660K
Regards -- Steve
nmirza
October 13th, 2002, 12:55 PM
I'm really interested in upgrading my HTPC to XP. Any idea if this problem will be fixed anytime soon?
Naveed
nmirza
October 13th, 2002, 12:55 PM
I've just finished installing XP and Girder on my system. I am not seeing any issues with Girder shrinking to tray mode. Wonder what is causing the "weirdness"?
nmirza
October 13th, 2002, 12:55 PM
WEIRD! I'm seeing that behavior too.
Jus_001
October 13th, 2002, 12:55 PM
I too have experienced these problems under xp.
mattwire
October 13th, 2002, 12:55 PM
SpDif support under win2k was fixed with service pack 2. So upgrade to service pack 2 and you'll be able to use spdif correctly.
jon_rhees
October 13th, 2002, 12:55 PM
FWIW, I've been using Girder for some time under XP and although I *am* able to shrink to tray and resume normally, I did notice a strange issue:
1. Startup Girder (girder setup to start normal-screen): TaskManager reports Girder takes over 3MB of memory!
2. Minimize Girder, now Task Manager reports Girder only takes 800K
3. Restore screen, minimize, etc., Girder from now on only takes 800K
Scenario 2:
1. Startup Girder (girder setup to start minimized in Tray): Girder takes over 3MB!
2. Restore screen -- still takes 3MB
3. Minimize to tray, continues to take 3MB...
So, I have no idea what is happening, but just in case, I have a 'startup' script in Girder to minimize itself when started.
-Jon
jon_rhees
October 13th, 2002, 12:55 PM
Ron, I don't know... I was simply reporting what Windows Task Manager reports for that app. The task manager in XP is pretty much the same as the one in 2K.
-Jon
epsylon3
October 13th, 2002, 12:55 PM
Ya but a compatible with other OS with multiple app libraries...
(Right Click on Exe / Compatibity)
<font size=-1>[ This Message was edited by: epsylon3 on 2001-12-10 19:33 ]</font>
Powered by vBulletin® Version 4.1.8 Copyright © 2012 vBulletin Solutions, Inc. All rights reserved.