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 - Doug Bissett

Pages: 1 ... 98 99 [100] 101 102 ... 107
1486
Networking / Re: Secure ftp server?
« on: September 17, 2013, 05:19:56 pm »
I will admit, that I never tried STunnel with Peter's FTP server.

RSync should work with STunnel, but I haven't tried that either.

There is Open Private Network: ftp://ftp.netlabs.org/pub/unixos2/openvpn.zip, which I have been meaning to check out, but I haven't done it yet. The package doesn't seem to have any documentation in it, other than what is displayed when you try to run it.

Another option, which is probably easier, is to simply copy your files to a USB thumb drive, and carry that with you.

Quote
but no clue if this is doable with stunnel or openssh.

Probably the easy way to find out, is to try it.

1487
Networking / Re: Secure ftp server?
« on: September 17, 2013, 05:44:56 am »
Is there a secure ftp server for eCS? I'm currently using Peter Moylan's ftp server but this does not support login with SSL / TSL. AFAIK with usual ftp the password is transmitted as plain text. What do you use when you want to access files on your server from outside?

You can use STunnel to add secure connections. The docs are reasonably good, and it works well.

ftp://ftp.netlabs.org/incoming/stunnel-4.52-shl-20120515.zip

1488
Utilities / Re: SyncBackup & ssh-askpass
« on: September 16, 2013, 12:11:55 am »
I don't know of any such package, but I think it is unnecessary anyway. Linux users seem to be obsessed by user IDs, and passwords, so that is probably where your problem lies.

I have been trying Linux Mint 15 Olivia Cinnamon 64, which is based on Ubuntu. I got RSync (eCS) to send data to it from eCS by doing this:

Make a directory in the home folder to receive the data (I called it RSyncData).

Create rsyncd.conf in the etc directory (use root to create/edit it). The contents are:
Code: [Select]
    read only = false
    timeout=1200
    log file = rsyncd.log

[backups]
    hosts allow = 192.168.0.100/24
    comment = Backup storage area
    path = /home/dougb/RSyncData
    gid = root
    uid = dougb

My user ID is dougb, and the machine IP address is 192.168.0.101. Change to match your machine, and ID. The log file ends up in the user's (dougb) home directory.

If RSync is already running, it should find the changes to rsyncd.conf. If it isn't running, start it.

I just use RSync, without the SyncBackup front end, so I am not too sure how you configure that. On the eCS end, I used a batch file to do the RSync command:
Code: [Select]
SET RSYNC_PASSWORD=1234567

W:\UTILITY\RSYNC\BIN\RSYNC.EXE -a --delete --log-file=logs/RsyncTest.log U:/acpi/ 192.168.0.101::backups/

This starts RSync, to copy the contents of U:/acpi to the RSyncData folder in Linux. The password is the password for the user defined in the rsyncd.conf file (uid).

Once you get it actually working, you can add whatever else you need (which SyncBackup probably does anyway). The trick seems to be to set the password, in the environment variable, before starting the program, so that RSync can use it.

I use a timeout value of 1200 (seconds), because RSync seems to time out, and cut off the transfer, if an individual file transfer takes longer than the timeout. That happens with large files, and slow connections.

1489
Hardware / Re: Webcam Support for OS/2 and eCS!!
« on: September 13, 2013, 10:32:09 pm »
Okay, now we can display the camera image on the desktop, and we can create a *.BMP file by taking a snapshot. Huge step forward, but now what?  :D

Now we need applications that do what the user wants. And these have to support all the uvc webcams on the world. I know that we are far from that and I don't think we will ever reach that. I am working my way upwards from the usb host controller drivers in the direction of such applications. Right now all usb host controller drivers support isochronous transfers. Many thanks to Lars Erdmann. Without him this would not have been possible.

I doubt if it is necessary (or even desirable) to support every web cam that ever existed. Lars is doing wonderful work.

Quote
For testing these isochronous transfers I had to modify my usbecd.sys device driver. This driver was originally intended for control transfers only. So I could build some usb hardware and play with it. Later on I added support for bulk and interrupt transfers.  Bulk transfers for the CanoScan 4400F and interrupt transfers for Pen and Touch devices. So usbecd.sys is one way towards these applications. However usbecd.sys will be a bottleneck. It can only handle one isochronous endpoint and all its iso buffers must reside in one 65535 bytes memory block. I am not going to improve that. This driver is for testing purposes only.

I know that the source is available for older versions of usbecd.sys. I would think that the new source could be the basis for developing more specific drivers. I personally don't know much about that, but there should be others who have some knowledge, and interest.

FWIW, I use usbecd.sys with mACPUPS, to communicate with my APC UPS. It works well...

Quote
Another way would be usbresmg.sys -> usbcalls -> libusb -> ported linux based applications. However, all these three components do NOT currently support isochronous transfers. Yet another way might be via a new usbvideo.sys driver that ties into the multimedia subsystem. What is the right way to go? Who is going to do that? I cannot do it all.

I know that VLC, in Linux Mint, will support the camera in my ThinkPad L530. Apparently, it can also do communications, but I haven't looked at what it can actually do. It uses something called a "Capture device", to do it. I assume that a "Capture device" is some sort of driver. Some study of what VLC is expecting, could lead to a method of transferring data into VLC, for further processing.

The "right way to go" is, as usual, the easiest, and most flexible, way to do it (usbvideo.sys, I would expect, but I am far from being an expert). Who? That is, as usual, one of the biggest problems that we have. I don't have the expertise, but I think there are a number of people who could do it. Your work, supported by Lars' work, has allowed capturing the data, and it can convert that into a moving picture. Now, we need a way to make that picture available to other programs, for further processing. I think the other programs already exist (but may require some tweaking to make them work in eCS or OS/2). VLC, for example, should be able to handle streaming video, from a device driver.

1490
Hardware / Re: Webcam Support for OS/2 and eCS!!
« on: September 13, 2013, 04:18:27 am »
Quote
The latest release of the latter appears to be from August.

Actually, version 11.04 is from Sept. 6. David apparently removed something that Lars had submitted. I didn't try the 11.02, or 11.03 versions. The new camera support does not work with the 11.04 version, it does require the 10.195 version, from Lars, that is at HOBBES. What will be in eCS 2.2 is anybodies guess, at this time.

Okay, now we can display the camera image on the desktop, and we can create a *.BMP file by taking a snapshot. Huge step forward, but now what?  :D

1491
Quote
-> but what is working mostly is the sound with Youtube videos inside Firefox!

Interesting...

Looking at YouTube in Firefox, on my ThinkPad L530, the sound seems to be much clearer than "normal". I am still hearing some noise, that sounds like static on an old radio, but it is not repeating.

I am a little suspicious that the problem is caused by the Dolby support, but I don't know how to turn that off, or on (the settings don't seem to carry over from windows). It is possible that the YouTube videos are using some sort of Dolby support, or they may turn it off. A promising development, is that I can use the sound with Linux Mint 15 Cinnamon 64 (it actually sounds better than windows). Perhaps what we need, among other things, is an updated driver, based on the latest Linux code.

I got a mini Display port to HDMI adapter. It doesn't seem to do sound, even in windows (I may be missing something), and I haven't found a way to turn it on in eCS (video, or sound).

Good to hear that you got WiFi to go. Now, if we can convince some newer hardware to work, things will improve, but it looks like Multimac will be the answer.

1492
Hardware / Re: Webcam Support for OS/2 and eCS!!
« on: September 12, 2013, 09:43:12 pm »
Well done, and thank you, to all involved.

I have a Ricoh camera in my Lenovo ThinkPad L530 (it seems to be identical to the XT230 hardware). Once I figured out that the device name in the instructions is wrong, and corrected it, it works as advertized.

The instructions say:
Code: [Select]
DEVICE=C:\OS2\BOOT\USBECD.SYS /D:5986:02D2:0011 /N:$X230TD$but when I use that, the programs complain that they can't find the device $RICOHC$ (note the last "C"). After I changed the command to:
Code: [Select]
DEVICE=C:\OS2\BOOT\USBECD.SYS /D:5986:02D2:0011 /N:$RICOHC$it is working well (except for the known limitation).

1493
Hardware / Re: eCS on an Asus X55U?
« on: September 12, 2013, 06:46:44 am »
Quote
If waiting for eCS 2.2 is better choice than trying to use eCS 2.0, I might try installing eCS 2.0 onto my netbook with Win 7 limited on it.

I would think that eCS 2.2 GA would be better than eCS 2.0. If you have access to Software Subscription, you could try eCS 2.1. The current beta eCS 2.2 is not usable, unless a new one has been released, as I write this. If you do decide to try eCS 2.0, you should review the information in: http://hobbes.nmsu.edu/download/pub/os2/doc/eCs-2-on-modern-laptop-win7-rev-1.zip and http://hobbes.nmsu.edu/download/pub/os2/doc/TAMING_WIN7_V0_2_1.zip.

One thing to be sure that you do, is create the recovery disks (DVDs), so you can get back to where you started.

Another option, is to try eCS (any version, but 2.1 or newer is best) in a Virtual machine. I find that eCS 2.1, and a patched up eCS 2.2 beta, works pretty good in VirtualBox, under Win7 (home premium and PRO 64 bit). Just be sure to enable the virtual machine extensions, in your BIOS.

1494
Programming / Re: Test build of GCC 4.7.3 available
« on: August 31, 2013, 05:52:14 pm »
Quote
Not that it seems that too many people care (based on the level of response to the initial build)

Paul, you should know by now, that three things come into play here:

1) People don't say anything when something works. When it doesn't work, most users assume that they are doing something wrong, and will spend some time trying to figure it out for themselves, before reporting a problem.

2) It is nearing the end of summer, in the northern hemisphere, so people are busy enjoying what is left of it, leaving little time for #1..

3). EVERYBODY is waiting for eCS 2.2 to show up again. (Hopefully, they get it right this time).

FWIW, I downloaded your previous attempt, meaning to get around to trying it, but #2 has intervened. Now, I will wait for your new version, and I still won't have the time to try it out. #3 will take priority, when it shows up.

Never fear. ALL eCS (OS/2) users appreciate what you do.

1495
Quote
I will be waiting for a Mesys fix.

You, me, and a lot of other people are waiting for a lot of things. Most people don't even know that they are waiting for the fix, but it looks like any new hardware (especially laptops) will require it.

Quote
I would like to have more because there are more applications I would like to run.

Actually, physical memory has very little to do with how much memory applications can use. The swapping system works very well, and with modern hardware, it becomes less noticeable because of the speed. The trick is to allocate a large enough initial swap size that it doesn't end up thrashing. That is why I suggest a 50 meg initial size, which can be increased, if necessary. There are a few things that need real memory (like VirtualBox), but if you start those first, the swapping system will look after the rest.

Quote
Found that the mb has lots of options.

Unfortunately, my L530 has very few options, and I have tried everything that would seem to be safe to try. It seems that eCS needs to be trained to skip over stray memory holes, that seem to pop up anywhere in memory. IMO, UEFI is poorly designed, and even more poorly documented, but I suppose that is to be expected, considering where it came from.

1496
I have an Intel DH77EB motherboard which has eCs 2.1 installed. To get it to work I had to install the updated ACPI. The system runs but only reports 512 MB  of memory. It has much more. I had heard this could be a Boot Loader issue. Can anyone shed more light on the status of this?

I have a Lenovo ThinkPad L530 that has the same problem (4 GB installed). It is caused because there is a memory hole at the 512 meg mark, that eCS doesn't know how to work around. I have tried both the OS4, and QSINIT, packages, but they don't help. QSINIT may give you some interesting information, but it won't fix the problem, unless you can determine what is causing the memory hole, and remove the cause.

I have heard that somebody is looking into the problem, for Mensys, but I suspect that it is on hold, until eCS 2.2 is finally released. FWIW, eCS works pretty well in 512 meg. Just give it a swap file initial size of about 50 meg (adjust as necessary), and hope they can fix it.

The other option, is to run eCS in a virtual machine, under an OS that can work around a memory hole. I use VirtualBox under Win7 PRO 64 bit, and it works pretty well, although I have not really stressed it much. If you do that, I suggest NOT using the VirtualBox multi CPU feature. ECS doesn't seem to like it. You also need to enable the virtual machine support in the BIOS to be able to run eCS in VirtualBox.

1497
Applications / Re: os4apic.psd is released
« on: August 24, 2013, 05:38:31 pm »
Quote
Just released ! Updated OS4 Kernel

I tried that on my Lenovo ThinkPad L530. It is just as broken as the earlier version was. As soon as the actual boot starts (after the OS2  loader menu is responded to, or times out), the machine immediately reboots. This is long before OS2APIC, or OS4APIC would get involved.

I also see that there is a new QSINIT, which works a little better. At least the machine will boot.

I also tried the OS4 package on my antique Athlon machine. It seems to work there, but, from what I have seen, adds nothing that isn't in the IBM stuff.

Quote
Roderick, you don`t want to answer

I would hope that Roderick is working at getting eCS 2.2 out the door, in good shape. I would be surprised if he has been here since his last post. I also think it is not wise to discuss details with Roderick. He knows a bit about the overview, but I am sure that he knows very little about the details.

1498
Hi Sigurd.

1. I think that Andi has it right (or, very close to right). XWLAN triggers DHCP activity after it gets connected. Think of it as plugging in the cable on a wired NIC. Nothing can happen, until the cable is connected. The same is true of wireless. Nothing happens until it is connected. XWLAN is the tool that is used to "plug in the cable", then it starts the configuration for TCPIP. If it cannot get connected, it will not attempt to start the DHCP configuration tool.

The power setup seems to be stored in the device (at least in Intel devices). If you do not turn off all power control to the device (only possible in windows, AFAIK, and it is in the device setup, not the system power controls), it remembers that it is supposed to reduce power consumption after a while. The first power reduction thing that seems to happen, is to turn off the radio, which effectively disconnects the cable (possibly only in one direction). It seems that GENMAC doesn't (or doesn't know how to) reset the timer, so the radio gets turned off at some random point, and it will stay off, until something turns it back on (usually reboot).

A "public" hotspot usually has no security (known as an "Open access point"), so XWLAN doesn't really need to do anything special to connect (no password, and no encryption negotiation), so it is more likely to succeed.

You may also want to try an updated SUPPLICANT (the part of XWLAN that actually does the connection). The last one that I tried is http://smedley.id.au/wpa_supplicant-2.0-devel-os2-2012-02-25.zip. You can also use the XWLAN menu to make the supplicant visible, so you can see what it has to say, when it attempts to connect. From memory (I haven't got XWLAN installed, at the moment), RMB on the widget, and select Supplicant (or whatever it is - third from the bottom???), and click Visible. A window will open. The contents usually make a bit of sense, and may indicate what the problem is.

1499
Hi Sigurd.

1. I found that I needed to turn off all power control for the wireless NIC, in windows, on my T43, or it would run for a while, then quit. It seems that what windows sets, gets remembered in eCS.  I found a setting in the NIC settings to do that so it was set separately from the windows system power controls. I don't have access to the T43 any more (my brother has it). It also has the problem where it would not work with WPA2, but did work with WPA (WPA2 worked in winXP, of course). I think there is a problem in the GENMAC interface between the windows driver, and XWLAN, which means that it will not get fixed. WPA seems to be reasonably secure. Hopefully, Multimac, for wireless devices, will sho up sooner, rather than later.

6. USB 3.0 will, finally, make USB useful for large media storage. USB 2.0 is usable, but far too slow when you start doing gigabyte data transfers. A better interface is eSATA. I have one hard disk enclosure with that feature. It only runs at SATA I speeds, but that is pretty acceptable. Unfortunately, it seems that eSATA has not gained much support, and I don't see it on newer systems, for some reason. I am able to leave the USB 3.0 BIOS setting at AUTO on the L530, and it seems to work okay.

7. I think the USB widget will work okay, once they finish fixing it. The interim version, that I have, seems to be okay, so far (a couple of weeks now).

1500
Sigurd:

1, What, exactly, is the device? If there is a Multimac driver for it, use that.

5. Great!

6. It appears that the USB 3.0 port (on my L530) is, by default, attached to one of the EHCI controllers. It also seems that the machine was shipped with the Win7 (Pro 64) driver disabled, so I had to turn it on to get USB 3.0 support (I suspect that they aren't too sure that USB 3.0 support is really working). I don't, yet, have a USB 3.0 device, so all I can do is assume that it works in windows. I can still use the port in eCS, it seems to detect that the device is not USB 3.0, and connects the port to the EHCI controller. I have no idea what it might do if I had a USB 3.0 device. It should use it as a USB 2.0 device, but the dead USB 3.0 controller might mess that up. It should work okay when it is connected to a USB 2.0 controller.

8. It may work, until ACPI gets loaded (still under BIOS control). Then ACPI would take control, and there is no interface to ACPI for those functions. There is a Linux thing for ThinkPads (I don't remember the name), to add those functions, that may be possible to port to OS/2.

9. I tried the OS4loader (haven't tried the latest), but didn't find a way to work around the hole. I also tried the QSloader, which supplied the information that it is a 4K hole, at the 512 meg mark. I couldn't get it to work either. Apparently, somebody is working on the OS2loader, but that is all that I have heard. I suspect that it won't be in eCS 2.2 GA.

Jan-Erik:

5. The sound in my L530 seems to be some sort of hybrid between an Intel device, and a Realtek device (at least that is what windows indicates, in the device manager). The mentioned UniAud does make sound, but each sound seems to be echoed about 20 times, before it stops playing it. Any new sound starts it's own echo, which very quickly becomes a "noise", that eventually tapers off to no sound.

7. A beep at eCenter load is probably caused by one of the widgets. The "fixed" USB widget beeps when it starts, and when it stops (most annoying, but that is supposed to go away for the GA version).

Pages: 1 ... 98 99 [100] 101 102 ... 107