Well, as some remember, there was a discussion in this thread: viewtopic.php?f=6&t=19121 about the MSDN version of Windows 3.1 Farsi that is corrupted. I have to say I tried to get that one to work myself - I managed to get it to run by replacing its GDI.EXE with the one from the Arabic version but the characteres were all gibberish and it would obviously freeze with its own GDI.EXE.

Now a week ago I found a non-MSDN version of Windows 3.1 Farsi on a Google search. And surprisingly, it works. It installed without problems and booted without problems too.

Here's some screenshots:


.

The OS itself has been uploaded and is waiting in the queue for its turn to be released.

Well, I'm sure that mrpijey will be glad to upload this to the BetaArchive FTP server, since that's what he usually does when such releases are made, even if and when they are rereleases of something where the only other copy available was damaged (such as this Farsi release of Windows 3.1).

Well I've just verified both versions of Farsi Windows 3.1, and I've determined the following:
1. The MSDN one is version 3.1.127, while the non-MSDN one is version 3.11;
2. The MSDN one has fonts provided by Glyph Systems, while the non-MSDN one seems to have fonts provided by Microsoft themselves;
3. The two versions are mutually compatible (using the non-MSDN GDI.EXE on the MSDN version still produces gibberish characters).

So it seems we have two different versions at hand.

That's great, thanks...

great, another one for my collection!

Looks interesting...
I might give a chance to this.

Great! Ill try it for sure

The English resource says "Arabic fonts supplied by Glyph Systems", the biggest possibility is they hacked their own Arabic windows 3.11 to farsi. The evidence is they don't even change "Arabic" to "Farsi" in readme.wri!


and of course the charset convertor (convert.exe) of 3.11 version is Arabic one. Farsi has different encodings.

BTW this non-MSDN Farsi Windows 3.11 has a thin type of System font and FixedSys font.