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

Pages: 1 ... 7 8 [9] 10 11 ... 19
121
Storage / Re: changing USB volume letter
« on: June 18, 2019, 03:56:44 pm »
You can assign a drive letter without losing data by using Logical Volume Management (Simple) in the setup folder.

I think you can assign "None" and get the drive mounted with the next available letter.

I'm not sure how the assigned letter works for old Warp 4 systems, but I recall that it seems to ignore LVM and just mount the next available drive letter.

thank you Neil, I'll try.
I believed could also use DFsee as well but eventually needed some hint

122
Storage / changing USB volume letter
« on: June 18, 2019, 02:49:01 pm »
Hi, I've made an USB stick detectable-handlable on OS2 W 4.52 (Virtualbox guest machine) with DFsee following the precious instructions received here.
Now I realized that the choosen drive letter (G) conflicts with the Shared Folder drive wich is G as well.  When plugged in, the USB volume functionality hangs after being automatically shifted to H letter, it remains locked and often make OS2 WPS not responding as well, so a letter change to a still unassigned drive letter appears to be the solution.
Can you suggest a way to just re-assign the USB volume letter avoiding the whole volume creation process in DFsee, that would wipe all data in it ?
Thank you

123
Congratulations! Something I tried years ago but could not get Ubuntu to automatically start the OS/2 box inside Virtualbox directly and so I failed. Maybe you can share your way to do this. Thanks!

with pleasure:
-from Virtualbox main panel, on "Machine" menu, select "Create desktop icon"
-once you have the desktop icon, open its properties and from the Command field, take (copy) its content entirely
-go on the Ubuntu system settings , find Application Startup preferences, in the opened panel click the Add gadget, you now have the empty Command field so just paste there the command you copied before, give it the name you prefer, confirm/close.
Next time you run Ubuntu, the virtual machine will automatically boot with same preferences you left last time as shutted down

124
Hi all, I'd like to resume the results obtained joining this forum in sept 2018 starting from a very basic iniztial knowledge, maybe someone will read something interesting to pick ideas.
OS2 was my first contact pc system, found preinstalled in a Hyundai pc, 1996. After 4 years I felt forced to switch to Windows XP due to the hardware/software requirements, which OS2 could not follow as needed at that moment.

I just kept remembering OS2 as a vintage old car which was nice to have owned once but with no more chances to drive it again on the today roads.
This till last summer, when on a Windows 10 usenet newsgroup an expert member told that it was not impossible getting an OS2 Warp 4.52 virtual machine full working for VirtualBox but just good to load and leave as-it-is, with not much more to do for real use, except some exciting WPS menu browsing to feel back in the latest nineteens.

Meantime I was aware of the most recent OS2 system adapted distributions; Ecomstation first and then ArcaOS, good to have but not freeware and not even cheap.

Then I found online a downloadable OS2 Warp 4.52 ready-to-boot virtual machine in its first-boot state: ready, go.

Tried to get help for updating/actualization on an OS2 usenet group nearly abandoned, where the only member listening suggested to join your forum.
Ready, go.

From its first-boot situation -I believe corresponding to 1998 HW/SW-, you here have lead me to implement and update much more than expected :  dedicated Guest Addition for VirtualBox including shared folders and display custom resolution, Yum-Rpm packages Manager, USB volume handling, printer configuration, scanning device capabilities (Tame2), XWorkplace, Firefox, VLC, Samba and Netdrive for browsing external directories, and other useful features.

Now, since I like very much  systems on a self-bootable USB stick, and also said that OS2 W4 cannot support itself such capability, I created a self-bootable fully installed Ubuntu 18.04 USB stick, and setted an autostart command for the OS2 Warp 4.5 guest machine (updated as above described) cloned and moved from the initial Win10 host system to the Linux VirtualBox application there.

This is the result: plug the USB stick in, turn the laptop on, select the usb volume to boot, wait about 90 secs, and OS2 Warp 4.52 full screen appears ready to use, you know that is a virtual machine hosted in Linux only for the 5 secs initial Ubuntu splash screen.

Cool.
Thank to you

125
Networking / Re: Samba 4.9.0 based client
« on: June 09, 2019, 12:40:24 pm »
First question, is 192.168.1.84 the IP address of a different separate machine running a SMB/CIFS server?

Second question, what shows up in file manager when you click on 'network'?

Third thing, if you don't have a samba server running no matter what you are doing you are not going to find anything.  For example, on my network I have 3 NAS boxes that each run a SMB/CIFS server, I am also running samba servers on 3 of my computers.  All of those are visible to any samba client on the network.

ok, finally I made it work for Ubuntu host as well !!!


Almost everything was correct, the missing part was that Samba client in Linux must also be configured after installing, in order to set a specific folder for the samba resource and for which user, otherwise it won't be available.

This tutorial was my lighthouse:
https://www.computerbeginnersguides.com/blog/2018/04/27/install-and-configure-samba-in-ubuntu-18-04-bionic-beaver/0

and you the navigator  :D
thanks



126
Networking / Re: Samba 4.9.0 based client
« on: June 07, 2019, 05:23:03 pm »
OK, that still requires that you get the Linux networking setup correctly.

The problem will still be viewing anything on the disks of your win 10 machine. Ubuntu should be able to read the win10 drive partitions (you can do that with a live linux usb/dvd so a full install makes it easy) the problem comes from just how vbox running on linux on usb will see the SMB/CIFS server that only works when win10 is running (since Ubuntu is the operating system when running from your USB, win does not start the SMB/CIFS server therefore any samba drives will not be visible).

ok, I' have had this idea yesterday and have also installed the smb client on Ubuntu, but then responding same "Connection to 192.168.1.84 failed (Error NT_STATUS_CONNECTION_REFUSED)"  as in OS2 when give the "smbclient \\192.168.1.84\home" command in linux terminal.  It could also be the client activation not correctly performed or running.....

127
Networking / Re: Samba 4.9.0 based client
« on: June 07, 2019, 06:55:49 am »
(remember you will not see your win 10 box because it is not running while you are booted into your live linux USB stick).

I hope this helps bur remember I am using a full Linux Mint install on a real computer whereas you are using a live linux from a bootable USB.

I'm using a full Ubuntu 18.04 install, it is on an USB stick but fully installed like it was on a pc.

Not a live usb

128
Networking / Re: Samba 4.9.0 based client
« on: June 06, 2019, 10:51:25 pm »
How did you setup networking for the Linux vbox host? 

If you want it to see anything on your network you have to set it as a 'bridged adapter', at least that is how I have vbox setup in a real Linux Mint machine and I can see everything on my network.

Have also changed the Vbox network setting in "Bridge adapter" as you said but getting same

[C:\]smbclient \\192.168.1.84\home
gethostname failed
gethostname failed
Connection to 192.168.1.84 failed (Error NT_STATUS_CONNECTION_REFUSED)

it is like the Linux resource is not ready for some setting reasons (permissions? name? wrong mounted/unmounted status? .....
Not even appears a password prompt like it was in Windows host, which I would expect as a Linux standard

129
Networking / Re: Samba 4.9.0 based client
« on: June 05, 2019, 10:02:01 pm »
....what about linux (Ubuntu) host? I have same cloned Vbox Warp 4.52 machine, in an Ubuntu 18.04 system fully working in an usb pendrive.
When this USB is plugged in same laptop with Win10 hard disk, Ubuntu can browse every Win 10 directory, but from Warp 4.52 virtual machine the resource call
[C:\]smbclient  \\192.168.56.1\Users

gives this answer:

gethostname failed
gethostname failed
Connection to 192.168.56.1 failed (Error NT_STATUS_IO_TIMEOUT)

also, found the Ubuntu machine static ip address 192.168.1.84 (by ifconfig command),
 if I give
[C:\]smbclient  \\192.168.1.84\

obtain:
gethostname failed
gethostname failed

I presume not getting the correct resource call for Ubuntu (or I'm missing an important part as usual), do you have your own experience to get me on the right path here as well?
 :D
Thank you





130
Networking / Re: Samba 4.9.0 based client
« on: June 03, 2019, 09:01:39 pm »
Server entry is still wrong...

needs to be Server: 192.168.56.1 NOT \\192.168.56.1\

I went for this entry after having tested the different combinations of "\" symbol (only \\ before, only \ after, completely without), and with my choice was the only one without error messages yesterday.
But today the message is  : "The smbfs resource was not mounted to Mount point L:\   Error code: 58"

While the way you suggest gives this error message after pressing DONE: 
"The smbfs resource was not mounted to Mount point L:\   Error code: 65"

Do you have a ndpsmb.log at all?

LOOK BELOW !!!!!

still cannot believe, please don't wake me up!

I kept trying every variation of settings in smbfs parametres, and now I've found it needed the "workgroup" specification in the Workgroup field, and nousers/nopassword in the login table.

This is it, thank you a lot Paul, Sean, Dave, David, Dariusz, Ivan, Wim, everyone who supported me here, hope this thread will be an additional reference for those ones encountering issues in configuring Samba and NetDrive in OS2 Warp 4.52.


131
Networking / Re: Samba 4.9.0 based client
« on: June 02, 2019, 11:16:31 am »
Seems to me that 192.168.56.1 as said by Paul Smedley is correct.

Wim

Hi Wim, as said, the thing is that the resource is available at a "smb:>" prompt in an OS2 command window, and (also said), if it is available there must be available in NetDrive.
Hi Mauro, unfortunately for you I have no experience with smb nor NetDrive at all, so I cannot help you further. Sorry.

ok, thank you anyway for answering.  Samba implementation was tricky but at the end with good suggestions and attempts I succeeded to make it work at least by OS2 command line, while NetDrive is really a mistery. I believe it might be a version issue of application itself or ndsmb plugin version not matching with Samba version (although already tried to change them) or else some implementation is only good for ARCA OS but not for OS2 Warp 4.52.

132
Networking / Re: Samba 4.9.0 based client
« on: June 02, 2019, 09:07:12 am »
Seems to me that 192.168.56.1 as said by Paul Smedley is correct.

Wim

Hi Wim, as said, the thing is that the resource is available at a "smb:>" prompt in an OS2 command window, and (also said), if it is available there must be available in NetDrive. The issue could also be -just guessing- the password request that I skip just by hitting RETURN :

smbclient \\192.168.56.1\Users


gethostname failed
gethostname failed
Enter WORKGROUP\GUEST's password:

here I hit RETURN and I get this :

Try "help" to get a list of possible commands.
smb: \>

then I command
smb: \> dir

and the requested resource's folders are available

  .                                  DR        0  Sat Jul  7 13:06:16 2018
  ..                                 DR        0  Sat Jul  7 13:06:16 2018
  Default                           DHR        0  Wed Sep 26 20:29:58 2018
  Default.migrated                    D        0  Sun Sep  4 19:20:29 2016
  desktop.ini                       AHS      174  Sat Jun 16 17:26:53 2018
  Public                             DR        0  Wed Sep 26 20:28:39 2018
  user                                D        0  Sun Jul 31 08:38:03 2016

                239907945 blocks of size 4096. 178492899 blocks available
smb: \>

133


Same as on Unix, use chmod. Something like (untested)
Code: [Select]
chmod -R 0775 dir/
The -R will recurse through the subdirectory, remove if not needed.

Right Dave, it worked with this command, thanks.

Ivan, I needed to change permissions in two folders due this answers at a OS2 command line:

invalid permissions on directory C:\MPTN\ETC/samba/private/msg.lock': has 0777 should be 0755
invalid permissions on directory C:\MPTN\ETC/samba/private/msg.sock': has 0777 should be 0700

still fighting with Samba implementation, installing from rpm package on OS2 Warp 4.52 is not enough, then I have to move/add myself some files and folders in C:\MPTN\ETC  to get it work

134
Applications / how to change a directory permission level in OS2
« on: June 01, 2019, 07:42:30 pm »
from 0777 to 0775 ?
Same Unix command line?
Thank you

135
Networking / Re: Samba 4.9.0 based client
« on: June 01, 2019, 02:06:24 pm »
Server entry is still wrong...

needs to be Server: 192.168.56.1 NOT \\192.168.56.1\

I went for this entry after having tested the different combinations of "\" symbol (only \\ before, only \ after, completely without), and with my choice was the only one without error messages yesterday.
But today the message is  : "The smbfs resource was not mounted to Mount point L:\   Error code: 58"

While the way you suggest gives this error message after pressing DONE: 
"The smbfs resource was not mounted to Mount point L:\   Error code: 65"


Pages: 1 ... 7 8 [9] 10 11 ... 19