|
-
Dec 1st, 2022, 02:28 PM
#1
Thread Starter
Junior Member
VB Continuity
I've been a VB user for nearly 20 years. In those 20 years I've had to reinstall Windows and VB many times. I just got caught with a new problem! Win7 comes with IExplorer 4.0. When you attempt a clean reinstall of Win7 it hangs up when it attempts to download Win7 Updates because IExplorer 4 isn't recognized anymore! At least that was my experience. I'm kinda stuck with several very capable computers that won't run Win11, so I expect to need the option of having a Win7 available to reinstall VB and other products in the future. I seem to remember, from the very early days, there were procedures for installing programs (making the appropriate Registry entries manually) if the need arose. I've heard that the Win11 Registry is no different that the Win10 one. With these kinds of problems in mind, is anyone interested in creating a thread to develop mechanisms/procedures for being able to maintain a method of installing Win7 so we can guarantee having VB 6.0 available? I've run most of my VB programs with Office 2017, so the current runtime libraries still work with VB 6. If anyone else shares these problems or feels they might, please let me know!
Tags for this Thread
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|