Does anybody know where I can get the original Windows 95 Platform SDK (or Win32 SDK)? I need it for the Windows 95 DDK (driver development kit). Thanks!
Here's February 2003 Platform SDK which supports Windows 9x (though I don't know if it works with Windows 95 DDK):
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.1.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.2.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.3.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.4.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.5.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.6.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.7.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.8.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.9.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.10.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.11.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.12.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.13.cab
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.bat
http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/extract.exe
(links taken from https://docs.moodle.org/dev/FebruaryPlatformSDK)
WinworldPC has beta Win95 SDKs:
https://winworldpc.com/product/windows-sdk-ddk/windows-95-ddk
There is also a "16-bit SDKs" package under "Tools and Resources" on the MSDN Subscriber downloads in case you have a subscription, but it does not seem to include the Windows 95 SDK.
I think MSDN subscriptions downloads area usually has stuff like this, though Windows 95 is pretty ancient; I'm not sure you're going to be able to find it easily.
Try googling "A8ACFA3DD1468C7281C4D2F152364585346E0C10". Don't know how "legal/legit" this is though. Use at your own risk.
I've found a good link on installing the two (SDK and DDK) but I can't find the SDK anywhere. I looked at my old VB6 install, but it doesn't look like it's on that disk. I'll keep on looking. See this for installing the two, together:
http://www.geoffchappell.com/viewer.htm?doc=notes/windows/archive/pdk.htm
Related
while understanding the differences between 10.0.19041.0 and 10.0.22000.0 SDK ,I encountered
https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/ this page. After looking into it , I understood 10.0.22000.0 is mainly for windows 11 applications .
If we select 10.0.019041 as the package and build the application, won't it run on windows 11.
If we want our application to be run on windows 11 do we need to choose 10.0.22000.0 over 10.0.19041.0.
Please correct me if my understanding is wrong.
Thanks for the help!
TLDR: No, your understanding is wrong. You can likely use whatever version you want and your application will run on both, Windows 10 and Windows 11.
Long with details:
It's true, the 10.0.19041 SDK is for Windows 10.
It's also true, 10.0.22000 SDK is for Windows 11.
Let's have a look from a user perspective:
When you download software, how often do you need to select the correct operating system? Not very often. So, somehow, the SDK version does not seem to be very important.
Let's have a look from a Microsoft perspective:
Does Microsoft want all developers require a rebuild of their Windows 10 programs once they release Windows 11? Certainly not, because this would mean that with the release of Windows 11, there wouldn't be a single application which runs on Windows 11. Microsoft couldn't even perform inhouse tests for multi-million-user software such as Adobe Reader.
Let's have a look from a technical perspective:
The Windows SDK provides the API definitions of Windows. The Windows API is very old. And since Microsoft does not want developers to rebuild and, even worse, let them fix breaking changes, Microsoft keeps that API incredibly stable. They will not change the API, they will only add new API methods.
The chance that the Windows API you use already existed in Windows 10 and still exists in Windows 11 is almost 100%. So your application compiled for Windows 10 will still work on Windows 11.
Likewise, if you compile with the Windows 11 API and don't use the most recent fancy API, your application will still work on Windows 10.
Example
Let's say you developed an application that manages Fonts. You have used the interfaces IDWriteFontSet, IDWriteFontSet2 and IDWriteFontSet3. With Windows 11, Microsoft has added IDWriteFontSet4. As long as you don't use that interface and stick to the previous 3 interfaces, your application will run fine. Once you start using IDWriteFontSet4, your application may crash on Windows 10 (potentially only if the user invokes the functionality, not so sure).
I just downloaded and tried to install the 'Rosetta' rough sets tool on my laptop with OS Windows 10, but I can't. And after I search, it seems only compatible for Windows 98 / XP. But the problem I saw in the video tutorial is that anyone can run it on an OS that looks like that. Does anyone know of a solution to being able to use Rosetta on Windows 10?
Error message when I install Rosetta
I have just solved this problem after many days of googling and trying various ways. I use the "Run programs made for previous versions of Windows" feature in the control panel, then troubleshoot. I have also written down the step I did on that, and I uploaded in my medium story, but in "Bahasa Indonesia". So if you want to read it, you can translate it into English first to understand.
The medium link below:
https://medium.com/#andini.pratiwi/tidak-bisa-install-software-old-version-karena-tidak-compatible-dengan-os-windows-10-solusinya-1d8820c71572
First of all: I know that Windows XP is end of life, insanely insecure, a big risk and that everyone still using it will be doomed for ever.
Nonetheless I have to provide an application that can also run on Windows XP and I do so using Go.
In 1.10 it was announced that XP will no longer be supported and 1.11 confirms this in the release notes:
As announced in the Go 1.10 release notes, Go 1.11 now requires
OpenBSD 6.2 or later, macOS 10.10 Yosemite or later, or Windows 7 or
later; support for previous versions of these operating systems has
been removed.
I compiled my application with 1.11 and tried to execute it on a Windows XP SP3 virtual machine. It could be executed successfully !
Then I thought that the revoked support for Windows XP only applies to the development toolchain but even that can still be executed on Windows XP:
As you can see the main go binary still runs on XP too. Is it already known when it will no longer be possible to run golang compiled exes on Windows XP because of technical limitations or if certain methods will fail because they can no longer work because of missing APIs on XP ?
Issue #23380 is the relevant discussion.
In short:
Note that even if 1.10 is the last version to support XP, you'd get bugfix backports until 1.11 is out, and security backports until 1.12 is out. That means until January 2019 <…>
As to supporting Windows XP, there are both technical and non-technical reasons.
Supporting a platform requires:
Someone who has access to it, and an incentive to work on it
(either paid or unpaid).
The most active Go-on-Windows developer, Alex Brainman,
seems to have no interest in XP anymore.
This platform must be supported on autobuilders which are part of the Go release / QA process.
An autobuilder must be supported by someone.
Bugs specific to a platform must be fixed and tested.
For instance, that issue refers to #23375 which happens only on Windows XP (SP3).
But even if a bug was specific to Windows in general—as opposed
to Windows XP, a fix for it would have to be tested on XP anyway.
Hence, unfortunately, if there is no interest in supported Go on Windows XP coming from some "powerful entities"—such as corporations—the best you can do is to actually work towards still supporting this by yourself, FWIW.
Also note that even after the support is officially ended, you still might have success building newer Go releases from the source (which is reasonably simple since Go 1.5 as Go is now built using (an older release of) Go).
Hence a real show-stopper would be the Go team hitting some roadblock which would just require some kernel feature not present in Windows XP.
A good example was some difficulty with SEH handling on Windows 2000 which eventually led to dropping support for that OS.
One of the components in my application is failing on Windows because Windows K/KN systems don't have Media Feature Pack installed. To prevent this I was thinking of adding a check during install time to see if Media Feature Pack is installed on the current system. However, I haven't found enough information about MFP to do so.
For most versions of Windows it's already installed but some Windows 8 and 8.1 installations don't have it. I need a programmatic way to do this.
I would need any one of the info to achieve this:
Regkey based
What are the regkeys that can be used to determine if Media Feature Pack is installed? Does Media Feature Pack (like .NET framework / VC redistribution) set some regkey which can be used to determine this?
Is there any API that can be used to detect Media Feature Pack?
Are there any DLLs that can be used to for detection?
I know mf.dll and mfplat.dll are installed in sys32 folder, but can I rely on these two files for MFP detection?
Found the answer and posting here if helps someone
There is a registry key at:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\WindowsFeatures\WindowsMediaVersion
Some links:
http://support.microsoft.com/kb/922474
This will help you detect the actual windows flavor:
http://msdn.microsoft.com/en-us/library/ms724358%28v=vs.85%29.aspx
http://msdn.microsoft.com/en-us/library/aa394239%28v=vs.85%29.aspx
Got to Control Panel > Programs > Turn Windows Feature On/Off
in my case it's installed. You can also install by marking on it. then hit OK
If I build a hello world application using a modern version of Qt4, what would be the minimum version of Windows my program could work on?
Would it work on Windows 2000, or even on older releases, like NT or Win95?
hard to say since QT is an open source project and you also need to consider the compiler as possible variant, but there are solutions even for Windows 98 Compiling Qt for Windows 98 and Windows 2000/NT is still supported on really recent releases like the 4.7 and 5.0 is supporting them as well.
I suppose that the real issue is Windows 95, but you really need Win95 ?
This days there are free OS that are production ready and user-proof.
Sometimes you will find references to Windows 95 in the QT wiki like at the bottom of this page, but at least for the 4.x branch it's unclear if it's supported or not, the branch 4.x is capable of supporting up to Windows ME, at least according to the platform notes from QT/Trolltech.
Probably with something like the version 4.3/4.4 you can get a QT environment under Windows 95.
EDIT
answering to your edit I will say that supporting Windows 2000/NT it's not an issue, supporting older OS will require a downgrade for your QT version and Windows 95 it's a lottery.
Look at the supported platform notes. If the OS is not in Tier 1 or 2 then you should just try and see.