|
code
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Contemplating the Migrationapps are fairly robust and have been deployed operationally on a limited scale. There is approximately 30 to 40K lines of code. A big question of the user base is "Will these apps work on Vista or Windows 7?". A valid question. The Apps heavily use XML 4.0, tie to an Access 2003 database, and rely on a small set of active X controls, and integrate with Office 2003. I've received a lot of help from this community over the past couple of years to over-come hurdles in the projects - which I greatly appreciate. So... where do I go from here? Initial attempts to get things to function on Vista have been unsuccessful. Primary issue is getting the VB6 run-time to install. My IS2009 install package fails even though it is set to install on a Vista box. I have not spent much time with Vista and figure my user base will go from XP to Windows 7 since the new OS is just around the corner. I know that Windows 7 has a virtual XP option... but that seems like a limited solution to VB6 not running on these newer OSs. So my question... do I migrate to Dot Net or should I consider another path? I could possibly use JAVA... What about C-sharp? I've seen reports that VB2008 isn't all that it was cracked up to be. I've also heard rumors that people are moving away from Dot Net as it hasn't lived up to the expectation or hype that it was given... Any thoughts on the best migration path would be appreciated. "Brian" <Br***@discussions.microsoft.com> wrote in message My VB6 apps work fine from Windows 95 to 7.news:3D414564-F5F5-4234-BC5E-4A35B25CC827@microsoft.com... > A big question of > the user base is "Will these apps work on Vista or Windows 7?" > The Apps heavily use XML 4.0, tie to an Access 2003 database, and No problem here.> rely on a small set of active X controls, and integrate with Office 2003. > Initial attempts to get things to function on Vista have been The reason for this is that the VB6 runtime files are protected under Vista, > unsuccessful. > Primary issue is getting the VB6 run-time to install. My IS2009 install > package fails even though it is set to install on a Vista box. including their registry entries, so you can't update them nor even register them. They are at SP6 anyway, so there is no point to try to update them. The solution is to NOT install or register the VB6 runtimes on Windows Vista/2008/7, so check for the OS version, and if it's Windows 2003 Server or below, then update the runtimes. Microsoft said there is no plan to include the VB6 run time after Windows 7, so after 7, update the VB6 runtime as usual. In the article below, all the files under the heading "Supported and Shipping in Windows Vista, Windows Server 2008, and Windows 7" are protected, so don't update or register them, just make exception in the installer for these files. Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 and Windows 7 http://msdn.microsoft.com/en-us/vbasic/ms788708.aspx > I have not Besides the installation issues above, many of the things that broke some > spent much time with Vista and figure my user base will go from XP to > Windows > 7 since the new OS is just around the corner. VB6 apps started with Vista, so if your app works under Vista, it will work under 2008/7. The main issue with Vista is changes in security, or how most home users run as administrators in 2000/XP. Users who are members of the limited "Users" group don't have write access to the sub folders under "Program Files" and HKLM in the registry. They can read from these locations, but can't write to them. In Vista, if you write to some of these locations, it's redirected to another file. Search the newsgroups for SHGetSpecialFolderLocation() for details. But more importantly, when you call an API function with a flag like ALL_ACCESS, usually the function fails with access denied error. This happens under Windows NT4 too, but in Vista, the admin have a split token(two personalities if you will), the default behaves as if the user is member of "Users", and when elevated, behaves as Administrator. So if under Vista, your program works fine when you right click and use "Run As Administrator", then you have permissions issues. The most common API calls that fail are OpenProcess(), RegOpenKey(Ex), OpenFile(), CreateFile(), and VB's Open statement. Basically check any function that has "Open", or "Create" in it's name, and any function that manipulate files or folders. Use only the flags that you need. > So my question... do I migrate to Dot Net or should I consider another A VB6 app uses less resources than a DotNet app, so you have to add more > path? memory to run the newer OS'es, even more if you use a terminal server since memory usage multiplies per process. See this article: http://blogs.technet.com/markrussinovich/archive/2005/04/16/the-coming-net-world-i-m-scared.aspx Thanks for the very informative post... You jogged my memory on the VB6
pieces in Vista... I'll have to try to manually load my apps onto Vista and just run them. I do access the Registry and store user specific application parameters... Does Vista protect the CurrentUser keys in the same way as LocalMachine keys? Guess I'll find out when I try... Also... does it matter which version of Vista is installed? I'll update my installer to do checks or just create a simple Vista/Windows 7 installer. Thanks... Show quoteHide quote "Nobody" wrote: > "Brian" <Br***@discussions.microsoft.com> wrote in message > news:3D414564-F5F5-4234-BC5E-4A35B25CC827@microsoft.com... > > A big question of > > the user base is "Will these apps work on Vista or Windows 7?" > > My VB6 apps work fine from Windows 95 to 7. > > > The Apps heavily use XML 4.0, tie to an Access 2003 database, and > > rely on a small set of active X controls, and integrate with Office 2003. > > No problem here. > > > Initial attempts to get things to function on Vista have been > > unsuccessful. > > Primary issue is getting the VB6 run-time to install. My IS2009 install > > package fails even though it is set to install on a Vista box. > > The reason for this is that the VB6 runtime files are protected under Vista, > including their registry entries, so you can't update them nor even register > them. They are at SP6 anyway, so there is no point to try to update them. > The solution is to NOT install or register the VB6 runtimes on Windows > Vista/2008/7, so check for the OS version, and if it's Windows 2003 Server > or below, then update the runtimes. Microsoft said there is no plan to > include the VB6 run time after Windows 7, so after 7, update the VB6 runtime > as usual. > > In the article below, all the files under the heading "Supported and > Shipping in Windows Vista, Windows Server 2008, and Windows 7" are > protected, so don't update or register them, just make exception in the > installer for these files. > > Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 > and Windows 7 > http://msdn.microsoft.com/en-us/vbasic/ms788708.aspx > > > I have not > > spent much time with Vista and figure my user base will go from XP to > > Windows > > 7 since the new OS is just around the corner. > > Besides the installation issues above, many of the things that broke some > VB6 apps started with Vista, so if your app works under Vista, it will work > under 2008/7. The main issue with Vista is changes in security, or how most > home users run as administrators in 2000/XP. Users who are members of the > limited "Users" group don't have write access to the sub folders under > "Program Files" and HKLM in the registry. They can read from these > locations, but can't write to them. In Vista, if you write to some of these > locations, it's redirected to another file. Search the newsgroups for > SHGetSpecialFolderLocation() for details. > > But more importantly, when you call an API function with a flag like > ALL_ACCESS, usually the function fails with access denied error. This > happens under Windows NT4 too, but in Vista, the admin have a split > token(two personalities if you will), the default behaves as if the user is > member of "Users", and when elevated, behaves as Administrator. So if under > Vista, your program works fine when you right click and use "Run As > Administrator", then you have permissions issues. > > The most common API calls that fail are OpenProcess(), RegOpenKey(Ex), > OpenFile(), CreateFile(), and VB's Open statement. Basically check any > function that has "Open", or "Create" in it's name, and any function that > manipulate files or folders. Use only the flags that you need. > > > So my question... do I migrate to Dot Net or should I consider another > > path? > > A VB6 app uses less resources than a DotNet app, so you have to add more > memory to run the newer OS'es, even more if you use a terminal server since > memory usage multiplies per process. See this article: > > http://blogs.technet.com/markrussinovich/archive/2005/04/16/the-coming-net-world-i-m-scared.aspx > > > > > "Brian" <Br***@discussions.microsoft.com> wrote in message No, current user keys and AppData folder(per user) are fully news:3EED7506-35A4-4C35-AB19-D78C6D26DB3D@microsoft.com... > Thanks for the very informative post... You jogged my memory on the VB6 > pieces in Vista... I'll have to try to manually load my apps onto Vista > and > just run them. I do access the Registry and store user specific > application > parameters... > > Does Vista protect the CurrentUser keys in the same way as LocalMachine > keys? Guess I'll find out when I try... readable/writable. It's only the machine wide settings and locations that are read-only. > Also... does it matter which version of Vista is installed? No.> I'll update my installer to do checks or just create a simple You can just copy the EXE, and register any DLL or OCX you need and their > Vista/Windows > 7 installer. dependencies(if any) for testing. And there are other problem areas with VB6 on Vista, some of which have been
overcome so not yet. IDE problems executing: SendKeys INI routines. These seem to be OK in the comple app. Compiled app problems: Transparancy handled differently - no click-through with Vista Aero on. This kills one of my apps. My tooltip rouines that work OK on XP blow up the screen on Vista (aero off) and I have to reboot to clear. Have not had time to troubleshoot this so I just use a different method to show a tip. Why do we not have a place to register all the Vista related problems so we can keep up with it? Trying to find these in the newsgroup is difficult for me. Show quoteHide quote "Nobody" wrote: > "Brian" <Br***@discussions.microsoft.com> wrote in message > news:3EED7506-35A4-4C35-AB19-D78C6D26DB3D@microsoft.com... > > Thanks for the very informative post... You jogged my memory on the VB6 > > pieces in Vista... I'll have to try to manually load my apps onto Vista > > and > > just run them. I do access the Registry and store user specific > > application > > parameters... > > > > Does Vista protect the CurrentUser keys in the same way as LocalMachine > > keys? Guess I'll find out when I try... > > No, current user keys and AppData folder(per user) are fully > readable/writable. It's only the machine wide settings and locations that > are read-only. > > > Also... does it matter which version of Vista is installed? > > No. > > > I'll update my installer to do checks or just create a simple > > Vista/Windows > > 7 installer. > > You can just copy the EXE, and register any DLL or OCX you need and their > dependencies(if any) for testing. > > > > On Mon, 18 May 2009 19:05:01 -0700, Bee
<B**@discussions.microsoft.com> wrote: >Why do we not have a place to register all the Vista related problems so we In terms of peer support there is>can keep up with it? news:microsoft.public.vb.vista.compatibility which gets little traffic, mostly misguided posts about non-VB Vista compatibility. As you say though it would be handy if there was a common repository of VB/Vista issues and solutions. Bee wrote:
> And there are other problem areas with VB6 on Vista, some of which have been Fix: > overcome so not yet. > > IDE problems executing: > SendKeys http://visualstudiomagazine.com/articles/2007/11/13/vb-statement-against-vista.aspx > INI routines. Huh? What's the problem there?"Karl E. Peterson" <k***@exmvps.org> wrote in message Probably permissions on where to save INI files, not the INI functions news:uY8fNSK2JHA.5728@TK2MSFTNGP03.phx.gbl... > Bee wrote: >> INI routines. > > Huh? What's the problem there? themselves. Nobody wrote:
> "Karl E. Peterson" <k***@exmvps.org> wrote ... True, if going for apppath under programfiles.>> Bee wrote: >>> INI routines. >> >> Huh? What's the problem there? > > Probably permissions on where to save INI files, not the INI functions > themselves. On Mon, 18 May 2009 14:49:02 -0700, Brian
<Br***@discussions.microsoft.com> wrote: Show quoteHide quote >Thanks for the very informative post... You jogged my memory on the VB6 Brian, have a read of my recent posting in this thread.>pieces in Vista... I'll have to try to manually load my apps onto Vista and >just run them. I do access the Registry and store user specific application >parameters... > >Does Vista protect the CurrentUser keys in the same way as LocalMachine >keys? Guess I'll find out when I try... >Also... does it matter which version of Vista is installed? > > >I'll update my installer to do checks or just create a simple Vista/Windows >7 installer. > >Thanks... MM On Mon, 18 May 2009 11:23:05 -0700, Brian
<Br***@discussions.microsoft.com> wrote: >Initial attempts to get things to function on Vista have been unsuccessful. I have successfully run my VB6 application on XP2, Vista and Windows 7>Primary issue is getting the VB6 run-time to install. Beta using a separate manifest file. That is, zero installation! Just copy the files, including OCXs, to a new folder, create a shortcut, bingo! I even managed to run the app off a DVD. See here: http://www.littletyke.myzen.co.uk/ktn/index.html MM Hi,
MM schrieb: Show quoteHide quote > On Mon, 18 May 2009 11:23:05 -0700, Brian Works here on my WIN XP SP3 box.> <Br***@discussions.microsoft.com> wrote: > >> Initial attempts to get things to function on Vista have been unsuccessful. >> Primary issue is getting the VB6 run-time to install. > > I have successfully run my VB6 application on XP2, Vista and Windows 7 > Beta using a separate manifest file. That is, zero installation! Just > copy the files, including OCXs, to a new folder, create a shortcut, > bingo! I even managed to run the app off a DVD. > > See here: http://www.littletyke.myzen.co.uk/ktn/index.html > > MM One question: which tool did you use to create the manifest? "Ulrich Korndoerfer" <ulrich_wants_nospam@prosource.de> wrote in message It also works here on my Vista SP2 setup. I'm not sure what tool MM used to news:uhotmUz3JHA.5276@TK2MSFTNGP04.phx.gbl... > [Addressed to MM] Works here on my WIN XP SP3 box. > One question: which tool did you use to create the manifest? produce the manifest but it might be Make My Manifest. I've used it for only a short time myself purely for test purposes at the moment (version 0.6.6) and it seems to work fine so far: http://mmm4vb6.atom5.com/ Mike On Thu, 28 May 2009 04:38:34 +0100, "Michael Williams"
<M***@WhiskeyAndCoke.com> wrote: Show quoteHide quote >"Ulrich Korndoerfer" <ulrich_wants_nospam@prosource.de> wrote in message From one Mike to another, thanks to you, too, for your confirmation!>news:uhotmUz3JHA.5276@TK2MSFTNGP04.phx.gbl... > >> [Addressed to MM] Works here on my WIN XP SP3 box. >> One question: which tool did you use to create the manifest? > >It also works here on my Vista SP2 setup. I'm not sure what tool MM used to >produce the manifest but it might be Make My Manifest. I've used it for only >a short time myself purely for test purposes at the moment (version 0.6.6) >and it seems to work fine so far: > > http://mmm4vb6.atom5.com/ > >Mike MM On Thu, 28 May 2009 03:39:29 +0200, Ulrich Korndoerfer
<ulrich_wants_nospam@prosource.de> wrote: Show quoteHide quote >Hi, Grüß Gott! I used Make My Manifest. See: http://mmm4vb6.atom5.com/> >MM schrieb: >> On Mon, 18 May 2009 11:23:05 -0700, Brian >> <Br***@discussions.microsoft.com> wrote: >> >>> Initial attempts to get things to function on Vista have been unsuccessful. >>> Primary issue is getting the VB6 run-time to install. >> >> I have successfully run my VB6 application on XP2, Vista and Windows 7 >> Beta using a separate manifest file. That is, zero installation! Just >> copy the files, including OCXs, to a new folder, create a shortcut, >> bingo! I even managed to run the app off a DVD. >> >> See here: http://www.littletyke.myzen.co.uk/ktn/index.html >> >> MM > >Works here on my WIN XP SP3 box. > >One question: which tool did you use to create the manifest? I first downloaded http://home.comcast.net/~bvocs/miscdls/MMM-0-6-6.exe and was also, like comments elsewhere on the web, a bit wary, since it is an .exe. Now in my Downloads folder I've also got MMM-0-6-6.ZIP, but I'm blowed if I can find the link I got it from! Perhaps Bob knows where it's hiding! The ZIP contains: Readme.txt Mmm.exe Mmm.ini Using MMM.rtf Mscomctl.ocx Comdlg32.ocx Tlbinf32.dll I found I could NOT use the installer MMM-0-6-6.exe on Windows 98SE (it just loaded, then immediatly exited), but it DID work on XP. Unfortunately, the MMM web site doesn't appear to have been updated for several months now, so I don't know what's happening about future developments. By the way, I'm very pleased to hear that Know The Notes works at your end! Yours is the FIRST actual, concrete confirmation of this! Thanks. MM Guten Abend :-)
MM schrieb: >>> ... Thanks for the info. I am aware of MMM and had played a little bit with >> Works here on my WIN XP SP3 box. >> >> One question: which tool did you use to create the manifest? > > Grüß Gott! I used Make My Manifest. See: http://mmm4vb6.atom5.com/ > version 0.6.5. > ... Well, regfree running works. However there are some quirks with your app > By the way, I'm very pleased to hear that Know The Notes works at your > end! Yours is the FIRST actual, concrete confirmation of this! Thanks. when running on my system: - the white background does not cover the whole area. Maybe this is due to my dpi-setting for the monitor (set to 120 dpi) - the sound of your sample midi-file is not played (I can not hear it). On Fri, 29 May 2009 22:39:06 +0200, Ulrich Korndoerfer
<ulrich_wants_nospam@prosource.de> wrote: >- the white background does not cover the whole area. Maybe this is due That is something to look at, but.......> to my dpi-setting for the monitor (set to 120 dpi) >- the sound of your sample midi-file is not played (I can not hear it). .....THIS is a much bigger problem! Do you see either MIDI Mapper or Microsoft GS Wavetable SW Synth in the Output Device combo? If so, is the output volume turned down? (Once I had muted the output so couldn't hear anything!) Is another application blocking the soundcard? I've seen that before as well. By the way, both my PCs have the identical mobo with onboard sound from Realtek. I do have a Creative Labs PCI soundcard, but it is not fitted in any PC at the moment. But I could fit it over the weekend sometime, disable the mobo sound and check that KTN works through that as well. I also have a spare PC that is ancient, but will run Windows 95. Maybe I can check that too. MM Hi,
MM schrieb: > ... Both.>> - the sound of your sample midi-file is not played (I can not hear it). > > .....THIS is a much bigger problem! > > Do you see either MIDI Mapper or Microsoft GS Wavetable SW Synth in > the Output Device combo? > > If so, is the output volume turned down? (Once I had muted the output My fault. Indeed one of the audio card's input channels (the software > so couldn't hear anything!) > synthesizer channel) was muted. Sorry for the false alarm. On Sat, 30 May 2009 01:02:00 +0200, Ulrich Korndoerfer
<ulrich_wants_nospam@prosource.de> wrote: Show quoteHide quote >Hi, Mensch, da habe ich beinahe nicht mehr schlafen können!> >MM schrieb: > >> ... >>> - the sound of your sample midi-file is not played (I can not hear it). >> >> .....THIS is a much bigger problem! >> >> Do you see either MIDI Mapper or Microsoft GS Wavetable SW Synth in >> the Output Device combo? >> > >Both. > >> If so, is the output volume turned down? (Once I had muted the output >> so couldn't hear anything!) >> > >My fault. Indeed one of the audio card's input channels (the software >synthesizer channel) was muted. Sorry for the false alarm. Okay, we can all make mistakes, fair enough! Thanks for letting me know so rapidly. Back to that other problem, and I wonder, have you inspected the Compatibility option? I found this improved the visual look on Vista, though it doesn't make much difference on XP. I'll see if I can dig out more details tomorrow. Maybe you could email me a screenshot to depict the 'white' issue? (kylix_is@... etc etc) Cheers! MM Hi,
MM schrieb: > Back to that other problem, and I wonder, have you inspected the See http://www.prosource.de/Temp/ktn.png> Compatibility option? I found this improved the visual look on Vista, > though it doesn't make much difference on XP. I'll see if I can dig > out more details tomorrow. Maybe you could email me a screenshot to > depict the 'white' issue? (kylix_is@... etc etc) The buttons also indicate problems with the screen settings. On Sat, 30 May 2009 03:37:51 +0200, Ulrich Korndoerfer
<ulrich_wants_nospam@prosource.de> wrote: >Hi, Thanks. No, I haven't seen *that* yet! Looks a bit of a mess, doesn't> >MM schrieb: > >> Back to that other problem, and I wonder, have you inspected the >> Compatibility option? I found this improved the visual look on Vista, >> though it doesn't make much difference on XP. I'll see if I can dig >> out more details tomorrow. Maybe you could email me a screenshot to >> depict the 'white' issue? (kylix_is@... etc etc) > >See http://www.prosource.de/Temp/ktn.png > >The buttons also indicate problems with the screen settings. it! I'll find that Compatibility tab later and see what settings I tried. However, it was only to correct a little bit of flashing when the keyboard was scrolled. Your pic shows up a much more fundamental problem. To Michael Williams: Does it look OK on your PC? MM Hi,
MM schrieb: Show quoteHide quote > On Sat, 30 May 2009 03:37:51 +0200, Ulrich Korndoerfer What I am trying to tell you: your program most probably makes false > <ulrich_wants_nospam@prosource.de> wrote: > >> Hi, >> >> MM schrieb: >> >>> Back to that other problem, and I wonder, have you inspected the >>> Compatibility option? I found this improved the visual look on Vista, >>> though it doesn't make much difference on XP. I'll see if I can dig >>> out more details tomorrow. Maybe you could email me a screenshot to >>> depict the 'white' issue? (kylix_is@... etc etc) >> See http://www.prosource.de/Temp/ktn.png >> >> The buttons also indicate problems with the screen settings. > > Thanks. No, I haven't seen *that* yet! Looks a bit of a mess, doesn't > it! I'll find that Compatibility tab later and see what settings I > tried. However, it was only to correct a little bit of flashing when > the keyboard was scrolled. Your pic shows up a much more fundamental > problem. calculations regarding the sizes of several GUI elements (the white background, the button sizes for example). The faulty display is typical for programs that do not take correctly into account that the environment they are running in has an other setting of the monitor-dpis than the environment used during development. It is *not* a compatibility problem. On Sat, 30 May 2009 23:24:14 +0200, Ulrich Korndoerfer
<ulrich_wants_nospam@prosource.de> wrote: Show quoteHide quote >Hi, Ah, NOW I see what the problem is! Yes, by changing the font size I> >MM schrieb: >> On Sat, 30 May 2009 03:37:51 +0200, Ulrich Korndoerfer >> <ulrich_wants_nospam@prosource.de> wrote: >> >>> Hi, >>> >>> MM schrieb: >>> >>>> Back to that other problem, and I wonder, have you inspected the >>>> Compatibility option? I found this improved the visual look on Vista, >>>> though it doesn't make much difference on XP. I'll see if I can dig >>>> out more details tomorrow. Maybe you could email me a screenshot to >>>> depict the 'white' issue? (kylix_is@... etc etc) >>> See http://www.prosource.de/Temp/ktn.png >>> >>> The buttons also indicate problems with the screen settings. >> >> Thanks. No, I haven't seen *that* yet! Looks a bit of a mess, doesn't >> it! I'll find that Compatibility tab later and see what settings I >> tried. However, it was only to correct a little bit of flashing when >> the keyboard was scrolled. Your pic shows up a much more fundamental >> problem. > >What I am trying to tell you: your program most probably makes false >calculations regarding the sizes of several GUI elements (the white >background, the button sizes for example). The faulty display is typical >for programs that do not take correctly into account that the >environment they are running in has an other setting of the monitor-dpis >than the environment used during development. It is *not* a >compatibility problem. get exactly the same (bad) effect on my Windows 98SE PC. Dunno what to do about it, though. I've never changed font size from the default. Probably not a difficult problem to fix, but never having faced it, I don't know where to start. I'll probably have to pay more attention to ScaleWidth and -Height and paint the background(s) accordingly. Thanks! MM On Sat, 30 May 2009 03:37:51 +0200, Ulrich Korndoerfer
<ulrich_wants_nospam@prosource.de> wrote: >Hi, Further to my reply a few minutes ago, may I suggest the following?> >MM schrieb: > >> Back to that other problem, and I wonder, have you inspected the >> Compatibility option? I found this improved the visual look on Vista, >> though it doesn't make much difference on XP. I'll see if I can dig >> out more details tomorrow. Maybe you could email me a screenshot to >> depict the 'white' issue? (kylix_is@... etc etc) > >See http://www.prosource.de/Temp/ktn.png > >The buttons also indicate problems with the screen settings. Go to http://www.microsoft.com/windowsxp/using/helpandsupport/learnmore/appcompat.mspx and scroll down to Set Compatibility Properties Manually. The picture shows the Compatibility being set to Windows 95. I suggest you try Windows 98. I believe I also checked the box marked "Disable visual themes" when I last saw a problem. MM On Sat, 30 May 2009 03:37:51 +0200, Ulrich Korndoerfer
<ulrich_wants_nospam@prosource.de> wrote: >Hi, This is the update to the Readme.Txt file, under Troubleshooting, as> >MM schrieb: > >> Back to that other problem, and I wonder, have you inspected the >> Compatibility option? I found this improved the visual look on Vista, >> though it doesn't make much difference on XP. I'll see if I can dig >> out more details tomorrow. Maybe you could email me a screenshot to >> depict the 'white' issue? (kylix_is@... etc etc) > >See http://www.prosource.de/Temp/ktn.png > >The buttons also indicate problems with the screen settings. of today: ================================================================ If the program's screens do not 'look right' on your PC, please bear in mind that it was developed with Windows 98 Second Edition. Windows XP and Vista provide a Compatibility feature to help ensure that older programs (older in terms of the operating system used for development) continue to run. You can search for Compatibility in Windows Help, but for a quick exercise, try this to improve the appearance of the program if it doesn't look like the image on the Know The Notes web site: Go to the program's shortcut. This is the entry Know The Notes on your Start/Programs menu, or maybe another shortcut on your desktop if you have created one. Right-click on the shortcut and select Properties at the foot of the menu that appears. You'll now get another pop-up with several tabs, one of which is Compatibility. The first section on this tab is Compatibility mode. I suggest you first try selecting: Run this program in compatibility mode for Windows 98. If that doesn't help, try checking the box marked Disable visual themes. You can mix and match the various options until you find a combination that works better for you. The setting(s) you choose will be remembered the next time you run Know The Notes. ================================================================ MM 
Other interesting topics
Control Focus
Help using SendMessage() function can the loading of a large number of records go as quick as in DOS Auto Spacing Labels in 2D Graph What is Sendkeys Chr(188)? FMLabs FMTKit functions BigInteger and BigDecimal [equivalents] for VB.NET? Is using raw, uncooked Winsock so bad? NewEnum in Interface Font Scaling |
|||||||||||||||||||||||
