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
1
Setup & Installation / Re: RAM disk does not work anymore
« on: August 08, 2019, 11:11:08 am »
Now it works again, I did not understand why. MEMDISK is not part of my Config.sys, this was a failure in the post. Of course I selected the drive letter in the setup program.

2
Setup & Installation / Re: RAM disk does not work anymore
« on: August 07, 2019, 09:26:53 am »
I have realized that the RAM disk is working, but there's a wrong drive letter. os2ldr.cfg holds:
RAMDISK = HPFS PERSIST Z:
RAMDISKNAME = Ramdisk Z

Drive Z seems to be occupied. Any ideas? Drive Y works.

3
Setup & Installation / RAM disk does not work anymore
« on: August 07, 2019, 09:00:43 am »
ArcaOS RAM disk does not work anymore. A hardware problem is possible, I had two other programs which does not run anymore (and I could fix it by re-copying the content of C). Four files are used:

c:\os2ldr.cfg (hidden)
file content:
RAMDISK = HPFS PERSIST *:
RAMDISKNAME = Z

c:\os2\boot\HD4DISK.ADD
c:\os2\boot\MEMDISK.ADD

Then there's a setup program with user interface:
C:\sys\bin\HIDISK.EXE

Any ideas what is also needed ? How can I find out why it fails?

4
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.

5
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:

http://www.hypermake.com/english/do.html

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

http://www.hypermake.de/deutsch/do.html

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


6
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  ?

7
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.

8
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.

9
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?

10
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.

11
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.

12
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.

13
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.

14
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.

15
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

Pages: [1] 2 3 ... 5