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 - Neil Waldhauer

Pages: 1 ... 26 27 [28] 29 30 ... 37
Networking / Re: Samba users and groups
« on: September 10, 2015, 05:52:35 pm »
Herwig Bauernfeind let me know that Crypt is a part of RXCRYPT.DLL, which was not on my libpath.

I had installed the rxlib4smb.wpi from the SAMBA website, but somehow I was missing RXCRYPT.DLL. I installed it again, and Users and Groups now works as expected.

Setup & Installation / Re: Networking eCS & Win 7 new article !
« on: September 09, 2015, 09:18:31 pm »
I've got the evfscli, but I didn't get the mount command to work. Some part of the syntax must be wrong, because it gives SYS0123.

When I have the server up and the wrong npdspb.dll in the browsing machine, any file that is read by the client gets its timestamp updated. So I need to replace a bunch of files with wrong timestamps, but no other problem. This problem was fixed by the Oct 2013 update to ndpsmb.dll, which is not found on the eCS 2.2 beta II installation DVD. I always update after installation from a thumb drive before connecting to my server.

Edit: I've got it working now. The command line I used was:

Code: [Select]
evfscli attach r:


Networking / Re: Samba users and groups
« on: September 07, 2015, 03:35:24 pm »
You recommend backing off from the more recently released 3.3 to the older 3.5? Why?

Networking / Samba users and groups
« on: September 06, 2015, 03:54:52 pm »
I'm using SAMBA server 3.3, and I have a problem with users and groups.

Using SAMBA users and groups, I cannot add a user. The dialog is filled out, but when I click OK, the error is

Line 68 of PB_AddUserOK_Click in smbusers.VRM

password.nx - Crypt(VRGet('EF_passowrd', 'Value'), salt);

I look for a program named Crypt, but nothing is found.

This is also reported in trac:
The bug has been assigned to Herwig Bauernfeind

Events / Re: Warpstock 2015 presentations
« on: August 31, 2015, 08:18:21 pm »
I just added this presentation by David  Azarewicz to the website:

Arca Noae Device Drivers: Recent Progress and Future Plans

In this session, we will review the progress and future plans of some key drivers for OS/2. We will cover some of the issues that were encountered and the solutions that were implemented. There should also be time to address questions from the audience. There has been some exciting progress in the past several months so you do not want to miss this session.

Networking / Re: windows 7 does not see os/2 device
« on: August 27, 2015, 02:42:33 am »
OK, I'll update Suntan Special next week when I get back from vacation. I don't use Win 7, so 2.1.5 was always good enough. I sure hope the really bad bugs are also fixed in 2.2.

Edit: It's updated now. I tested the beta for the worst bugs, and found it to be clean.

Networking / Re: windows 7 does not see os/2 device
« on: August 26, 2015, 05:46:36 pm »
It is somewhat important to remember that when trying to use Win 7 shares that the password used is the one for the Win 7 machine. I think you created the same password for every machine, but it really makes no difference what your password is on the eCS machine.

Where does it say that you need a beta SAMBA client plug-in to connect to Win 7?

Setup & Installation / Re: Networking eCS & Win 7 new article !
« on: August 23, 2015, 03:52:56 pm »
So it looks like you are installing the older 3.5 server rather than the newer 3.3 server.

On either, I think it's a good idea to check on how attributes and timestamps work before committing to a production environment. The 3.3 server has been tweaked to where I can use it. I know there has been work on KLibC to try to make permissions, timestamps, ownership and groups work. But OS/2 is not the same as Linux, so be careful.

On my production server, I have scripts to restore a lot of key files from backup after an bad client connects.

Installation of 3.3 always crashes at the end when creating the admin user. Users and Groups always crashes in the same place. I use some rexx scripts in the \samba directory to add users. Windows 7 can use my server. I'm very inexperienced on Windows, so more of a cookbook is needed. I wonder if my Win 7 Enterprise is different from others for networking.

How do you automatically connect after a reboot?

Setup & Installation / Re: Networking eCS & Win 7 new article !
« on: August 22, 2015, 08:50:03 pm »
I can't get the eCS EVFS-based SAMBA to connect at boot time. It will connect later, but I can't connect automatically. Any idea how to do this?

Networking / Re: windows 7 does not see os/2 device
« on: August 10, 2015, 10:10:46 pm »
Things look good from the end.

You might make sure that the Windows 7 machine has workgroup, userid and password set the you think they should be.

Networking / Re: windows 7 does not see os/2 device
« on: August 06, 2015, 04:59:04 am »
I think you see Tobopeep (eCS 2.2b2) now from Windows 7 because the Samba Server is running.

I hope that this article on networking, which was in the first reply, will help get sharing to work.

To Gregory, I'm using Version 3.3.16-eCS 1.1.4-804. I'm testing Samba 4, which has not been released yet.

Networking / Re: windows 7 does not see os/2 device
« on: August 06, 2015, 12:28:33 am »
Well, Arthur, it looks like SAMBA is not started. Try the "Start SAMBA server" icon and see if the status changes to "running". Once SAMBA is running, the shares may be visible to both OS/2 and Windows.

Nice information, Dave, about getting IBM File and Print Client to work with Windows 7.

Looking at the CUPS howto, I see a pretty good description of how to download and install CUPS. (Thanks, Pete!)

A couple of things are lacking. First, about shopping for a printer. The method today is to buy a printer based on what the vendor would most like to sell, then try it on Cups, and if that doesn't work, then abandon eCS and use some operating system that supports printers.

A better solution would be to collect the list of printers that Cups supports, and present it pretty clearly so you can see the supported printers. To test the list, take a Sunday newspaper, and check Cups support for each printer that you find.

Second, about apps support. Show configuring and using Cups support for Open Office, Firefox and PMView (feel free to substitute apps that you use). Especially show printing on an envelope or other non-standard form. I'm finding that printer support is actually better than back in the IBM supported days, but you have to do a lot of tinkering, research and waste a bit of paper to get there.

A Warpstock attendee asked me if we could have a presentation about hand editing PPD files. If that's what it takes, I'd like to see that described. My printer works because I edited the PPD file to take out unsupported characters / languages.

Networking / Re: windows 7 does not see os/2 device
« on: July 23, 2015, 03:55:48 pm »
When you get a chance, please show us the Samba Status Monitor, Daemons screen so we can see if Samba is running.

Tobopeep has PMVNC server installed, so if you start that, you will be able to remote control Tobopeep, too.

Networking / Re: windows 7 does not see os/2 device
« on: July 22, 2015, 04:12:02 pm »
Samba Server is not installed with eCS 2.2 beta 2, but it is installed on my eCS preloaded systems.

The Quick Guide doesn't really address users and has a link that looks like it went out of date.

I always use usernames and passwords for my networking. Can Windows and SAMBA work without them, as Arthur is asking?

Another thought is about name resolution. Arthur: do the Windows machines know Tobopeep by name, or just by IP address? It looks like you've got some kind of name resolution configured. Personally, I just use the hosts file on each machine.

Pages: 1 ... 26 27 [28] 29 30 ... 37