http://www.eweek.com/article2/0,1895,1930314,00.asp
http://www.eweek.com/article2/0,1895,1930303,00.asp
New Windows Vista build 5308 - 22 Feb 2006
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Hello!
It seems that 16-bit applications are working OK.
I was able to build 16-bit FiveWin application with
Clipper and Blinker. When starting resulting EXE,
the following message appeared:
"NTVDM encountered a hard error".
and then:
"Cannot find file ... (or one of its components).
Check to ensure the path and filename are correct
and that all required libraries are available."
Using Filemon ( http://www.sysinternals.com/Utilities/Filemon.html )
I noticed that it tried to open COMMCTRL.DLL. After copying
that file to \windows\system\, application functioned OK.
Long live 16-bit applications (Just joking!),
Roman
It seems that 16-bit applications are working OK.
I was able to build 16-bit FiveWin application with
Clipper and Blinker. When starting resulting EXE,
the following message appeared:
"NTVDM encountered a hard error".
and then:
"Cannot find file ... (or one of its components).
Check to ensure the path and filename are correct
and that all required libraries are available."
Using Filemon ( http://www.sysinternals.com/Utilities/Filemon.html )
I noticed that it tried to open COMMCTRL.DLL. After copying
that file to \windows\system\, application functioned OK.
Long live 16-bit applications (Just joking!),
Roman
© I'm not patented!
- Antonio Linares
- Site Admin
- Posts: 37481
- Joined: Thu Oct 06, 2005 5:47 pm
- Location: Spain
- Contact:
Yep, it works without commctrl.dll with February build.Antonio Linares wrote:The most recent FW 2.7 does not need that DLL.
Here are the 16 and 32 bit "About" boxes:
BTW, it's funny to see "DOS 5.0" in Vista, which is returned
by OS() function in 16-bit version of FW. (this is probably
because of NTVDM). Is there a simple way to get version
of real OS in 16bit FW?
Regards, Roman
© I'm not patented!