Recent Posts

Pages: [1] 2 3 ... 10
Networking / Re: Updated Samba Client
« Last post by David McKenna on Today at 03:42:20 pm »
Thanks Paul!

  This 4.19.5 server seems to perform about the same as the 4.19.4 version, except WINBINDD will not start - log ends with this message:

[2024/02/25 09:07:58.200000,  5] ../../librpc/rpc/dcesrv_core.c:430(dcesrv_interface_register_b)
  dcesrv_interface_register_b: Interface 'winbind' registered on endpoint 'ncalrpc:' (single process required)
[2024/02/25 09:07:58.200000,  1] ../../source3/winbindd/winbindd.c:1038(winbindd_setup_listeners)
  lp_winbindd_socket_directory() = \socket\winbindd, WINBINDD_SOCKET_NAME = pipe
[2024/02/25 09:07:58.200000,  0] ../../lib/util/util.c:225(directory_create_or_exist)
  directory_create_or_exist: mkdir failed on directory \socket\winbindd: No such file or directory
[2024/02/25 09:07:58.200000,  0] ../../lib/util/become_daemon.c:123(exit_daemon)
  exit_daemon: daemon failed to start: Winbindd failed to setup listeners, error code 32

 Didn't we see something like this before?


EDIT: added net rpc user log for comparison...
Comments, Suggestions & Questions / Re: Hobbes (Files) Reoganization
« Last post by ivan on Today at 02:48:06 pm »
It appears that you are making it much too complicated to find anything with your reorganisation.  Use the 'keep it simple' idea, that way people can just look through the main division , see what is there and select what they want without needing a deep knowledge of OS/2.  Your system assumes that everyone has a deep knowledge of the inner workings of the OS (I have been using OS/2 since version 1.20 and I would be lost with your system.  Most people using it just want it to work, people just trying it out expect to be just able to select something to try without having to know the inner workings).
Comments, Suggestions & Questions / Re: Hobbes (Files) Reoganization
« Last post by Lars on Today at 09:27:06 am »
"wpsenh" makes no sense as every WPS class enhances the WPS. That is the nature of every WPS class.
Networking / Re: Updated Samba Client
« Last post by Paul Smedley on Today at 08:53:49 am »
4.19.5 binaries
smbcl419.dll  (for use with previous 4.19.x ndpsmb.dll):
All executables including server:

This doesn't fix the bug with 'net rpc user', things now die around:
Code: [Select]
file_new: new file fnum 1809131870
file_name_hash: C:/var/temp/samr hash 0xf50f54d6
local_np_connect_send: socket_dir = C:\MPTN\ETC/samba/ncalrpc, state->socketpath = \socket\samr, lower_case_pipename = samr
np_sock_connect_send: sockpath = \socket\samr
push_sec_ctx(109, 514) : sec_ctx_stack_ndx = 1
push_conn_ctx(2061744258) : conn_ctx_stack_ndx = 0
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1
Security token: (NULL)
UNIX token of user 0
Primary group is 0 and contains 0 supplementary groups
pop_sec_ctx (109, 514) - sec_ctx_stack_ndx = 0
np_sock_connect_connected: async_connect_recv returned Can't assign requested address
local_np_connect_connected: np_sock_connect failed: Can't assign requested address
Networking / Re: Updated Samba Client
« Last post by Paul Smedley on Today at 05:40:19 am »
Apologies for the delay.  We were away last weekend (16th - 18th) and I was side tracked last week.

I still think I'm right,  but I haven't found the smoking gun yet.  I did manage to patch the source to 4.19.5 last week - will post binaries at some point.

I'm thinking that /pub/os2/util/wps maybe has too many files. Even that I removed from it the wallpaper changer utilities. (/pub/os2/util/wallpaper)

I'm thinking that it may be slip into:
1) /pub/os2/util/wpsenh (?) - For WPS (GUI) Enhancers
2) /pub/os2/util/???? (?) -  All the "bars", like stuff for WarpCenter, launchpad and new desktop bars. Which is a good name for these ones?
3) /pub/os2/util/wps - For the utilities that register, deregister, classes... and anything else related to WPS.

What do you think, too drastic?
Or maybe just moving the "bars stuff" may be enough?

Programming / Re: SQL running total
« Last post by Doug Clark on Today at 01:30:57 am »
Oops - I realize that some of the entries in ODBCINST.INI still had the path to my Lotus SmartSuite install.   Which will cause an error of not being able to find the driver or setup routines.

These new files have the paths removed - because you really don't need to put them in either ODBC.INI or ODBCINST.INI.  ODBC can find them on the LIBPATH.

Hardware / Re: Netbios network speed pci-pcie adapter
« Last post by Doug Clark on Today at 01:25:56 am »
The connection between the card that plugs into the PCIe slot and the circuit board that contains the two PCI slots is actually a special cable that can only be plugged in to those two cards even though it uses a USB connector.  It cannot be plugged into a regular USB connector on the motherboard.  If it is it will ruin the motherboard and the expansion card - according to the vendor.

The vendor says it does not need a driver, but the instructions with the adapter say to plug the card into the PCIe slot first and wait until the blue light comes on the card/adapter, then plug in the PCI card into the adapter - you need to wait until Windows loads a driver for the adapter.  The tech support forums indicate that on some machines you have to make change to bios settings so that Windows will recognize the adapter.  So I am guessing they built it to use some driver that Microsoft distributes with Windows.

Strangely enough, when I tested it the Intel driver appears to recognize the Intel NIC on boot up  but I cannot connect to my server or transfer any data.

The other issue with this adapter is that they located the power connector right at the back of the PCI connectors, which means you cannot physically plug in any PCI card that is longer than the connector itself, because any power connector you plug in will stick up far enough to block the card from fully plugging into the slot.  The StarTech adapter uses a pig tail for the power connector so that you can fit a card into its slot without any clearance issues.

When I did my test with the Trotwei Blue two connector adapter I did not plug power into the adapter because the power connector would not fit with a PCI card plugged in.  And even then I could not use the same Intel NIC that I used with the StarTech, because of the location of the power connector.  So it is possible there was an incompatibility between the Intel NIC I used with the Trotwei Blue and that adapter.  I used a different Intel NIC with the StarTech.

The Intel Pro 1000 MT that I used in the StarTech is a PCI/PCI-X  card that fits in either a 32 bit or 64 bit PCI slot.  The extra "fingers"  on the card are for when it is plugged into a 64 bit PCI slot. (The card automatically detects which kind of slot it is plugged into.)  But those fingers will not allow it to fit in the Trotwei Blue adapter, even without power connected to the adapter.

Hardware / Re: Netbios network speed pci-pcie adapter
« Last post by Martin Iturbide on February 24, 2024, 10:35:34 pm »
Thanks for sharing Doug

I have a little question about this one that does not work on ArcaOS.
This PCI to PCIe adapter does NOT work:
It looks like that are two adapter sold as one. 1) USB to PCI-e and 2) PCI to USB. Was the PCI-e to USB recognized in ArcaOS as an USB port?
Maybe the one that does not work is the PCI to USB adapter.

Applications / Re: Test build of dooble with qt5
« Last post by Eugene Tucker on February 24, 2024, 09:54:27 pm »
Tom thank yo for providing this for testing. I have found that Dobble runs multimedia much better in Windows than Otter or Falcon. Although Windows 11 security balks at the exe. AAnd it runs better than Dobble QT5 in Arca OS.
Pages: [1] 2 3 ... 10