Re: Poor real time operation in DOS emulation mode




<junkawat@xxxxxxxxx> wrote in message
news:1190769661.624693.309260@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On 22 ñôèîáø, 03:45, "V Green" <van...@xxxxxxxxxxx> wrote:
"PSRumbagh" <PSRumb...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message

news:86577F1B-3729-4093-B9BD-0FF98D6BF876@xxxxxxxxxxxxxxxx

My Compaq Presario V2000 laptop does not have a floppy drive. I made aDOS
6.2 start up CD-ROM for the Presario on my old HP Pavilion 6465 desktop
(Circa 1999) which runs on Win98. I set the Presario's BIOS to look first
at the CD-ROM. The laptop did boot but the C: drive was not available as it
is NTFS. I put QB V4.5 and the data aquistion program, written in QB, on
the
boot CD. Although the program sort of ran, it could not access the PCMCIA
to
IEEE-1284 card. This is not the way to go. So, I will run the QB program on
the old HP Pavilion under a trueDOSboot as it's C: drive is not NTFS. This
is progress?

Yeah, I know...

On older laptops with PCMCIA cards, there wereDOSdrivers
for the PCMCIA controller and then another driver for whatever
card you stuffed into it.

Those days are long gone, I am afraid, unless you can find a combo
of old stuff that will work. Ebay might be your friend here...







"V Green" wrote:

Try making a floppy "Startup Disk" in W98,
boot off that and try your app again.

If it's still choppy, you need to jump into the
Wayback Machine and find "real"DOSsomewhere.

"PSRumbagh" <PSRumb...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:372BFAD0-5834-4092-A6E3-3DF43E596615@xxxxxxxxxxxxxxxx
I have a HP Pavilion 6465 (Circa 1999) desktop that runs on Win98. If I
hold
down the "F8" key on bootup I have a choice of booting in Win98, Win98
safe
mode or "Command Prompt Only". Is the Command Prompt Only selection a
real
DOSor an emulatedDOS? It loads very fast (less than 1 second). Typing
VER
at the prompt returns Windows98 (Version 4.10.1998). It seems that my
data
acquisition program written in QB V4.5 runs with a less choppy output,
but
not perfect.

"HeyBub" wrote:

PSRumbagh wrote:
I have a data acquisition program written in Quick Basic V4.5 that
I
want to run in theDOSemulation window of WindowsXP. The program
outputs 8 bits of data at a continuous rate of 4 KSPS to a DAC for
real time waveform generation. The program works OK in a true, pure
DOSenvironment where it produces a smooth, continuous waveform.
Under WindowsXPthe data comes out in spits and spurts, not
continuously. It appears as though Quick Basic V4.5 is getting
about
1.25% of the microprocessor's core time and the DAC output is very
choppy. WinXP'sTask Manager says there are 63 processes running in
the background. Is this intermittent, choppy operation because of
the
multi-tasking nature of WinXP? Is there any way to make thisDOS
application work in apparent real time under WinXP? I am using
Tame-Dosto speed up theDOSapplication and reduce the
microprocessor loading.

No. By definition,XPis a pre-emptive multi-tasking operating system
(Win98
was the first).XPwill time-slice available CPU cycles between active
tasks, including those that are just waiting, such as checking to see
if
the
mouse moved in the last few nano-seconds.

You need a dedicated computer runningDOS(notXP).

Pay no attention to those who swear a Linux box will do the job.

Fortunately for you, I have a COMPAQ Portable II (286) that I'll be
willing
to let go for $200.-äñúø è÷ñè îöåèè-

-äøàä è÷ñè îöåèè-

For a complete solutions Checkout
http://www.taocomputers.com/english.asp
their company is called Tao Computing Solutions. They have a product
called Tao ExDOS, it's basically a
-----------------------
<DOS emulator>

You really have NO idea what PS's problem
with XP DOS is do you?

If you did you would realize how irrevelvant your
SPAM post is.

Clue: HE ISN'T PRINTING!
----------------------

that solves all these
problems on Windows 2000/Windows XP/Windows 2003 and Windows Vista.

All printing problems including USB printers, Win only printers that
do not support text ROM fonts. Terminal Server Printing redirection,
support for all codepages, direct access to hardware, parallel
dongles, parallel ports, serial ports, full screen font/s, CPU
Resource manager, Terminal Server full support, Terminal Server
Printing redirection, Full screen emulation on Vista's Aero interface,
Printing to LPT1-LPT9, Support for console applications, They have a
Lite version which captures all printing from DOS applications 100%
with no TSR's to bug you and use up memory. MINIMAL CPU USAGE ! ! The
software takes care of all CPU issues. You will never get 100% CPU
Used with this software.There is an option to directly from DOS to
Microsoft Word, HTML, RTF, TXT using the correct codepages, fonts and
pagination. AMAZING!!! everything I needed in one product. we can all
keep working with DOS for several years more.


.



Relevant Pages

  • Re: Poor real time operation in DOS emulation mode
    ... problems on Windows 2000/Windows XP/Windows 2003 and Windows Vista. ... do not support text ROM fonts. ... Terminal Server Printing redirection, ... MINIMAL CPU USAGE! ...
    (microsoft.public.windowsxp.general)
  • Re: Poor real time operation in DOS emulation mode
    ... problems on Windows 2000/Windows XP/Windows 2003 and Windows Vista. ... do not support text ROM fonts. ... Terminal Server Printing redirection, ... MINIMAL CPU USAGE! ...
    (microsoft.public.windowsxp.general)
  • Re: Local Printing with IE
    ... The problem may be that the CE5 does not support such type of printer. ... but installing serial port sniffer between printer and your ... printing support component to your platform in PB? ... I hope that the debug messages will indicate anything ...
    (microsoft.public.windowsce.platbuilder)
  • Re: [S] main-xaw.c
    ... we haven't removed support for it completely either. ... The real problem is actually printing anything useful on it. ... Because Russian language happens to use those funny Cyrillic letters, ... it looks like I just have to copy PostScript fonts from ...
    (rec.games.roguelike.angband)
  • RE: Printing from ASP.NET application
    ... when performing printing on ASP.NET web page,correct? ... server-side .NET code that deal with printer will only affect the server ... Microsoft MSDN Online Support Lead ... I don't want the end user to have to view the report and then select the ...
    (microsoft.public.vsnet.general)