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 ... 23 24 [25] 26 27 ... 29
Applications / Re: Yum error! "Python strikes again"!
« on: July 19, 2016, 02:34:54 pm »
1) rename the \etc directory to say \etc_xxx
2) rename the \usr directory to say \usr_xxx
3) reboot and hope for the best
4) rerun ANPM, it should now ask you if it should install yum/rpm (because it now can no longer find it because of 1) and 2) ), answer with yes and wait until it is done
5) reboot, if everything went well you will now have a new \etc and \usr directory and you can then delete \etc_xxx and \usr_xxx. You will need to run ANPM to update a whole bunch of packages because the prebundle installed at 4) contains outdated versions of a number of packages.

Utilities / Re: IRQ Monitor
« on: June 25, 2016, 12:25:55 pm »
May I throw in that with USB drivers 10.205 and 10.206 I have also reworked the USBMSD.ADD data transmission code. I hope it has helped performance while at the same time it should reduce IRQ load.

Hardware / USB drivers 10.206 released
« on: June 22, 2016, 10:35:02 am »
Sorry but since it's kind of urgent: I had to do yet another critical fix to USBMSD.ADD in order to prevent data loss and/or an endless cycle in trying to write/read data under specific circumstances.
Get the latest 10.206 from Hobbes as usual. Contained file "readusb.txt" lists the changes (as usual).

Hardware / USB drivers 10.205 released
« on: June 14, 2016, 09:26:31 pm »

I hope to have fixed the problems with USBMSD.ADD that existed up to and including 10.204.
Just try out and report back.
Available, as always, on Hobbes (, currently in "incoming" directory.

This is difficult to say:
The DDK code that we have available is not up to date. Things might have been fixed in 10.162 that are broken in the DDK code (in short: I can never trust the DDK code).
Additionally even a large file can be transferred in small chunks.
The error case is very specific.
I am on my way of getting the issue fixed. Needs more testing.

It rather depends on what bulk amounts of data you copy. I have observed this when using the WPS to copy back a whole stick's contents. In that case, the WPS (or rather, the underlying copy mechanism) tries to optimize copy speed by combining copy operations into one several large data movement operations. When that happens the driver can fail and I think this is also true for 10.162.
It occured to me when I ran a program (dskxtrt.exe) to view a fixpak file's contents on a USB stick and for one file the CRC would fail but not for the others. I suspect that in the past I had copied this file to the hard disk and now back onto the USB stick and this file has been corrupted already in the past. I cannot remember if at that time I had 10.162 in use.


a word of warning:
there was a serious bug in USBMSD.ADD which might lead to data corruption on USB media (clipped files, corrupted files etc.).
It only happens under very specific conditions but unfortunately it will not show up immediately (no trap or the like).

I am not sure if that error also exists in IBM original 10.162 as I am building upon the DDK code which was pretty much outdated compared to the 10.162 binary. I have now reworked the relevant code but it needs more testing ...

I will prepare 10.205 if time comes.


Programming / Re: Compiling PM app on 2016.
« on: June 04, 2016, 08:39:53 am »
I seem to remember that OpenWatcom comes with all toolkit header files and also import libraries.
That means: you should be able to compile and link a PM application with OpenWatcom without requiring anything else.
The nice thing about OpenWatcom is the IDE. That should make it easier for users to set up a development project.
But of course, if a makefile already exists then it might be easier to just use the compiler/linker that is used in the makefile.

Setup & Installation / Re: JFS format error
« on: May 23, 2016, 01:37:27 pm »
You should try and run chkdsk. What filesystem is currently in use?

Setup & Installation / Re: OS/2 is unable to operate your hard disk
« on: May 23, 2016, 01:27:27 pm »
Unfortunately that will not work that easily.You will also need to change each and every directory path to fix drive letters in config.sys and also in os2.ini and os2sys.ini as well as in any other configuration file you can think of.

May I add something:
I don't know what USB version the OP uses but I am currently working on fixing eject processing in USBMSD.ADD.
In particular, devices with > 1 partition seem to increase problems (but it also happens with large floppy devices or devices that only have 1 partition).
I guess this is due to the fact that there is no proper handshaking between OS2LVM.DMD and USBMSD.ADD of when the device should no longer be accessible (since it has been ejected). It might also be due to the fact that MANY devices (in particular those that do not have removable media like USB sticks and USB hard disks) do not support the LOCK/UNLOCK/EJECT SCSI equivalent commands that USBMSD.ADD uses on bootup (LOCK) and on eject (UNLOCK followed by EJECT).

Wait for version 10.204 ...


Setup & Installation / Re: USB
« on: April 22, 2016, 04:23:09 pm »
To add:
1) don't just install some drivers of my package. Just install ALL of them, the contained readme hopefully explains well enough how to do that. Also follow the hints regading USBCALLS.DLL and USBRESMG.SYS (which are not part of the IBM driver set but serve very useful purpuses around USB for all kinds of USB related things)

2) post the output of hcimonit.exe

3) post your config.sys

That should allow to give some help on what you need to change in config.sys in order to make it work.

By the way: I am working on version 10.203. It tries to solve some USBMSD issues that still exist. USB mass memory devices (like pen drive, USB hard drive) are very diverse and some of them don't properly follow the relevant USB specs. You might have a device that is problematic in which case there is no cure except for buying a different one.


Setup & Installation / Re: USB
« on: April 22, 2016, 01:02:06 pm »
A couple of things:
1) you always need USBD.SYS for ALL devices, no matter what device class. USBD.SYS is the "mediator" that interconnects the client drivers for the various device classes (USBHID.SYS, USBMSD.ADD, USBPRT.SYS, USBCOM.SYS, USBAUDIO.SYS, USBETHR.OS2 etc.) with the host controller drivers that do the "real data movement" work (USBUHCD.SYS, USBOHCD.SYS, USBEHCD.SYS)
USBHID.SYS has the special job that it is serving the "HID" device class which encompasses any USB device the user directly interacts with and by itself is the "mediator" for USBKBD.SYS and USBMOUSE.SYS which serve specific HID device types (keyboard and mouse respectively).

2) use HCIMONIT.EXE to tell you what host controllers you have and what type they are (UHCI, OHCI or EHCI). Then, supposing you have 5 UHCI controllers and 1 EHCI controller you need this as a minimum in config.sys to operate up to 4 USB mass memory devices:

And as ivan has correctly pointed out you of course need to install the file system drivers for all file systems you use.

Events / Re: Warpstock Europe 2016 - actual topics
« on: April 06, 2016, 11:39:01 pm »

Support for accessing unpartitioned/non-LVM USB sticks (large floppy) greater than 2GB

has already been done by me. The only thing that remains to be done is to find a way of how to DISABLE the "partition virtualization" (because that is what is done under the hood in order to access large floppy media) so that you can actually reformat the WHOLE media and truly partition it (that is: to switch from large floppy to a partitioned media).


Hardware / Re: print won't go to default tray
« on: April 05, 2016, 01:28:18 pm »

says it's accepting PCL5 and PCL5e. Have you tried with the printer driver that does PCL5 (I think there is an OS/2 printer driver that does PCL5 but I cannot remember which one ...)

Pages: 1 ... 23 24 [25] 26 27 ... 29