I have several programs created with Visual Basic 3.0 under Windows XP.
These required the file vbrun300.dl in the folder Windows/System32.
When I got a new PC with Windows 7 I did not install the Visual Basic 3.0 program. All I did was
copy the .exe programs and vbrun300.dl from the old PC. The programs have been working just fine
until a few days ago when I get the error message "Unexpected error; quitting" when I try to run
any of the programs. My wife also get the same error on her Windows 7, and her PC also contains
just the .exe programs and vbrun300.dll. I suspect the problem is due to a recent Windows update.
Any suggestions?"
If it is the same issue there seems to be a fix there:
After installing KB4522741 and KB4522355 the problem at my Machine Win10Pro, 32bit with old 16-bit programs (unexpected error;quitting) is gone.
Hope this helps.
No idea whether that fix was available for Windows 7. Considering that Win7 is on its last leg of extended support in its dying days you might want to grab it now if it does exist.
dilettante, thanks for your reply.
I don't have update KB4517389. Looks like that is a just Windows 10 update.
My only recent Windows 7 updates are on Oct. 12:
Update for Microsoft.NET Framework 4.8 (KB4515847)
Security Update for Microsoft Windows (KB4519976)
Before these my VB programs ran successfully.
Should I try uninstalling either or both of these? If that doesn't fix the problem can I re-install the updates?
Should I try uninstalling either or both of these?
Sounds dicey. Little reason to think it will help because all you have to go on is the approximate coincidence in time.
Originally Posted by sandbox147
If that doesn't fix the problem can I re-install the updates?
I would think they'd be offered again by Windows Update within hours unless you blocked them. Considering how slim the thread of hope is that these would help I wouldn't bother uninstalling them.
This may not help solve your problem, but whilst it is still in my 77 year old memory, I will pass it on -
VB3 was 16 bit
If you still have the source code for those programs, you could upgrade them to 32bit.
You may need another PC, to install VB4 for doing this magic.
VB4 could import (open) 16 bit VB3 source code, and could compile it as 32 bit VB4
All advice is offered in good faith only. You are ultimately responsible for the effects of your programs and the integrity of the machines they run on. Anything I post, code snippets, advice, etc is licensed as Public Domain https://creativecommons.org/publicdomain/zero/1.0/
This may not help solve your problem, but whilst it is still in my 77 year old memory, I will pass it on -
VB3 was 16 bit
If you still have the source code for those programs, you could upgrade them to 32bit.
You may need another PC, to install VB4 for doing this magic.
VB4 could import (open) 16 bit VB3 source code, and could compile it as 32 bit VB4
If memory serves it could only open them when they were saved as text [default for VB3 was binary]
VB4 supported both 16 and 32bit apps. Those written in VB3 would be loaded as 16 bit. I can't remember if there was an option to have vb4 try and replace all of the vbx files and upgrade to 32 bit, if so it would have issues if 3rd party vbx files were in use. VB4 did include some ocx files to upgrade popular 3rd party vbx but there were many that had no upgrade path.
If memory serves it could only open them when they were saved as text [default for VB3 was binary]
VB4 supported both 16 and 32bit apps. Those written in VB3 would be loaded as 16 bit. I can't remember if there was an option to have vb4 try and replace all of the vbx files and upgrade to 32 bit, if so it would have issues if 3rd party vbx files were in use. VB4 did include some ocx files to upgrade popular 3rd party vbx but there were many that had no upgrade path.
I started learning VB with VB3, so I doubt that I changed the default saving method.
I had no problem loading all of my VB3 projects into VB4.
Yup, all the extra VB3 controls/dependencies that I had added, had to be replaced with 32bit equivalents, but -
'Life was not meant to be easy',
Rob
It has been a while but I am pretty sure that only VB3 can properly open a VB3 source file that was saved in binary format and am sure binary was the default.
I changed my copy to always save in text format soon after I saw it was an option. Sometimes is nice to be able to open the mak file with notepad and have a look.
Reply With Quote
Originally Posted by sandbox147
