Home > Archive > Clipper > March 2005 > DOS open error 2
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| JTS Group 2005-03-15, 3:55 pm |
| Hi,
I run a DOS application created using Clipper 5.01 on a Windows ME machine
and got the error message "DOS open error 2". Can somebody tell me what
"DOS open error 2" is. The same application runs on Windows XP machines
without any problems. Are there anything about Windows ME machines that I
should watch out for?
Thanks,
Peter Tan
| |
|
| "JTS Group " <jtsgrp@singnet.com.sg> ha scritto nel messaggio
news:d16obd$s9d$1@reader01.singnet.com.sg...
> Can somebody tell me what "DOS open error 2" is.
Dos error 2 = File not found
| |
| Stephen Quinn 2005-03-15, 3:55 pm |
| Peter
> Are there anything about Windows ME machines that I
> should watch out for?
Yes - the fragility of the OS.
--
HTH
Steve
| |
| tom knauf 2005-03-16, 8:55 am |
| Hi,
I remember that ME on every startup replaces autoexec.bat and config.sys
with empty dummys, so if you set any environment thats gone.
HTH
Tom
"Stephen Quinn" <steveqNOSPAM@integritynet.com.au> schrieb im Newsbeitrag
news:39oegnF6415bqU1@individual.net...
> Peter
>
>
> Yes - the fragility of the OS.
>
> --
> HTH
> Steve
>
>
| |
| Ant?nio 2005-03-16, 3:55 pm |
| Tom,
> I remember that ME on every startup replaces autoexec.bat and config.sys
> with empty dummys, so if you set any environment thats gone.
Sorry, this in not exactly correct.
Any SET you put in autoexec is kept. Please have a look at the last
lines of this post.
[color=darkred]
>
> HTH
> Tom
>
> "Stephen Quinn" <steveqNOSPAM@integritynet.com.au> schrieb im Newsbeitrag
> news:39oegnF6415bqU1@individual.net...
Stephen,
[color=darkred]
Donot agree.
I work every day with: main machine=WinME and Laptop=WinXP Pro
To run Clipper applications, I find ME is perfectlly safe and stable.
For example:
- Calling external programs (pkzip, blat): works good in ME. Had
problems with other machines running XP;
- Network drives not connected at boot time: never happened with ME,
happens a lot at some sites with XP clients.
I could agree with you, if we were at "comp.os.for.general.use", but
not at "comp.lang.clipper".
Regards,
António Vila-Chã
Portugal
Output catched at Win ME dos box:
C:\>ver
Windows Millennium [Versao 4.90.3000]
C:\>type autoexec.bat
SET PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\UT
S;C:\BX;C:\CLI5\BIN;"C:\Programas\Mi
crosoft SQL Server\80\Tools\Binn\";i:;g:;h:\bcc\bin;h:\xhb\bin;
SET windir=C:\WINDOWS
SET winbootdir=C:\WINDOWS
SET COMSPEC=C:\WINDOWS\COMMAND.COM
SET PROMPT=$p$g
SET TEMP=C:\WINDOWS\TEMP
SET TMP=C:\WINDOWS\TEMP
SET BOXER=k0 t3 s h c C4 e.PRG.TXT.C.BAT.HTM 4 Fm500
SET CLIPPER=F151
SET INCLUDE=C:\CLI5\INCLUDE
SET LIB=C:\CLI5\LIB
SET OBJ=C:\CLI5\OBJ
SET PLL=C:\CLI5\PLL
SET DIRCMD=/4
C:\>type config.sys
C:\>
|
|
|
|
|