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

Pages: 1 ... 54 55 [56] 57 58 ... 85
826
Rich already explained it:
your editor app is a PM app. PM apps know nothing about the special handling for Ctrl-C.
your PM app needs to treat the Ctrl-C combination in its window procedure and do a "DosSendSignalException(pid, exception)". DosExecPgm returns the PID of the program it just started (in your case:cmd.exe).

827
Setup & Installation / Re: system settings in arcaos504
« on: January 17, 2020, 09:00:24 am »
You turn off swapping by specifying this in config.sys
MEMMAN=NOSWAP
and not by deleting the swap file.
But as Doug has said:
if you have plenty of memory,OS/2 will not swap anyways and the swap file will never grow beyond its initial size.

828
I think I cannot run cmd.exe via session by using DosStartSession because only DosExecPgm inherits the standard pipes stdin/stdout/stderr. Meanwhile, I fear we're spinning circles. At the first try, I used DosStartSession and Named Pipes. And I changed to DosExecPgm and unnamed pipes with DosDupHandle with the hope of managing the Ctrl-C Interrupt communication problem. Besides this point, the two ways are basically working. But I have a weak idea that DosExecPgm is the smarter option. In both cases, I can stop it. The DosStartSession variant has got DosStopSession, the DosExecPgm variant DosKillProcess. I cannot believe that there is no solution for sending Ctrl-C to cmd.exe. If noone has got an idea to send Ctrl-C to cmd.exe, I will program a kill option in several steps: One waiting for a finished line output and the harder one with immidiately killing the process. But Ctrl-S should suspend cmd.exe. I can suspend a thread but can I suspend a process? I fear not. And what about sessions? Can I suspend sessions? How does the parent process gets informed if the session ends itseif? I also fear that it is not possible. (With the DosExecPgm variant, I can wait for finishing with DosWaitChild.) Anyway, freezing the output of the parent editor should go. But what happens if the pipe is full? Does the OS suspend the process or do I get an error?


So why did it work for me ? I could start a session and redirect stdout and stdin without a problem.

829
You kill a session with DosStopSession.

830
I think you will have to use DosStartSession instead of DosExecPgm as you are starting a different app type.
When you do that you can also kill the session that executes CMD.EXE.
You can therefore register a handler for your process and if it fires,just kill the started session.

831
Setup & Installation / Re: system settings in arcaos504
« on: December 27, 2019, 04:16:57 pm »
I think the "shared memory problem" (the problem where the OS has no place to load new code or data and silently crashes and just reboots) plus the "module loader problem" (a crash in the module loader will happen if the internal DLL's module name does not match its filename, will subsequently bring down the whole system) are the 2 worst problems in OS/2 as the user has no clue what is going on when these crashes happen. The user also has no chance to record any trap info on these 2 errors as the system will not even enter the ordinary OS exception handling.

Just for fun: have you ever marked code and data of an EXE to load high ? That will directly blow the application on loading (because OS/2 expects an app to load at linear address 0x10000 which is not the case if exe code is loaded into high memory ...).

Lars

832
Applications / Re: Timidity MCD install (Minstaller).
« on: December 22, 2019, 09:02:31 am »
I can also confirm that timidity.exe works for me.

You can still associate "timidity.exe" with MIDI files. The only problem is that it won't play on a double click but instead you have to invoke it via the MIDI file's context menu.

833
Hallo Martin,

1) I don't think that you are to blame for the clogged up incoming directory. But from what I heard, the automatic procedure is no longer in place and therefore, a human being has to move that stuff to the final destination. And with that many files, I think the motivation of that human being is going to severly drop.

2) Yes, people will need drivers for older HW. But if you have 2 driver versions for the very same HW, then almost always, the newer driver version will suffice. The risk is just too high that people will try a severly outdated version and then run into all sorts of problems. This for example is true for PRINT01.SYS: it existed for a long time, was "superseded/side stepped" by PAR1284.SYS (also by IBM) but now PAR1284.SYS is outdated for PCI devices (even though it handles SPP/EPP and ECP just fine) and has been superseded by the latest version of PRINT01.SYS that can be configured to handle any PCI plug-in card with a parallel port (through the "PCIDev.tbl" configuration file). There is just a too high risk that people won't go anywhere with PAR1284.SYS.

834
Hardware / Re: PCIe parallel port card
« on: December 18, 2019, 12:31:50 pm »
and last but not least, if everything seems to fail, read the bottom of this page (regarding use of DOS config tool):

http://wiki.linuxcnc.org/cgi-bin/wiki.pl?WCH

835
Hardware / Re: PCIe parallel port card
« on: December 18, 2019, 12:07:41 pm »
@Neil,

if this does not work:
1C00,3050,p1,,e1

then try this:
1C00,3050,s,,p

and let us know what worked, if any :-)

836
Hardware / Re: PCIe parallel port card
« on: December 18, 2019, 09:17:59 am »
@Neil: I think you will need to disable all onboard/legacy parallel ports (hopefully possible to do that via BIOS).
I am not sure if PRINT01.SYS will be able to handle a mixed combination of legacy and PCI parallel port interfaces.


837
Hallo Martin,

I think it would be a good idea to not upload outdated drivers to Hobbes:

1) the Hobbes incoming directory is completely clogged up with old drivers and nobody seems to have interest to move that stuff to the final destination. This leads to the problem that other apps and drivers (like DFSee or my new USB drivers and other interesting apps) also get stuck in the incoming directory and never reach their final destination

2) there is a risk that people will download outdated drivers which have long been replaced by newer ones. This leads to all kinds of questions and requests for help which are unnecessary because various problems have been solved by newer drivers.


On the other hand, if you have old source code to upload, then go ahead. Old source code is always a good place to start off to create new stuff.


Regards,
Lars

838
Hardware / Re: PCIe parallel port card
« on: December 18, 2019, 07:49:48 am »
I just checked: PAR1284.SYS does NOT offer the PCIDev.tbl support even though it DOES support ECP and EPP parallel ports.
Can anyone enlighten me if PAR1284.SYS was superseded by an updated PRINT01.SYS that also supports ECP and EPP parallel ports plus support for non-legacy port addresses ?

Lars

839
Hardware / Re: PCIe parallel port card
« on: December 18, 2019, 07:41:48 am »
correction time:
I received a private email that pointed me to the fact that PRINT01.SYS supports file \OS2\BOOT\PCIDev.tbl.
I was not aware of that (I thought that was only for COM.SYS) but if yes, maybe this additional entry in PCIDev.tbl will do the trick (if I guess the syntax correctly,it is only poorly documented, my assumption is that each of the 6 possible entries after the vendor and device ids aligns with a BAR entry in PCI config space):

;IOCrest PCI-Express parallel port card WCH 382
1C00,3050,p1,,e1


Regards,
Lars

840
Hardware / Re: PCIe parallel port card
« on: December 17, 2019, 11:13:45 am »
I did not find a good HW manual for the chip. But with the given PCI output, I'd assume (that is: I don't know but it's likely) that the given I/O port range on your system (this is setup by the BIOS) is 0xE000 - 0xE0FF for the lower set of standard parallel port (and EPP) registers and 0xE100 - 0xE103 for the upper 4 registers (to support ECP).

It's obvious that these are not the standard I/O ports addresses for a standard parallel port and that's why it will not work with PRINT01.SYS or PAR1284.SYS for that matter.
However, the chip claims it DOES contain a IEEE1284 compliant controller which means it has the same set of operational registers as a standard parallel port with the very same functionality.

It would be possible to take the PAR1284.SYS source code (being part of the DDK) and "convert" that so that it uses the I/O port addresses that the BIOS has set up instead of the hard coded ones (standard parallel port addresses).

It's work but it is not impossible.

Lars

Pages: 1 ... 54 55 [56] 57 58 ... 85