It will run on Win95. I know this because I have tested it. Of course, you didn't expect it to run on a 16 bit OS like Win3.1 right?
Also, I know how to program in VB better than most people can. I've talked to people that have earned various degrees in VB that couldn't tell me the first thing about the Declare Sub/Function statement (which is the primary mechanism to access external native code - eg. The Windows API's). If you know what you're doing, it will run pretty fast.
Of course the language is part of it (many parts of the program are not totally compiled, it is somewhat "scripted", you could say, as in it doesn't make calls directly to Windows, it calls thru the VB runtime.
Yes, I could write it in <insert your language here> but no, I don't want to take the time to learn it. Yes, maybe it's faster/better/whatever it is but I don't have any time anymore to learn lots of new computer stuff, so I stick with what I'm good at. Which is VB, HTML, PHP, some C/C++, Java, and Asm thrown in for good measure.
The map editor will run faster and more error free if you can meet certain requirements, like these (these are from the machine that was used to compile and develop it.)
- WinXP Pro (it was initially compiled on a Win98 without problems)
- 333mhz Pentium-II
- 192MB ram
- at least 100-200 mb of virtual memory available on the drives
- video card made after 1998
- closing all unneeded programs, like IE, AIM, etc. before running the editor.
- Up to date versions of all the common components (MS common controls, etc), updates to the OS, updated drivers.