Project Complete how can convert .exe file and run all windows

I have finished my work Now I want to make it a software (.exe) then go to all OS.
I.e.

Windows 10
Windows 2000
Windows 2003
Windows 3.X
Windows 7
Windows 8
Windows 95
Windows 98
Windows CE
Windows ME
Windows NT
Windows Vista
Windows XP

( i found OS name on net )

I've used this in the Declare Function
shell32.dll
advapi32.dll
user32.dll
msimg32.dll
gdi32.dll
.
Now how to change it in the way that my Project runs on every windows

i also used ( Inno Setup Compiler )

Thanks

Windows CE is not compatible with any of the other versions, there was a CE Toolkit available for VB that would allow you to build an app for a CE device but those apps are quite a bit different than a PC based App would be.

Windows 3.x is 16 bit, VB6 creates 32 bit apps so not compatiable with any windows version prior to Windows 95.

Most apps will work in any of the other windows versions provided you are not violating any of the security checks that were added after XP.

Quote:

---

Originally Posted by kako0000000

I've used this in the Declare Function
shell32.dll
advapi32.dll
user32.dll
msimg32.dll
gdi32.dll

---

This is not enough info to judge if your app is compatible with any OS version. There are multiple API functions in user32 that were added in XP or Win10 so you have to comb through all those API declares and figure out the minimal OS version any of these is supported on.

FYI, Win 9x does not support unicode version of win32 API usually.

cheers,
</wqw>

Better explain why you think you need to support all versions of Windows since 3.X

Odds are the oldest version of Windows that you are likely to see is XP. I would think it would be pretty rare to find someone still using one of the older versions and if they were then they should not be surprised when they try to run new software and it doesn't work as not only would they be using an outdated OS but also some pretty old hardware, with little ram or HDD space.

i've seen windows ce... in a milling machine but that's pretty much it. It's as defunct as defunct can be and was replaced with xp embedded. 3.1 was barely functional as an OS to start with, not even having folders. You COULD make code for it, if you managed to find a version of vb4. It could compile in 16 or 32 bit. If you were to package your dependent dlls in the same folder, it doesn't matter what version the OS has in the system folder. By default, apps use the one in the same folder if it's there. Whether your app can run on anything older than 98 depends on a lot of factors too boring to get into here involving memory allocation and supported hardware. As far as software compatibility goes though, your entire list (which oddly you alphabetized instead of sorting by age) pretty much boils down to these versions: windows ce, windows 95 (basis for 98, 98se (you forgot this one), xp, xp media center 2003, and millennium edition. You almost certainly won't get anything useful to run on versions of NT older than 5 as you can't even be sure it's an x86 processor as those were cross platform. 2000 was based on nt and xp-32 is compatible with it. xp-64 is 85% vista. Vista, windows 7, 8, 8.1, and 10 all run the same core (mostly). Even microsoft can't make apps cross-platform to all of these. You don't have a chance. Target xp and your app will "probably" work with everything newer although you better respect the file locations (only save to the user appdata).

thanks replay me
but anybody not tell me that how create .exe file who run all windows
and when anybody delete the software then delete folder
inno setup

Quote:

---

Originally Posted by kako0000000

thanks replay me
but anybody not tell me that how create .exe file who run all windows
and when anybody delete the software then delete folder
inno setup

---

The exe file is created by VB using the Make option. You can not make an exe that will work on all the versions you list, that is not possible in VB6.
As for the versions that VB can build an exe for if it works or not will depend on what your program uses and how it is written. It may work on all of them and it may not.

I would not use Inno for the setup.

Quote:

---

i've seen windows ce... in a milling machine but that's pretty much it.

---

Really, I was writing programs for Windows CE devices for about 15 years. Needless to say I have saw it on a lot of devices and used for a lot of things though VB6 is not a good choice to write anything for it. Early on I used VB5 and the CE Toolkit then quickly moved to Embeded VB3 and later moved to VB.Net. Over the last couple of years these devices have gotten more rare and Android is filling the space once held by Windows CE and Windows Mobile though there are still new devices out there with Ce on them.

@kako0000000: If you compile a new empty Standard-Exe project to Project1.exe this will run on Win9x family of OSes which include Win95, Win98 and WinME and on x86 NT 3.51 and newer which include x86 NT 4, Win2000, WinXP, Vista, Win7, Win8/8.1 and Win10.

Project1.exe will not run on 16-bit Win 3.x, any version of Win CE or non-x86 versions of NT.

So there is no telling you "how create .exe file who run all windows" as it's impossible with VB6.

To add insult to the injury, it's Inno Setup that would not run on WinCE, Win3.x and Win9x to begin with.

cheers,
</wqw>

Quote:

---

Originally Posted by Lord Orwell

i've seen windows ce... in a milling machine but that's pretty much it. It's as defunct as defunct can be a

---

As DataMiser says, Windows CE and Windows Mobile (which uses Windows CE) were widely used for mobile devices. Even today you can still buy new mobile devices which use Windows Mobile 6.x.
Windows Phone 7 broke compatibility (where have we heard that before?) and Windows Phone 8 and Windows 10 Mobile weren't successful either. Microsoft lost this market to Android devices.
Windows Embedded Handheld is a version of WM6.5

You can't use VB6 on these devices.

I don't know why the OP requires the old OSs listed, but realistically you are unlikely to see anything older than Windows XP.

Even asking about working on a operating system is insufficient, you need to know what version/service pack it is too. So the oldest Windows version you are likely to see is Windows XP Service Pack 3. Extended support for Windows XP ended in 2014.