Hi Mark,
Interesting that you had problems with VB 6. I used Visual Studio 6 under XP
with no problems. Have not tired it under my new installation - I installed
VS.NET 2003 instead.
Regarding Calendar Creator, it is an application designed to run under
Win9x, ME, and NT, but not XP. It is strange that an ap designed for NT will
not run on XP, but that is the case here. I did try using the compatibility
mode - Win95, Win98, ME, and NT, but the results were the same with any of
them. Also tried to run with 256 colors and turning off other features. None
of this made a difference.
I also have VMWare and did install CC 6 in an ME VM. The only problem with
doing that is that my network printer does not work correctly with the VM.
That is a separate issue that I might address later. For now, I "solved" the
problem by purchasing version 9 of Calendar Creator for only $4.23 including
tax and shipping from Surplus Computers that Cuffy10 of this list pointed me
to.
I am not sure that the security patch theory is the answer. The program did
not run in an older install of XP under my VMWare. I will do some more
poking just to satisfy my own curiosity.
Peter
----------------------------
[log in to unmask]
-----Original Message-----
I have had this experience with Visual Basic PRO 6.0 . I suspect it has
something to do with a security patch. In your old XP install, the program
was probably installed prior to the patch, and in the new install it was
installed after you patched the OS. I think the answer lies in "when" the
program was installed relative to the patches.
How "old" is it. Have you tried telling XP to run it in it's own memory
space and treat it as a 16 bit application?
When I run in to this, and it is a application that I use infrequently, I
will run it in a virtual machine with VMWare, in 98 or Win2000. In fact,
that has been my solution for VB PRO 6.
Rode
The NOSPIN Group has added a new feature on our website,
web based bulletinboard for questions and answers:
Visit our sister website at http://nospin.com
|
