News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests
NB: Posting URL's See here: Posted URL Change

Main Menu

Instruction Set detection for 32 bit Operating Systems

Started by Gunther, February 03, 2013, 08:24:36 AM

Previous topic - Next topic

FORTRANS

Hi,

Quote from: Antariy on May 08, 2014, 03:36:34 AM
Maybe the reason is really in the console programs?

   Yes, it is looking like console programs are not supported.  Could
not even find an MS-DOS command prompt/box.  Oh well.

Quote from: hutch-- on May 08, 2014, 03:45:28 AM
Just vaguely I remember that you needed a specialised linker to build a win32S application.

   Well the program that worked with Win32s was linked with the
linker that came with MASM32.

Regards,

Steve N.

Gunther

Hi Steve,

Quote from: FORTRANS on May 08, 2014, 05:53:51 AM
Quote from: hutch-- on May 08, 2014, 03:45:28 AM
Just vaguely I remember that you needed a specialised linker to build a win32S application.

   Well the program that worked with Win32s was linked with the
linker that came with MASM32.

that could perhaps help a bit.

Gunther
You have to know the facts before you can distort them.

dedndave

i seem to recall we went through all this 5 years ago when i was working on the OS ID stuff   :P
http://www.masmforum.com/board/index.php?topic=11963.msg91220#msg91220

FORTRANS


Gunther

Dave,

Quote from: dedndave on May 08, 2014, 06:09:59 AM
i seem to recall we went through all this 5 years ago when i was working on the OS ID stuff   :P
http://www.masmforum.com/board/index.php?topic=11963.msg91220#msg91220

yes, excellent power of recall. :t

Gunther
You have to know the facts before you can distort them.

FORTRANS

Hi,

QuoteCould not even find an MS-DOS command prompt/box.

   Well, that was stupid.  Just find something that can run a program,
and launch COMMAND.COM.  In a VDM it is the same as a direct
invocation of a VDM.  With MS-DOS and Win 3.11, you lose a bit of
usable memory compared to pure DOS, but you get prompt of
the hot keys to switch back to Windows.

Regards,

Steve N.

dedndave

not sure i understand what you're saying, Steve
as i recall, to get a command prompt in win 3.1, you exit windows
it is essentially a shell that runs under command.com
it's been a long, long time - and i wasn't much of a win 3.1 fan back then
so, i may have the facts thoroughly mangled - lol

hutch--

Dave,

Under Win3.0/1/11 you could get an instance of command.com while in Windows, it had less memory than a direct instance of command.com in DOS but did most things OK. If you wanted the real McCoy you exited Windows to DOS. There were the odd situations that Windows squarked at with a DOS prompt which followed from its ugly cooperative multitasking and if you needed some direct hardware access you had to exit to DOS.

Gunther

Steve,

Quote from: FORTRANS on May 08, 2014, 11:40:45 PM
   Well, that was stupid.  Just find something that can run a program,
and launch COMMAND.COM.  In a VDM it is the same as a direct
invocation of a VDM.  With MS-DOS and Win 3.11, you lose a bit of
usable memory compared to pure DOS, but you get prompt of
the hot keys to switch back to Windows.

would it be a better solution to compile the entire thing with a 16-bit C compiler (for example Turbo C) and link against the 16-bit assembly procedure? All that Jazz with Win32s.

Gunther
You have to know the facts before you can distort them.

FORTRANS

Hi Gunther,

   Well if you want the results from a Pentium, go ahead.  I
don't think a Win32s console program is going to work.  I was
just trying things out just to see if I could get things working
with Win32s, and got a bit carried away.  Well I did get the
one example program to work.

Regards,

Steve N.

Gunther

Steve,

Quote from: FORTRANS on May 09, 2014, 07:05:56 AM
Well I did get the one example program to work.

no offense. It was just an idea. But your result sounds optimistic. Do you think that the other applications will work, too?

Gunther
You have to know the facts before you can distort them.

FORTRANS

Hi Dave,

Quote from: dedndave on May 09, 2014, 02:32:33 AM
not sure i understand what you're saying, Steve
as i recall, to get a command prompt in win 3.1, you exit windows
it is essentially a shell that runs under command.com

   Hutch explained it pretty well.  And I had never used a DOS
session under Windows 3.x, (IIRC...).  Which is why I could not
figure out how to do it.

Regards,

Steve N.

FORTRANS

Hi Gunther,

Quote from: Gunther on May 09, 2014, 07:09:52 AM
no offense. It was just an idea.

  And probably a good one if want to run any tests on my plain
Pentium systems.  The Pentium MMX with Win 98 works for
most programs now.  And it should show identical cycle results
anyway.

QuoteBut your result sounds optimistic. Do you think that the other applications will work, too?

   Well I got a dialog program to work, maybe something
could be made to work that way.  And write the results to
a file.

   I just got involved for the idea that it might be a way to
get me to start programming in the 32-bit world.  Win32s
has been a fun diversion if nothing else.

Regards,

Steve N.

Gunther

Hi Steve,

Quote from: FORTRANS on May 09, 2014, 07:29:52 AM
  And probably a good one if want to run any tests on my plain
Pentium systems.  The Pentium MMX with Win 98 works for
most programs now.  And it should show identical cycle results
anyway.

yes, but I need a few days for finishing the 16-bit version.

Gunther
You have to know the facts before you can distort them.