🚀 go-pugleaf

I believe the difference is that VB/DOS produces only DOS executable
code whereas VB/WIN oly creates Windows code.  The language
should be the same (except of course for the windowing functions)
It just depends on where you want your end Apps to run.


               -Joel

In article <2gsbbu$6ht@Ra.MsState.Edu>, jkm2@Ra.MsState.Edu (Joseph K Mcallister) writes:
|> I believe the difference is that VB/DOS produces only DOS executable
|> code whereas VB/WIN oly creates Windows code.  The language
|> should be the same (except of course for the windowing functions)
|> It just depends on where you want your end Apps to run.
|>
|>
|>                -Joel

 I have only started learning how to use VBDOS last week, but I have
 seen VB-Windows, and the major difference I note is the difference in
 the actual programming/editing environment...but the more I think
 about it, only Running in Windows could you use the VB-Windows code.

                                                     Nick Doan.
--
- Have you ever seen a bear combing his hair?
   Have you ever seen a whale with a polka-dot tail?

In article <2gsbbu$6ht@Ra.MsState.Edu> jkm2@Ra.MsState.Edu (Joseph K Mcallister) writes:
>I believe the difference is that VB/DOS produces only DOS executable
>code whereas VB/WIN oly creates Windows code.  The language
>should be the same (except of course for the windowing functions)

There are also a bunch of other differences between the languages
which pop up when you are porting from one to the other (commands
which behave differently, for instance). These are documented in the
VB/DOS manual. The interface design in VB/DOS is also not as slick as
that in VB/WIN (being DOS) -- for example, I don't think you can
create or use any kind of icon readily in VB/DOS.

/Matthew

--
Matthew Cravit                      | All opinions expressed here are
Michigan State University           | my own. I don't speak for Michigan
East Lansing, MI 48825              | State, and they don't speak for me
E-Mail: cravitma@cps.msu.edu        | (thank goodness).

In article <2gsipu$na4@msuinfo.cl.msu.edu>, cravitma@arctic.uucp (Matthew B Cravit) says:
>
>In article <2gsbbu$6ht@Ra.MsState.Edu> jkm2@Ra.MsState.Edu (Joseph K Mcallister) writes:
>>I believe the difference is that VB/DOS produces only DOS executable
>>code whereas VB/WIN oly creates Windows code.  The language
>>should be the same (except of course for the windowing functions)
>
>There are also a bunch of other differences between the languages
>which pop up when you are porting from one to the other (commands
>which behave differently, for instance). These are documented in the
>VB/DOS manual. The interface design in VB/DOS is also not as slick as
>that in VB/WIN (being DOS) -- for example, I don't think you can
>create or use any kind of icon readily in VB/DOS.
>
>/Matthew
>
>--
>Matthew Cravit                      | All opinions expressed here are
>Michigan State University           | my own. I don't speak for Michigan
>East Lansing, MI 48825              | State, and they don't speak for me
>E-Mail: cravitma@cps.msu.edu        | (thank goodness).


One thing that I have found is that VBWIN has been denuded of a lot of
powerful function calls that help in working with binary data.  (e.g. MKI$,
MKS$, MKD$, MKL$, CVI, CVL, CVD, CVS, PEEK, POKE, IN, OUT, etc.)

Anders

Major differences VBDOS / VBWIN:

- VBDOS will produce code that runs under DOS, on any 8086-based computer
  with acceptable speed. VBWIN doesn't.
- VBDOS will produce real executables. VBWIN doesn't.
- VBDOS includes a powerful ISAM database tool. VBWIN didn't up to 2.0;
  I dont know anything about the database control.
- VBDOS operates ONLY in text mode. You can switch to graphics mode, but
  then you can't use any of the forms and controls.
- VBDOS is fully BASIC PDS and QB compatible. VBWIN isn't.
- VBWIN lets you send vector output to the printer connected without
  bothering what type of printer it is; the windows driver does the rest.
  VBDOS only lets you send data directly to the printer, so you'll have
  to write pritner drivers yourself.
- VBWIN is kind of "obejct oriented", as you can create variables of type
  "Form", "Control" or any form name and have as many forms of the same
  kind displayed as you like. In VBDOS, you'll have to design every single
  form you want to use and assign it a name. No way to display two instan-
  ces of the same form.
- VBDOS has the DOS 640 KB memory limitation. VBWIN hasn't. On the other
  hand, VBDOS lets you manipulate memory & interrupts, VBWIN doesn't.
- VBDOS lets you create your own controls easily (some ASM required, but
  *really* only some).

That's all that comes to my mind for now. The biggest disadvantages of
VBDOS are the missing object-oriented concept and the printer driver
hassle. On the other hand, for many applications Windows is just a bit
"too big". VBDOS executables have the potential to execute faster be-
cause they're *real* executables and they can easily include ASM code,
while VBWIN has to deal with all the Windows procedure overhead.

DOS is not dead. As recession strikes, you'll not find a 486 machine
that easily runs your VBWIN application everywhere. And customers won't
be pleased if you tell them they have to install Windows on their 40
meg 286 Hercules machine only to run the small address databease you've
programmed. That's why I still like to use VBDOS.

Greetings
Fred

--
Frederik Ramm  ##  eMail ule3@rz.uni-karlsruhe.de  ## fax +49 721 379786