Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Martin Vieregg

Pages: [1] 2 3 ... 5
Setup & Installation / ArcaOS fix for Windows seamless problem ?
« on: April 07, 2019, 11:02:32 pm »
I am waiting for an ArcaOS fix to solve the Win16 seamless windows problem. Does anyone heared about any efforts? On my old computer, it did work with eCS 1.2 and SNAP. Not only the missing seamless functionality is a problem, the performance of the Win16-only drivers is extremeley bad.

Utilities / Re: DO.EXE new version commandline utility 1.99
« on: January 07, 2019, 08:25:22 am »
I've updated the archive files of DO to 2.00a:

german language with a short explanation how to use (the readme.txt is only in english)

I have decided to write DO in uppercase letters on Unix systems. This seems to work fine.

Utilities / Re: DO.EXE new version commandline utility 1.99
« on: November 12, 2018, 10:51:11 pm »
I think the conflict only occurs on Unix systems. What about uppercase DO  or  Do  ?

Utilities / Re: architecture/substitute of cmd.exe ?
« on: October 20, 2018, 10:39:09 am »
Where can I get a documentation of the VIO APIs? How can I get the API commands from CMD/4OS2 ?

A part of the functionality can be programmed in the editor, e.g. a list of already entered commands.

Utilities / Re: DO.EXE new version commandline utility 1.99
« on: October 19, 2018, 11:42:52 pm »
I also use GO.EXE. A really nice utility.

Is there really a conflict with the REXX "do" ? Because in Rexx scripts, you have to write normal commandline commands in quotation marks and DO is part of the language (not in quotation marks). I have got DO.EXE in the path statement for years and all Rexx scripts work fine.

Utilities / Re: architecture/substitute of cmd.exe ?
« on: October 19, 2018, 11:33:28 pm »
I am now thinking about to write a new input/output window for cmd.exe or 4os2.exe.

I can start cmd.exe from my editor main program with the /K option and with a output and input file to a pipe:
Code: [Select]
cmd.exe /K >\pipe\myoutpipe <\pipe\myinpipe
and then in my Editor program, a separate thread reads input from \pipe\myoutpipe and if a line has been edited and finished by pressing enter, the typed line gets written to \pipe\myinpipe.

Is it really so simple? Or is the connection between cmd.exe and the PM command window more sophisticated and I will fail with this concept?

Utilities / Re: DO.EXE new version commandline utility 1.99
« on: October 19, 2018, 06:13:02 pm »
Now I've found a quite simple solution:

DO in capital letters, because Unix is case-sensitive. On OS/2 and Windows, you can countinue typing "do" in lowercase letters.

Utilities / Re: architecture/substitute of cmd.exe ?
« on: October 01, 2018, 10:40:28 pm »
I still do not understand where the "silly" commandline window is programmed. It seems that all shell programs use the same restricted window. Is it part of pmshell.exe ? What information is hold in cmd.exe? Only the syntax of the commands or also the commandline PM window with its functionality?
My main interest is to reprogram the window, not the functionality. Reprogramming the functionality is only necessary if it is not possible to divide the window from the commands.

Utilities / Re: architecture/substitute of cmd.exe ?
« on: October 01, 2018, 03:01:42 pm »
I installed Jonathan Pollards program, but I did not understand the purpose. Besides bad performance of e.g. "copy" in some circumstances, what is the need of replacing cmd.exe commands? In former times, there were lacks of 16 bit commands, but in newer OS/2 versions these problems were fixed.

My main interest is to have no more 8192 character buffer limitation (mode 80,102, 160,51) and a more comfortable editing and copy/paste functionalty.

Utilities / architecture/substitute of cmd.exe ?
« on: October 01, 2018, 12:22:32 pm »
The restrictions of the OS/2 commandline window are nervy. 4OS2 has the same restrictions. There's another command line program "take command", but it is no more supported yet and does not support basic cmd.exe commands like "dir /s".

I am the author of the ME Editor and of the DO.EXE commandline program. With ME.EXE, you can already import stdout:
dir /s | me in

I am thinking about a cmd.exe substitute. Basic functionality (dir, md, cd) has to be programmed in the new program, more complicated commands should be run via cmd.exe, while cmd.exe pipes it output to ME. That's because for every cmd command, cmd.exe has to be restarted and "forgets" old settings like the current directory or assign statements, so all functionality where the window has to remember something has to be reprogrammed.

I would like to ask: Is it right that the command line window (frame, fonts, buffer) is part of cmd.exe, so it is not possible to re-program the window only and not the commands? In 4os2, only the commands were reprogrammed, so I assume it is started via cmd.exe.

Utilities / Re: DO.EXE new version commandline utility 1.99
« on: October 01, 2018, 12:01:20 pm »
good to hear that doo has already another meaning...

doit is not so useful, because the parameters are verbs

do delete
do rebuild
do copy
do touch

Perhaps, anyone else has got a good idea.

Utilities / Re: DO.EXE new version commandline utility 1.99
« on: September 13, 2018, 07:36:41 pm »
Meanwhile, I've uploaded the MacOS and Linux version of DO:

DO for Linux 64 bit archive file
DO for MacOS X archive file

Applications / Re: DOS and Win-OS/2 Windowed Sessions
« on: August 25, 2018, 11:34:14 am »
It seems that Panorama generally does not support Win16-seamless, only Snap does. But Snap has very poor performance with current graphics cards. The Alt-Home trick works on my system. ArcaNoae has got the rights of the SNAP source code and plans to update SNAP for newer graphics cards, but I haven't heard any timetable the last months.

With ArcaOS 5.0.3, a new Panorama version (1.11) has been published. Has anyone tried it? (I fear that the Win16-seamless problem has not been fixed.)

Utilities / DO.EXE new version commandline utility 1.99
« on: August 25, 2018, 12:31:36 am »
I have downloaded a new version of my DO.EXE commandline utility:

DO for OS/2 archive file
DO for Windows (32 bit) archive file

DO.EXE is a swiss army knife command line enhancement. Since the last published version 1.46, I have added a handful new functions.

- DO SHOWCLONE, KILLCLONE: find and delete clone files
- DO EVERY: time-related executing of batch files, .e.g. every 3 days

and, most important:

in variants. DO COPY shows the copied file names, DO PCOPY shows a progress bar. (With copy or xcopy, you won't get feedback for a long time when copying big files to slow drives like USB sticks.)
It is faster than XCOPY, because it can handle several file exensions simulateously. It collects all files before beginning with copying.
DO COPY can handle files larger than 4 GB on FAT32 drives. (There really seems to be no program which fits the problem.)

Please report bugs. 1.99 is a beta version, but it seems to work fine.
Please read the docu. DO.EXE can cause harm with only few input. By default, DO.EXE includes subdirectories.

A Linux and Macintosh version will follow. DO.EXE ist written with WDsibyl, and the other platforms with Freepascal-Lazarus.

Setup & Installation / Re: USB 3.0 /3.1
« on: July 04, 2018, 08:58:48 am »
I have got a new 27' 1440x2560 monitor with HDMI. All works fine with Panorama. DVI should also work (not tried yet) with 30 Hz.

Pages: [1] 2 3 ... 5