Hello,
After the creation of a file TXT (ascii), with the function RUN (Clipper
5.2e) or with Blinker 4 SWPRUNCMD (or with RUN and .BAT file) I open NOTEPAD
(Windows XP) to read or to print the file TXT.
The Clipper program remains however blocked until I do not close Notepad.
The Clipper program can work unfortunately alone in REAL MODE and not in
PROTECTED MODE (BLINKER OVERLAY is ON) !
It exists a manner to open a autonomous NOTEPAD window, so as to be able to
continue to work with the CLIPPER program?
Any suggestions ?
Thanks.
Bob
Clipper 5.2e & Blinker 4
|
|
0
|
|
|
|
Reply
|
 Bob
|
2/1/2010 9:59:40 AM |
|
Hello.
You could use "RUN START NOTEPAD file.txt"
Using this program (found in windows folder), your app takes back the
running, while your notepad starts in another program session.
til.
On 1 fev, 07:59, "Bob" <NoS...@NoSpam.net> wrote:
> Hello,
> After the creation of a file TXT (ascii), with the function RUN (Clipper
> 5.2e) or with Blinker 4 SWPRUNCMD (or with RUN and .BAT file) I open NOTE=
PAD
> (Windows XP) to read or to print the file TXT.
> The Clipper program remains however blocked until I do not close Notepad.
> The Clipper program can work unfortunately alone in REAL MODE and not in
> PROTECTED MODE (BLINKER OVERLAY is ON) !
>
> It exists a manner to open a autonomous NOTEPAD window, so as to be able =
to
> continue to work with the CLIPPER program?
>
> Any suggestions ?
> Thanks.
> Bob
> Clipper 5.2e =A0& Blinker 4
|
|
|
0
|
|
|
|
Reply
|
guidelli
|
2/1/2010 1:05:25 PM
|
|
Hello Til,
Already I had experienced with START, but the CLIPPER program remains
however blocked until the closing of NOTEPAD.
Thanks.
Bob
"guidelli" <guidelli@gmail.com> ha scritto nel messaggio
news:e07533f3-f96c-4d41-90e6-29625973f965@f11g2000yqm.googlegroups.com...
Hello.
You could use "RUN START NOTEPAD file.txt"
Using this program (found in windows folder), your app takes back the
running, while your notepad starts in another program session.
til.
On 1 fev, 07:59, "Bob" <NoS...@NoSpam.net> wrote:
> Hello,
> After the creation of a file TXT (ascii), with the function RUN (Clipper
> 5.2e) or with Blinker 4 SWPRUNCMD (or with RUN and .BAT file) I open
> NOTEPAD
> (Windows XP) to read or to print the file TXT.
> The Clipper program remains however blocked until I do not close Notepad.
> The Clipper program can work unfortunately alone in REAL MODE and not in
> PROTECTED MODE (BLINKER OVERLAY is ON) !
>
> It exists a manner to open a autonomous NOTEPAD window, so as to be able
> to
> continue to work with the CLIPPER program?
>
> Any suggestions ?
> Thanks.
> Bob
> Clipper 5.2e & Blinker 4
|
|
|
0
|
|
|
|
Reply
|
Bob
|
2/1/2010 1:21:15 PM
|
|
Dear Bob:
On Feb 1, 2:59=A0am, "Bob" <NoS...@NoSpam.net> wrote:
....
> After the creation of a file TXT (ascii),
> with the function RUN (Clipper 5.2e) or
> with Blinker 4 SWPRUNCMD (or with RUN and
> .BAT file) I open NOTEPAD (Windows XP) to
> read or to print the file TXT. The
> Clipper program remains however blocked
> until I do not close Notepad. The Clipper
> program can work unfortunately alone in
> REAL MODE and not in PROTECTED MODE
> (BLINKER OVERLAY is ON) !
>
> It exists a manner to open a autonomous
> NOTEPAD window, so as to be able to
> continue to work with the CLIPPER program?
>
> Any suggestions ?
Switch to xHarbour.
Use a text editor that is OLE capable.
Output to HTML, and open the file with a browser.
http://www.tek-tips.com/viewthread.cfm?qid=3D1246247&page=3D7
David A. Smith
|
|
|
0
|
|
|
|
Reply
|
dlzc
|
2/1/2010 2:49:30 PM
|
|
Well, most apps could be witched to xHarbour. That's a good idea.
But... in so many cases, we had no time enough to do it, or by a
simple detail like "cost" (still ref. to time and $$ to maintain
ourselves during convertions) we cant apply that.
It's strange your START not freein' your first app to keep running.
You could tell us what OS u ar using. I tested with w98 and Xp, and
workd well, with no more parameters. (Calling java jars, "Start java -
jar....").
The other idea workd with me too months ago. Calling a html browser. U
will have great text formating if using the "<html>,<font..>" things.
Also can use the browser to open your txt files too.
Just have a try.
Cya.
Evandro.
On 1 fev, 12:49, dlzc <dl...@cox.net> wrote:
> Dear Bob:
>
> On Feb 1, 2:59=A0am, "Bob" <NoS...@NoSpam.net> wrote:
> ...
>
>
>
> > After the creation of a file TXT (ascii),
> > with the function RUN (Clipper 5.2e) or
> > with Blinker 4 SWPRUNCMD (or with RUN and
> > .BAT file) I open NOTEPAD (Windows XP) to
> > read or to print the file TXT. =A0The
> > Clipper program remains however blocked
> > until I do not close Notepad. =A0The Clipper
> > program can work unfortunately alone in
> > REAL MODE and not in PROTECTED MODE
> > (BLINKER OVERLAY is ON) !
>
> > It exists a manner to open a autonomous
> > NOTEPAD window, so as to be able to
> > continue to work with the CLIPPER program?
>
> > Any suggestions ?
>
> Switch to xHarbour.
> Use a text editor that is OLE capable.
> Output to HTML, and open the file with a browser.http://www.tek-tips.com/=
viewthread.cfm?qid=3D1246247&page=3D7
>
> David A. Smith
|
|
|
0
|
|
|
|
Reply
|
guidelli
|
2/1/2010 3:51:00 PM
|
|
Hi Evandro,
I will try again with START and with the other your suggestions.
Thanks
Bob
-----------------------------
"guidelli" <guidelli@gmail.com>
Well, most apps could be witched to xHarbour. That's a good idea.
But... in so many cases, we had no time enough to do it, or by a
simple detail like "cost" (still ref. to time and $$ to maintain
ourselves during convertions) we cant apply that.
It's strange your START not freein' your first app to keep running.
You could tell us what OS u ar using. I tested with w98 and Xp, and
workd well, with no more parameters. (Calling java jars, "Start java -
jar....").
The other idea workd with me too months ago. Calling a html browser. U
will have great text formating if using the "<html>,<font..>" things.
Also can use the browser to open your txt files too.
Just have a try.
Cya.
Evandro.
On 1 fev, 12:49, dlzc <dl...@cox.net> wrote:
> Dear Bob:
>
> On Feb 1, 2:59 am, "Bob" <NoS...@NoSpam.net> wrote:
> ...
>
>
>
> > After the creation of a file TXT (ascii),
> > with the function RUN (Clipper 5.2e) or
> > with Blinker 4 SWPRUNCMD (or with RUN and
> > .BAT file) I open NOTEPAD (Windows XP) to
> > read or to print the file TXT. The
> > Clipper program remains however blocked
> > until I do not close Notepad. The Clipper
> > program can work unfortunately alone in
> > REAL MODE and not in PROTECTED MODE
> > (BLINKER OVERLAY is ON) !
>
> > It exists a manner to open a autonomous
> > NOTEPAD window, so as to be able to
> > continue to work with the CLIPPER program?
>
> > Any suggestions ?
>
> Switch to xHarbour.
> Use a text editor that is OLE capable.
> Output to HTML, and open the file with a
> browser.http://www.tek-tips.com/viewthread.cfm?qid=1246247&page=7
>
> David A. Smith
|
|
|
0
|
|
|
|
Reply
|
Bob
|
2/1/2010 8:18:16 PM
|
|
Bob,
>After the creation of a file TXT (ascii), with the function RUN (Clipper
>5.2e) or with Blinker 4 SWPRUNCMD (or with RUN and .BAT file) I open NOTEPAD
>(Windows XP) to read or to print the file TXT.
>The Clipper program remains however blocked until I do not close Notepad.
>The Clipper program can work unfortunately alone in REAL MODE and not in
>PROTECTED MODE (BLINKER OVERLAY is ON) !
>
>It exists a manner to open a autonomous NOTEPAD window, so as to be able to
>continue to work with the CLIPPER program?
Try starting a new command processor first:
RUN CMD /C START /B NOTEPAD file.txt
(or pass the same arguments to SWPRUNCMD)
Regards,
Klas
-------
klas dot engwall at engwall dot com
http://www.engwall.com/clipper/
The LFN Library for Clipper
The LanMan Library for Clipper
The NFPAT1A Timeslice release patch for the Nanforum Toolkit
|
|
|
0
|
|
|
|
Reply
|
klas
|
2/1/2010 11:52:00 PM
|
|
Hi Klas,
it is a pleasure to reread you...
I think that the simpler solution is that of to create a file. BAT in
function of the TXT to visualize....I use therefore RUN only for the .BAT
With Windows XP SP3 the system works alone if the file BAT (created with
Clipper) contains this order
%SystemRoot%\system32\cmd.exe /c start C:\directory\file.TXT
While manually (Prompt) it works also with the command: 'start file.txt'.
Not yet I understood why....
Under Windows 9x instead it works alone 'start C:\directory\file.TXT'
why CMD.EXE does not exist and not even %SystemRoot%\system32 exists !
Considering that my freeware program is used from many people with different
operating system (9x/XP/Vista/W7), is difficult to find a solution...
I found the function FT_DOSVER() (Nanforum) but I do not know what return
under the varied operating system
Suggestions they are appreciated
Thank you
Regards
Bob
-----------------------------------
"Klas Engwall" <klas.engwall@nospam.please>
> Bob,
>
>>After the creation of a file TXT (ascii), with the function RUN (Clipper
>>5.2e) or with Blinker 4 SWPRUNCMD (or with RUN and .BAT file) I open
>>NOTEPAD
>>(Windows XP) to read or to print the file TXT.
>>The Clipper program remains however blocked until I do not close Notepad.
>>The Clipper program can work unfortunately alone in REAL MODE and not in
>>PROTECTED MODE (BLINKER OVERLAY is ON) !
>>
>>It exists a manner to open a autonomous NOTEPAD window, so as to be able
>>to
>>continue to work with the CLIPPER program?
>
> Try starting a new command processor first:
>
> RUN CMD /C START /B NOTEPAD file.txt
>
> (or pass the same arguments to SWPRUNCMD)
>
> Regards,
> Klas
>
> -------
> klas dot engwall at engwall dot com
>
> http://www.engwall.com/clipper/
>
> The LFN Library for Clipper
> The LanMan Library for Clipper
> The NFPAT1A Timeslice release patch for the Nanforum Toolkit
|
|
|
0
|
|
|
|
Reply
|
Bob
|
2/2/2010 2:57:00 PM
|
|
Dear Bob:
On Feb 2, 7:57=A0am, "Bob" <NoS...@NoSpam.net> wrote:
....
> Considering that my freeware program is used
> from many people with different operating
> system (9x/XP/Vista/W7), is difficult to find
> a solution...
Output your text file with en extension of .htm, and RUN the text
file. The browser will open it, and I think it will close your
COMMAND.COM session and let your program run again. I don't have
Win98 anymore to try this there. Let us know if this does not work.
David A. Smith
|
|
|
0
|
|
|
|
Reply
|
dlzc
|
2/2/2010 3:31:10 PM
|
|
Hi david,
I have changed extension to the txt files with htm, but opening them with
Explorer I see that the column order (tabulation)
is lost.
I create the tabulation with PADR(...) and also with chr(13)+chr(10)
Too much work to transform txt in true htm
Thank you
Greatings
Bob
"dlzc" <dlzc1@cox.net>
Dear Bob:
On Feb 2, 7:57 am, "Bob" <NoS...@NoSpam.net> wrote:
....
> Considering that my freeware program is used
> from many people with different operating
> system (9x/XP/Vista/W7), is difficult to find
> a solution...
Output your text file with en extension of .htm, and RUN the text
file. The browser will open it, and I think it will close your
COMMAND.COM session and let your program run again. I don't have
Win98 anymore to try this there. Let us know if this does not work.
David A. Smith
|
|
|
0
|
|
|
|
Reply
|
Bob
|
2/2/2010 7:57:47 PM
|
|
Bob,
To distinguish between Win/DOS versions you can use OsLib by Dave
Pearson. It's available at http://www.davep.org/clipper/.
HTH, Eugene
|
|
|
0
|
|
|
|
Reply
|
E
|
2/2/2010 10:13:33 PM
|
|
Dear Bob:
On Feb 2, 12:57=A0pm, "Bob" <NoS...@NoSpam.net> wrote:
> Hi david,
> I have changed extension to the txt files with
> htm, but opening them with Explorer I see that
> the column order (tabulation) is lost.
Did you get control of Clipper back right away?
> I create the tabulation with PADR(...) =A0and
> also with chr(13)+chr(10). Too much work to
> transform txt in true htm
If you get control back right away (the hard part), then you *must*
investigate this for all your customers (Win7 thru Win98). If not,
you are right, it is a waste of time to go down this branch any
further.
If you do get control back, you can use this:
http://www.the-oasis.net/ftpmaster.php3?content=3Dftpgenrl.htm
.... down to tb2html.zip, and output the file in proper html format,
controlled as you would a tbrowse.
Please note that you could save your text file as .CSV or .XLS (with
commas instead of PADR), and execute this file and (likely) Excel (or
OpenOffice) will open it. Same for .DOC. And all *should* give
control back to your Clipper code right away.
And you will do what you choose to do, and you do not need to respond
to me. Would be nice to know what finally worked, so that posterity
will be saved some of your effort...
David A. Smith
|
|
|
0
|
|
|
|
Reply
|
dlzc
|
2/2/2010 11:02:13 PM
|
|
Bob,
>I think that the simpler solution is that of to create a file. BAT in
>function of the TXT to visualize....I use therefore RUN only for the .BAT
>With Windows XP SP3 the system works alone if the file BAT (created with
>Clipper) contains this order
>%SystemRoot%\system32\cmd.exe /c start C:\directory\file.TXT
Why do you need to specify the path to cmd.exe? I have swapped out to the OS in
several different ways over the years and always found cmd.exe or command.com
without the path. Do you change the environment before starting your app?
>While manually (Prompt) it works also with the command: 'start file.txt'.
>Not yet I understood why....
>
>Under Windows 9x instead it works alone 'start C:\directory\file.TXT'
>why CMD.EXE does not exist and not even %SystemRoot%\system32 exists !
>
>Considering that my freeware program is used from many people with different
>operating system (9x/XP/Vista/W7), is difficult to find a solution...
How about this, then:
if 'SYSTEM32' $ upper( getenv( 'COMSPEC' ) )
// Run the cmd.exe version
else
// Run the command.com version
endif
>I found the function FT_DOSVER() (Nanforum) but I do not know what return
>under the varied operating system
It is not reliable after DOS 6.x
Regards,
Klas
-------
klas dot engwall at engwall dot com
http://www.engwall.com/clipper/
The LFN Library for Clipper
The LanMan Library for Clipper
The NFPAT1A Timeslice release patch for the Nanforum Toolkit
|
|
|
0
|
|
|
|
Reply
|
klas
|
2/2/2010 11:04:53 PM
|
|
Hi Klas,
"Klas Engwall" <klas.engwall@nospam.please>
> Bob,
>
> Why do you need to specify the path to cmd.exe? I have swapped out to the
> OS in
> several different ways over the years and always found cmd.exe or
> command.com
> without the path. Do you change the environment before starting your app?
No !!
> How about this, then:
> if 'SYSTEM32' $ upper( getenv( 'COMSPEC' ) )
> // Run the cmd.exe version
> else
> // Run the command.com version
> endif
Good idea !
on my first PC (XP) COMSPEC give me the correct path
(c:\windows\system32\cmd.exe), and
also on the second (98SE) c:\windows\command.com !
Therefore I do not understand because I am obliged (under XP) to put the
PATH for CMD
For the moment is a mystery
I hope that with Vista and W7 COMSPEC is equal to XP.... I have not, right
now, PC with these OS.
However the solution with RUN CMD /C START NOTEPAD file.txt (...with
path...) now works ok.
Thank you
Regards
Bob
|
|
|
0
|
|
|
|
Reply
|
Bob
|
2/3/2010 5:54:45 PM
|
|
Dear David
> Did you get control of Clipper back right away?
I just renamed the TXT file without making changes to the program.... I have
open the file htm manually...
Now the solution with Notepad (...start notepad file.txt...) works ok (it
give control back... I create and
'RUN' a BAT file) but I should surpass some other difficulty (path...
COMSPEC on different PC...).
Thank you
Bob
|
|
|
0
|
|
|
|
Reply
|
Bob
|
2/3/2010 5:59:29 PM
|
|
Hi Bob,
In article <hkcdbj$7tn$1@tdi.cu.mi.it> NoSpam@NoSpam.net "Bob" writes:
> Hi Klas,
>
> "Klas Engwall" <klas.engwall@nospam.please>
...
> > How about this, then:
> > if 'SYSTEM32' $ upper( getenv( 'COMSPEC' ) )
> > // Run the cmd.exe version
> > else
> > // Run the command.com version
> > endif
>
> Good idea !
...
> However the solution with RUN CMD /C START NOTEPAD file.txt (...with
> path...) now works ok.
Well, joining all this together, how about:
comspec = GETENV ("COMSPEC")
RUN (comspec + " /C START NOTEPAD " + filename)
Ought to work for any/all Win OS ??
Just my 2p worth...
Pete
--
"We have not inherited the earth from our ancestors,
we have borrowed it from our descendants."
|
|
|
0
|
|
|
|
Reply
|
pete
|
2/4/2010 6:01:17 AM
|
|
Hi Pete,
> Well, joining all this together, how about:
>
> comspec = GETENV ("COMSPEC")
> RUN (comspec + " /C START NOTEPAD " + filename)
> Ought to work for any/all Win OS ??
<cut>
True! Thought to solve the problem just the way you suggested...
Hoping to work with W7 and Vista !
Thanks to all for the help and the courtesy
Bob
<pete@nospam.demon.co.uk> > Hi Bob,
>
> In article <hkcdbj$7tn$1@tdi.cu.mi.it> NoSpam@NoSpam.net "Bob" writes:
>
>> Hi Klas,
>>
>> "Klas Engwall" <klas.engwall@nospam.please>
> ..
>> > How about this, then:
>> > if 'SYSTEM32' $ upper( getenv( 'COMSPEC' ) )
>> > // Run the cmd.exe version
>> > else
>> > // Run the command.com version
>> > endif
>>
>> Good idea !
> ..
>> However the solution with RUN CMD /C START NOTEPAD file.txt (...with
>> path...) now works ok.
>
> Well, joining all this together, how about:
>
> comspec = GETENV ("COMSPEC")
> RUN (comspec + " /C START NOTEPAD " + filename)
>
> Ought to work for any/all Win OS ??
>
> Just my 2p worth...
>
> Pete
> --
> "We have not inherited the earth from our ancestors,
> we have borrowed it from our descendants."
|
|
|
0
|
|
|
|
Reply
|
Bob
|
2/4/2010 9:47:45 AM
|
|
I found the cause of the strange operation!
PC with Windows XP SP3:
manually in the Windows prompt I type SET <Enter>
and between the data I see that ComSpec = C: \ WINDOWS \ system32 \ CMD.EXE
Everything ok!
Same PC but with the program Clipper 5.2E + Blinker 4:
getenv ( 'COMSPEC') returns c: \ WINDOWS \ system32 \ COMMAND.COM
Why the difference ?
Thereby creating the file .BAT with COMSPEC get
C: \ WINDOWS \ SYSTEM32 \ COMMAND.COM / c start C: \ directory \ file.txt
does not work !!!!!! does not work with less
C: \ WINDOWS \ SYSTEM32 \ COMMAND.COM / c start notepad C: \ directory \
file.txt
If I change the . BAT and replace COMMAND.COM with CMD.EXE
sure it works!
What is the mystery?
Note that on the PC with Window 98SE SET & COMSPEC are identical (C: \
WINDOWS \ COMMAND.COM)
and the file .BAT works well: C: \ WINDOWS \ COMMAND.COM /c start wordpad
c:\directory\file.txt
Any ideas
Regards
Bob
-------------------------------------------------------------
"Klas Engwall" <klas.engwall@nospam.please>
> Bob,
>
>>I think that the simpler solution is that of to create a file. BAT in
>>function of the TXT to visualize....I use therefore RUN only for the .BAT
>>With Windows XP SP3 the system works alone if the file BAT (created with
>>Clipper) contains this order
>>%SystemRoot%\system32\cmd.exe /c start C:\directory\file.TXT
>
> Why do you need to specify the path to cmd.exe? I have swapped out to the
> OS in
> several different ways over the years and always found cmd.exe or
> command.com
> without the path. Do you change the environment before starting your app?
>
>>While manually (Prompt) it works also with the command: 'start file.txt'.
>>Not yet I understood why....
>>
>>Under Windows 9x instead it works alone 'start C:\directory\file.TXT'
>>why CMD.EXE does not exist and not even %SystemRoot%\system32 exists !
>>
>>Considering that my freeware program is used from many people with
>>different
>>operating system (9x/XP/Vista/W7), is difficult to find a solution...
>
> How about this, then:
>
> if 'SYSTEM32' $ upper( getenv( 'COMSPEC' ) )
> // Run the cmd.exe version
> else
> // Run the command.com version
> endif
>
>>I found the function FT_DOSVER() (Nanforum) but I do not know what return
>>under the varied operating system
>
> It is not reliable after DOS 6.x
>
> Regards,
> Klas
>
> -------
> klas dot engwall at engwall dot com
>
> http://www.engwall.com/clipper/
>
> The LFN Library for Clipper
> The LanMan Library for Clipper
> The NFPAT1A Timeslice release patch for the Nanforum Toolkit
|
|
|
0
|
|
|
|
Reply
|
Bob
|
2/4/2010 9:56:18 PM
|
|
I found the cause of the strange operation!
PC with Windows XP SP3:
manually in the Windows prompt I type SET <Enter>
and between the data I see that ComSpec = C: \ WINDOWS \ system32 \ CMD.EXE
Everything ok!
Same PC but with the program Clipper 5.2E + Blinker 4:
getenv ( 'COMSPEC') returns c: \ WINDOWS \ system32 \ COMMAND.COM
Why the difference ?
Thereby creating the file .BAT with COMSPEC get
C: \ WINDOWS \ SYSTEM32 \ COMMAND.COM / c start C: \ directory \ file.txt
does not work !!!!!! does not work with less
C: \ WINDOWS \ SYSTEM32 \ COMMAND.COM / c start notepad C: \ directory \
file.txt
If I change the . BAT and replace COMMAND.COM with CMD.EXE
sure it works!
What is the mystery?
Note that on the PC with Window 98SE SET & COMSPEC are identical (C: \
WINDOWS \ COMMAND.COM)
and the file .BAT works well: C: \ WINDOWS \ COMMAND.COM /c start wordpad
c:\directory\file.txt
Any ideas
Regards
Bob
-------------------------------------------------------------
"Klas Engwall" <klas.engwall@nospam.please>
> Bob,
>
>>I think that the simpler solution is that of to create a file. BAT in
>>function of the TXT to visualize....I use therefore RUN only for the .BAT
>>With Windows XP SP3 the system works alone if the file BAT (created with
>>Clipper) contains this order
>>%SystemRoot%\system32\cmd.exe /c start C:\directory\file.TXT
>
> Why do you need to specify the path to cmd.exe? I have swapped out to the
> OS in
> several different ways over the years and always found cmd.exe or
> command.com
> without the path. Do you change the environment before starting your app?
>
>>While manually (Prompt) it works also with the command: 'start file.txt'.
>>Not yet I understood why....
>>
>>Under Windows 9x instead it works alone 'start C:\directory\file.TXT'
>>why CMD.EXE does not exist and not even %SystemRoot%\system32 exists !
>>
>>Considering that my freeware program is used from many people with
>>different
>>operating system (9x/XP/Vista/W7), is difficult to find a solution...
>
> How about this, then:
>
> if 'SYSTEM32' $ upper( getenv( 'COMSPEC' ) )
> // Run the cmd.exe version
> else
> // Run the command.com version
> endif
>
>>I found the function FT_DOSVER() (Nanforum) but I do not know what return
>>under the varied operating system
>
> It is not reliable after DOS 6.x
>
> Regards,
> Klas
>
> -------
> klas dot engwall at engwall dot com
>
> http://www.engwall.com/clipper/
>
> The LFN Library for Clipper
> The LanMan Library for Clipper
> The NFPAT1A Timeslice release patch for the Nanforum Toolkit
|
|
|
0
|
|
|
|
Reply
|
Bob
|
2/4/2010 9:56:18 PM
|
|
The reason was obvious: opening Prompt with COMMAND.COM (XP) missing path,
contrary to what happens with CMD.EXE !!
Windows XP then handles differently command.com from cmd.exe ...... I see no
other reason....
Sorry abouth the double post caused by ADSL problems
Regards
Bob
|
|
|
0
|
|
|
|
Reply
|
Bob
|
2/5/2010 9:27:27 AM
|
|
Bob,
>I found the cause of the strange operation!
>PC with Windows XP SP3:
>manually in the Windows prompt I type SET <Enter>
>and between the data I see that ComSpec = C: \ WINDOWS \ system32 \ CMD.EXE
>Everything ok!
>
>Same PC but with the program Clipper 5.2E + Blinker 4:
>getenv ( 'COMSPEC') returns c: \ WINDOWS \ system32 \ COMMAND.COM
>Why the difference ?
Because the Clipper application is running under command.com, not cmd.exe, even
if you start it from an already opened cmd.exe console window. Remember that you
cannot run 16-bit applications in a 32-bit environment. You run them in the
NTVDM, and that is where command.com gets into the picture.
>Thereby creating the file .BAT with COMSPEC get
>C: \ WINDOWS \ SYSTEM32 \ COMMAND.COM / c start C: \ directory \ file.txt
>does not work !!!!!! does not work with less
>C: \ WINDOWS \ SYSTEM32 \ COMMAND.COM / c start notepad C: \ directory \
>file.txt
Apparently the file associations to not work correctly under command.com in XP
(I have no Win9x machine available to test if it works there). If you specify
cmd.exe instead I am pretty sure you will see your text file opened in notepad
in your first example. It works here, anyway.
>If I change the . BAT and replace COMMAND.COM with CMD.EXE
>sure it works!
>
>What is the mystery?
No mystery :-). See above.
>Note that on the PC with Window 98SE SET & COMSPEC are identical (C: \
>WINDOWS \ COMMAND.COM)
>and the file .BAT works well: C: \ WINDOWS \ COMMAND.COM /c start wordpad
>c:\directory\file.txt
As expected. What if you remove the application name (wordpad) from the call.
Does it still work?
Regards,
Klas
-------
klas dot engwall at engwall dot com
http://www.engwall.com/clipper/
The LFN Library for Clipper
The LanMan Library for Clipper
The NFPAT1A Timeslice release patch for the Nanforum Toolkit
|
|
|
0
|
|
|
|
Reply
|
 klas.engwall (791)
|
2/6/2010 12:34:52 AM
|
|
Bob,
>The reason was obvious: opening Prompt with COMMAND.COM (XP) missing path,
>contrary to what happens with CMD.EXE !!
I am not sure exactly what you are saying here. I don't think it is a path
problem but a file association problem.
>Windows XP then handles differently command.com from cmd.exe ...... I see no
>other reason....
My tests showed that the file associations (just running file.txt without
specifying the application to open the text file with) do not work properly
under command.com. So yes, the two shells need to be treated differently.
Regards,
Klas
-------
klas dot engwall at engwall dot com
http://www.engwall.com/clipper/
The LFN Library for Clipper
The LanMan Library for Clipper
The NFPAT1A Timeslice release patch for the Nanforum Toolkit
|
|
|
0
|
|
|
|
Reply
|
klas
|
2/6/2010 12:34:57 AM
|
|
Dear Klas
<precedent Klas post>
>>The reason was obvious: opening Prompt with COMMAND.COM (XP) missing path,
>>contrary to what happens with CMD.EXE !!
>
> I am not sure exactly what you are saying here. I don't think it is a path
> problem but a file association problem.
File association is Ok (XP = Notepad 98 = Notepad also)
The problem seems caused by START command !
W.XP = C: \ WINDOWS \ SYSTEM32 \ COMMAND.COM / c start notepad C: \
directory \file.txt
does not work !!!!!!
W.XP = C: \ WINDOWS \ SYSTEM32 \ COMMAND.COM / c notepad C: \ directory
\file.txt
works well !
The DOS now is a prehistoric system, but sometimes we discover something
new...
<last Klas post)
>
>>Note that on the PC with Window 98SE SET & COMSPEC are identical (C: \
>>WINDOWS \ COMMAND.COM)
>>and the file .BAT works well: C: \ WINDOWS \ COMMAND.COM /c start
>>wordpad
>>c:\directory\file.txt
>
> As expected. What if you remove the application name (wordpad) from the
> call.
> Does it still work?
>
W.98SE: without application name (wordpad) works well !
Regards
Bob
|
|
|
0
|
|
|
|
Reply
|
Bob
|
2/6/2010 6:26:30 PM
|
|
Bob,
>File association is Ok (XP = Notepad 98 = Notepad also)
>The problem seems caused by START command !
>W.XP = C: \ WINDOWS \ SYSTEM32 \ COMMAND.COM / c start notepad C: \
>directory \file.txt
>does not work !!!!!!
>W.XP = C: \ WINDOWS \ SYSTEM32 \ COMMAND.COM / c notepad C: \ directory
>\file.txt
>works well !
It is quite possible that start.exe does not work with command.com. I have never
used those two together.
Why do you still call command.com in XP? I thought we had established that you
were going to use cmd.exe in XP (and other NT based Windows versions, the ones
that have "SYSTEM32" in comspec) and reserve command.com for Win9x.
And please get rid of all the spaces. It is imnpossible to know if you mean
"/C", which is correct, or "/ C", which is wrong.
To sum up, if you use cmd.exe with start.exe in your NT/XP version you should be
OK with or without specifying notepad. Then a version for Win9x remains.
Regards,
Klas
-------
klas dot engwall at engwall dot com
http://www.engwall.com/clipper/
The LFN Library for Clipper
The LanMan Library for Clipper
The NFPAT1A Timeslice release patch for the Nanforum Toolkit
|
|
|
0
|
|
|
|
Reply
|
klas
|
2/7/2010 12:33:31 AM
|
|
Warning !
In Windows 98 and before START is a file START.EXE... (It's need path file)
In Windows XP is a hidden command.
Regards
Bob escribi� en mensaje ...
>Dear Klas
>
><precedent Klas post>
>
>>>The reason was obvious: opening Prompt with COMMAND.COM (XP) missing
path,
>>>contrary to what happens with CMD.EXE !!
>>
>> I am not sure exactly what you are saying here. I don't think it is a
path
>> problem but a file association problem.
>
>File association is Ok (XP = Notepad 98 = Notepad also)
>The problem seems caused by START command !
>W.XP = C: \ WINDOWS \ SYSTEM32 \ COMMAND.COM / c start notepad C: \
>directory \file.txt
>does not work !!!!!!
>W.XP = C: \ WINDOWS \ SYSTEM32 \ COMMAND.COM / c notepad C: \ directory
>\file.txt
>works well !
>The DOS now is a prehistoric system, but sometimes we discover something
>new...
>
><last Klas post)
>>
>>>Note that on the PC with Window 98SE SET & COMSPEC are identical (C: \
>>>WINDOWS \ COMMAND.COM)
>>>and the file .BAT works well: C: \ WINDOWS \ COMMAND.COM /c start
>>>wordpad
>>>c:\directory\file.txt
>>
>> As expected. What if you remove the application name (wordpad) from the
>> call.
>> Does it still work?
>>
>W.98SE: without application name (wordpad) works well !
>
>Regards
>Bob
>
>
|
|
|
0
|
|
|
|
Reply
|
Antonio
|
2/8/2010 12:21:47 PM
|
|
Hi Antonio,
"Antonio Martinez" <alcisoft@arrakis.es>
>
> In Windows 98 and before START is a file START.EXE... (It's need path
> file)
> In Windows XP is a hidden command.
Thanks for the information.
This was a doubt that I had had!
Now I have certainty.
Thanks
Bob
|
|
|
0
|
|
|
|
Reply
|
Bob
|
2/8/2010 1:33:50 PM
|
|
|
25 Replies
501 Views
(page loaded in 0.279 seconds)
|
Search |
Post Question |
Groups |
Stream |
About |
Register
4021 articles. 
20 followers. 