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 ... 8 9 [10] 11 12 ... 51
136
Hallo Ian,

thanks for your info. In fact, I have been playing around with active vs.  passive FTP and yes, Hobbes definitely requires passive FTP to work at all.

But it turns out that the Hobbes FTP server is the problem. I can logon to other FTP servers (IBM, for example) without any problem and browse and switch directories, read files etc.
The only FTP client that works reliably with Hobbes these days seems to be Filezilla under Windows 10. I do not know what magic it does, but it works. What I am going to do is to place my USB driver ZIP into a Windows directory that I have made visible via the guest extensions (the .IFS driver) and then I can send it via Filezilla from Windows 10.

I don't know what they did to the Hobbes FTP server. In the last 20 years before, I did not have a problem. But in the last 2 years, it has become increasingly difficult to upload files.

137
Hi Lars,

A quick question, where is the FTP server you are trying to connect to - on the local network or outside?  I ask this because I find it easier to to use the IP address of the host if on the local network.

For going outside the local network, again I will use the IP address if I know it and I have the tcp port 21 open as well as the udp port 21 open - if using ssh you also need port 22 open for tcp and udp.

Sorry I can't be specific about VirtualBox  because I can't get an OS/2 host to work on my Ryzen based computers.

What I wanteed to do is to upload my updated USB driver set to Hobbes, so yes, I tried to access a remote FTP server.
1) why would I need to open port 21 (and possibly 20 also) at all ? I mean, after all, I am running an FTP client and not an FTP server ?
2) in my desperation, I did open ports 20 and 21 in my router but that did not make a difference. When doing so, I found out that the router only sees the IP address of the host OS (Windows 10) but it does not see the IP address of the guest OS (OS/2) and therefore I could not really open the ports for the guest IP address. On the other hand, it makes sense that the router only sees the host IP address. As far as I understand, "bridged networking" makes VirtualBox assign an IP address to the guest and when the guest sends or receive an ethernet packet, the guest IP address is silently replaced by the host IP address (on send) or vice versa (on receive).

As I said, I am runnning OS/2 as a guest in Virtualbox and not as a Virtualbox host.

138
I am trying to use an ftp client within a OS/2 guest running on win 10 host.
Using Virtualbox, I "selected bridged networking" for the guest. The guest receives it's IP address via DHCP. By the way, I am using a WiFi connection from the host to the router and therefore, the selected adapter for the "bridged networking" connection is the WiFi adapter.

From the guest I can ping the outside world, let's say "www.microsoft.com". I can also use a web browser.
What I cannot get to work is using an ftp client from the guest. I tried the standard OS/2 ftp client and also "nftp" but both ftp clients eventually fail to communicate with port 21 (I guess that is the target port of the ftp server I attempt to connect to ?).

Can anyone tell me what I need to change either in my router or on my Win 10 host so that I can run an ftp client from the guest ?


139
Storage / Re: ArcaOS USB floppy drive letter assignment
« on: October 20, 2020, 09:32:01 pm »
The application is for OS/2.
Hi Greg,
did you receive my two answers for your request?
Lars

140
Storage / Re: ArcaOS USB floppy drive letter assignment
« on: October 19, 2020, 10:12:08 pm »
Another thing to try: boot with only the USB floppy attached but not any other USB stick.
Use switch /A_USAGE:1

141
Storage / Re: ArcaOS USB floppy drive letter assignment
« on: October 19, 2020, 09:54:55 pm »
That is not true. If you have no legacy floppy drive, you can force a USB floppy drive to use drive letter A:
The /A_USAGE switch will do but I forgot the correct value. Try 0,1,2.
It is also possible that you need to load IBM1FLPY.ADD for the "drive letter handover" to work (I cannot remember any more).
Or try the other way and remove it from config.sys.

142
Programming / Re: Creating a RPM package for PMDLL
« on: October 12, 2020, 03:30:18 pm »
Hi

I also tried a different sample, since Ivan posted the Task Buster binaries. So I tried to create a rpm package for it.

But I may be missing something on the .spec, since the installer tells me it required BUSTER.DLL and I had included it on the package.

This is the error I get:

Code: [Select]
[C:\HOME\RPMBUILD\RPMS\I686]yum install TaskBuster-2.00-1.oc00.i686.rpm
Setting up Install Process
Examining TaskBuster-2.00-1.oc00.i686.rpm: TaskBuster-2.00-1.oc00.i686
Marking TaskBuster-2.00-1.oc00.i686.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package TaskBuster.i686 0:2.00-1.oc00 will be installed
--> Processing Dependency: buster.dll for package: TaskBuster-2.00-1.oc00.i686
--> Finished Dependency Resolution
Error: Package: TaskBuster-2.00-1.oc00.i686 (/TaskBuster-2.00-1.oc00.i686)
           Requires: buster.dll
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

Any tips on how I tell the rpm installer that BUSTER.DLL is already included there?

Regards

Hi Martin,
have you looked at https://www.golinuxcloud.com/how-to-create-rpm-package-in-linux/ or similar pages ?

What you need to do is set up a directory structure in some temporary dir to DIRECTLY reflect the directory structure that you specify in %files in the spec file which is also the directory structure that you want to exist or be created on the installation target (for example, an "bin" dir for executables and a "lib" dir for DLLs). You then create a tar file from the files to install that preserves that directory structure.
Once this is done, you need to place that tar file into the subdirectory that "rpmbuild" will look for (installation) sources.
Maybe you should look at the tar file you produced (did you ?) to see what directory structure you have created.

143
Programming / Re: Creating a RPM package for PMDLL
« on: October 11, 2020, 10:44:04 pm »
Martin's problem is not a runtime problem but an installation problem.
Nonetheless, if what you say is true, that also means that Martin will have to change the spec file accordingly.

144
Multimedia / Re: (SOLVED) Broken Audio on MMOS2
« on: October 10, 2020, 01:54:27 pm »
Well,if you install my USB audio package,then you should NOT install the "default WAV device applet" if you also use AN. They have the replacement that you mentioned. My expectation is that their solution should autoselect the USB audio driver as default as soon as you plug in a USB device.

145
Programming / Re: Creating a RPM package for PMDLL
« on: October 10, 2020, 12:40:06 pm »
One Thing is clear by now: you have a screwed installation of yum/rpm.
I suggest you redo the install of yum/rpm via ANPM, if possible. Possibly also python.

146
Programming / Re: Creating a RPM package for PMDLL
« on: October 07, 2020, 09:13:36 am »
1) go to directory \var\cache\rpm\wps\packages and check if you find a file for your package (PMDLL). Have a look at the contained file and check if the string resolves to what you expect it to be
2) try to do a "dry" run of wps-object.exe:
   a) change to directory \usr\lib\rpm\pc
   b) invoke: wps-object.exe /create pmdll "PMDLL_EXE:WPProgram|PMDLL|<WP_DESKTOP>|EXENAME=((%{_bindir}/PMDLL.EXE));ASSOCTYPE=Executable,Dynamic Link Library;ASSOCFILTER=*.EXE,*.DLL;|R"

That should create the desktop icon. Of couse, since the path does not properly resolve, it will not work. But that will let you check if wps-object.exe runs unobstructed. If the latter fails then you know you have a problem with your WPS. If it succeeds, it means you have a problem somewhere else in your spec file or a broken RPM installation that possibly fails in resolving the %{_bindir} variable.

The "R" stands for "replace" in contrast to "U" which stands for "update". Since "update" is the default, you do not need to specify it.

All of this is explained here:http://trac.netlabs.org/rpm/changeset/91

That will also show you that wps-object.exe really is just a simple REXX script that has been compiled into an executable (via the REXX2EXE tool from Veit Kannegieser).

Lars



147
Programming / Re: Creating a RPM package for PMDLL
« on: September 30, 2020, 07:49:44 pm »
Hi Lars, from a cmd prompt,
Code: [Select]
[H:\tmp]rpm --eval %%_bindir
%_bindir

[H:\tmp]rpm --eval %_bindir
/@unixroot/usr/bin

Note that even the second one isn't correct as /@unixroot will resolve here as /w:/usr/bin.
And yes, %UNIXROOT% needs to be set to a drive letter plus colon, though on a single root system such as everything on C:, /usr/bin will work for most programs with exceptions for DOSISH programs that consider / to be the start of a parameter and use a drive letter to tell it's a PATH. Wlink is an example that needs a drive letter when using / as a dir separator.

... and now we are in deep shit trouble because the 4OS2 command line behaves as I have stated but the OS/2 command line behaves as you have stated.

148
Networking / Re: ArcaMapper - Parameter Incorrect
« on: September 30, 2020, 01:10:50 pm »
That sounds like there are two DLLs with identical name but completely different functionality.

Well IO wondered that too, but once i uninstall the Vac++ and reboot, its still broken.

VAC 3.x has the unfortunate misbehaviour to install completely outdated SOM DLLs. And its installer prepends the LIBPATH statement with the path to these outdated DLLs. Therefore, DIRECTLY AFTER installation of VAC 3.x and BEFORE rebooting, you will need to modify config.sys to put this prepended path to the very end of LIBPATH. Likewise, after deinstallation, check that all files are gone and that LIBPATH (and also PATH, HELP, DPATH etc.) are correct (no longer containing paths of the VAC 3.x installation).
SOM is used all across the board, most notably, the complete WPS builds upon SOM.

149
Programming / Re: Creating a RPM package for PMDLL
« on: September 30, 2020, 09:31:30 am »
Try:

Code: [Select]
%wps_object_create_begin
PMDLL_EXE:WPProgram|PMDLL|<WP_DESKTOP>|EXENAME=((%{_bindir}/PMDLL.EXE));ASSOCTYPE=Executable,Dynamic Link Library;ASSOCFILTER=*.EXE,*.DLL|R
%wps_object_create_end

By the way: you can only set the ASSOCTYPE's that actually exists. On my system, "Executable" exists but not "Dynamic Link Library". Check your XWorkplace Workplace Shell Object.
In the end, the "lengthy" string that you specify as the 4.parameter (where parameters are separated by |) follows the setup strings as described in the "Workplace Shell Programming Reference"

150
Networking / Re: ArcaMapper - Parameter Incorrect
« on: September 29, 2020, 11:11:25 pm »
That sounds like there are two DLLs with identical name but completely different functionality.

Pages: 1 ... 8 9 [10] 11 12 ... 51