For a while now I've been suffering with an annoying problem when running OI on my Windows 7 laptop: any window or control that used the "default" font was rendered at the wrong size - it was being rendered as though I had a high DPI (120) set, which of course I didn't - the laptop was set to run at 96 DPI.
Here's a couple of examples to show you what I mean:
None of my other PCs running OI had this problem - just my laptop. The only difference was that the laptop OS was installed by Dell, whereas all my other machines were installed by me.
After some searching I came across the following blog post which gave the solution:
Windows 7, bitmap fonts and Microsoft Dynamics GP
Basically the DPI was set to 120 during the installation process which means that the standard OS bitmapped fonts were installed as 120 DPI rather than their 96 DPI versions. Unfortunately in Windows 7 these fonts are not changed by a user's individual DPI settings - they are system wide, and so affect all users regardless of their DPI setup.
Making the registry changes described in the MSDN blog article above solved the problem and OI now looks normal on my laptop again.
Here's a couple of examples to show you what I mean:
None of my other PCs running OI had this problem - just my laptop. The only difference was that the laptop OS was installed by Dell, whereas all my other machines were installed by me.
After some searching I came across the following blog post which gave the solution:
Windows 7, bitmap fonts and Microsoft Dynamics GP
Basically the DPI was set to 120 during the installation process which means that the standard OS bitmapped fonts were installed as 120 DPI rather than their 96 DPI versions. Unfortunately in Windows 7 these fonts are not changed by a user's individual DPI settings - they are system wide, and so affect all users regardless of their DPI setup.
Making the registry changes described in the MSDN blog article above solved the problem and OI now looks normal on my laptop again.
Labels: OpenInsight, Windows 7
Well we've been running with Windows 7 on a couple of our laptops for a few weeks now and we like it! The ability to launch a program by typing just a few letters of its name is brilliant... the only downer was not being able to run AREV at all anymore - oh yes, and the fact that as of the time of writing OpenInsight 9.1 completely hangs - I mean COMPLETELY hangs Windows 7 64 bit.
Note I said "was" because today we installed Virtual PC for Windows 7 along with XP Mode and huzzah - we have an environment where we can actually work with AREV and OI! You can read all about it here.
The only thing to point out is that once you enabled virtualization in your BIOS you have to do a cold reboot - turn the machine completely off. Easily overlooked and potentially frustrating.
[Edit] - The hanging issue is fixed for OI 9.1.1
Note I said "was" because today we installed Virtual PC for Windows 7 along with XP Mode and huzzah - we have an environment where we can actually work with AREV and OI! You can read all about it here.
The only thing to point out is that once you enabled virtualization in your BIOS you have to do a cold reboot - turn the machine completely off. Easily overlooked and potentially frustrating.
[Edit] - The hanging issue is fixed for OI 9.1.1
Labels: Virtual PC, Windows 7, XP Mode
Previous Posts
Archives
BlogRoll
Subscribe
Subscribe via RSS
(For those who still appreciate civilised technology.)
Add to your reader
Scan to subscribe
Subscribe to
Posts [Atom]
| Making Databases Happen |
USA +1 267 238 3814
|