I did think of one thing... make sure that the Web client is set to Seamless not a partial screen or a named resolution 800 x 600 et al. We had one app that if you had the web client NOT set to seamless that the text would scrunch. The only thing I thought of on my "bad" app was that whatever registry key it queried for screen size didn't give the app what it wanted. i.e. the app thought you had a different screen size than what you had, so didn't draw right. You might want to try via Program Neighborhood the app and deliberately screw up the resolution and see if you can replicate the "scrunching" factor. (to test the theory/if you can break it on cue and "unbreak" it you're on the way to a solution) Msg: #1 in digest From: "Steve Raffensberger" <sraffens1@xxxxxxxxxxx> Subject: [THIN] Re: UPDATE: Re: VB app on Win 2k3: fonts look different? Date: Sat, 11 Sep 2004 09:30:39 -0400 When you run it from the W2K3 console and it is fine, are you using the same screen resolution and color depth as the RDP/ICA clients? -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of Landin, Mark Sent: Friday, September 10, 2004 3:32 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] UPDATE: Re: VB app on Win 2k3: fonts look different? I originally asked: > > We are publishing a VB app a consultant wrote for us. It looks good on > > our Windows 2000 systems, but when published from our test Windows > > 2003 terminal server, the labels for the various fields on the forms > > look scrunched together, and in some cases, the label is truncated. > > Other applications published on this server look OK ... It's only this > > VB app that is having the problem. Later, I wrote: > The field labels themselves are "scrunched up". The field > themselves have also all shifted to the left, so that the > right side of the screen is pretty empty (it's a form we run > full-screen ... It's pretty busy). > In a couple of cases, the fields actually run up against long > field labels so the labels appear truncated. Text INSIDE the > fields themselves appear to be OK. > ... > I think what I'm going to do is to put the > Win2K Sans Serif font on the > 2k3 box (it's still in testing mode, so if I break something > I can always roll back to a previous ghost) and see if that > resolves the problem. I wasn't able to change the font out (wouldn't let me delete the Sans Serif on the Windows 2003 .. Something had it open), but I did try another thing. I'm an idiot so I didn't test this before, but: when the app is run from the console of the Terminal Server, it appears FINE. If the app is run from an ICA client as a desktop or as a published app, it's screwed up. AND, if it's run over an RDP desktop it is STILL screwed up (somehow, I thought it would work over RDP, making this an ICA-specific issue). Now then: I'm running MPS 3.0 on Windows 2003, using the ICA 8.00.24737 client. The application is a VB6 app, launched from a Microsoft Great Plains 7.5 sessions. This app looks fine using this ICA client when presented from a Windows 2000/Metaframe XP system, but looks bad when presented from a Windows 2003/MPS 3.0 system. ******************************************************** This Weeks Sponsor triCerat: Have you had your fill of printing support calls, unauthorized apps running on unsecured Terminal Servers, profile headaches, and application performance problems? Join us and learn how you can have a less demanding on-demand enterprise! http://www.tricerat.com/?page=events#register ********************************************************** Useful Thin Client Computing Links are available at: http://thin.net/links.cfm *********************************************************** For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use the below link: http://thin.net/citrixlist.cfm