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 - David McKenna

Pages: 1 ... 4 5 [6] 7 8 ... 51
76
Networking / Re: Updated Samba Client
« on: January 03, 2024, 01:15:09 pm »
Paul,

  I quickly tested both of these new ndpsmb.dll's, but neither helped with the \software\os2 directory. Tried with ea support on and off on both the server and client, but no difference.

 The \software\os2 directory contains 6 directories and over 2500 files for over 22GB of data. By far the largest directory on the disc.

 Gotta run to work... more testing later.

Regards,

77
Networking / Re: Updated Samba Client
« on: January 03, 2024, 04:03:01 am »
Guys,

 C:\OS2\SYSTEM is on the DPath and OSO001.MSG exists there. It is indeed just the \software\os2 folder that does not display. I have 'Supports EAs' turned off in the ndctl program (always do), so it should ignore EA's - does the plugin honor that (it is not in smb.conf - I'll add it)? I can also clean EA's in that directory on the server.

 That last line is the last thing I did before collecting the log: Did a 'dir' on the N:\software\os2 directory from the command line, and got the 'SYS0318: Message file OSO001.MSG cannot be found for message  0109.' message. That the log says 'software\os2\OSO001.MSG' is kinda bizarre - that file is not in that directory.


Regards,

78
Networking / Re: Updated Samba Client
« on: January 02, 2024, 10:44:49 pm »
Paul,

 Yes, I meant that I still get the 'out of memory' problem when sharing the root of a drive with that new build of smbd.exe...

  Attached is the log I got when I started ndctl, then tried to navigate to the folder that doesn't display via WPS on the shared drive, then by command line, then shut down ndctl.

Regards,

 

79
Networking / Re: Updated Samba Client
« on: January 02, 2024, 12:37:56 pm »
Paul,

  No improvement with this one unfortunately (not any worse either). I set my smb.conf on my client to:

[global]
   workgroup = IBMPEERS
   loglevel = 2
   client min protocol = NT1
   log file = C:\MPTN\ETC\samba\log\log.smbd.%U.%M

 and restarted ndctl, but I am not getting any logs. How do I set up logging on the client side?

Regards,

80
Networking / Re: Updated Samba Client
« on: January 02, 2024, 02:24:19 am »
Hey Dariusz,

  What server and version is the NAS running? I have only seen the '0 files' issue on OS/2 SAMBA server versions after 4.11 (which does not do it) (Paul's 4.13, 4.15, and now 4.18 all do it when serving a root directory). Seems like there is something in the OS/2 client that triggers this phenomenon, because Windows clients don't do it...

Regards,

81
Networking / Re: Updated Samba Client
« on: January 02, 2024, 01:41:18 am »
Paul,

  Good questions..did some testing-

 I tried using a Windows machine (this is with the updated smbd.exe on the server) when the OS/2 machine showed '0 files' and Windows worked! Windows works fairly good with the 4.18 server on OS/2 with the new smbd.exe (maybe a little slower than the 4.11 server) - both when sharing the root of the drive and a subdirectory.

 Yes, when I restart NDCTL after I get the '0 files' condition on OS/2, it starts to work again. For awhile... There are no traps on the server and don't need to restart it.

 I tried sharing only one folder on my share drive (not the root), and I have yet to get the '0 files' condition on OS/2. Been at least an hour now and still good... except:

 There is one folder I cannot browse on the OS2 client. It has about 2500 files and 6 directories in it. It worked with the 4.11 server (took awhile to populate), but I end up with a '0 files' condition (takes about 90 seconds while the WPS is blocked) with 4.18. Command line doesn't work either, I get this message:

[N:\os2]dir

The volume label in drive N is NETDRIVE.
Directory of N:\os2

SYS0318: Message file OSO001.MSG cannot be found for message  0109.

 Get the same on this folder if I share the root too. Windows can read this folder either way, though it is rather slow dispaying it.

Regards,

82
Networking / Re: Updated Samba Client
« on: January 01, 2024, 03:22:17 pm »
Paul,

  Well, it's back. After using the share for about 20 minutes, it stops working - WPS shows 0 files and directories on the share and the command line shows:

[N:\]dir

The volume label in drive N is NETDRIVE.
Directory of N:\

SYS0008: There is not enough memory available to process this command.
All available memory is in use.

 Mem/v on the client shows:

[C:\]mem /v

Total physical memory:     16,270 MB
Accessible to system:       3,222 MB
Additional (PAE) memory:   13,048 MB

Resident memory:              153 MB
Available virtual memory:   3,596 MB

Available process memory:
  Private low memory:         326 MB
  Private high memory:      2,173 MB
  Shared low memory:          231 MB
  Shared high memory:       1,199 MB

 Mem/v on the server shows:

[C:\]mem /v

Total physical memory:     16,270 MB
Accessible to system:       3,222 MB
Additional (PAE) memory:   13,048 MB

Resident memory:              180 MB
Available virtual memory:   2,948 MB

Available process memory:
  Private low memory:         355 MB
  Private high memory:      2,058 MB
  Shared low memory:          235 MB
  Shared high memory:       1,386 MB

 Not clear why the client thinks there is no memory?

Regards,

83
Networking / Re: Updated Samba Client
« on: January 01, 2024, 02:38:33 pm »
Hey Paul!

  Now it works... thanks! I'll test for awhile and see if I get any of the issues I got with the last 2 versions - but a quick test shows I can browse with the WPS and open files (JPG and MP3) and move stuff around...

Regards,

84
Networking / Re: Updated Samba Client
« on: January 01, 2024, 04:33:01 am »
Happy New Year Paul!

 I tried this smbd.exe, and did the exact same routine as the last logs (start server, then attach client to share, then try browsing with WPS (shows 0 files or directories), then dir on root of share drive from command line (says pipe has ended), then stopped server and collected logs. No exceptq file was created this time, and no trap shows in the logs - attached.

Regards,

85
Networking / Re: Updated Samba Client
« on: December 31, 2023, 10:28:19 pm »
 Hey Paul,

 Yeah, I already tried changing to C:/MPTN/ETC/samba/spool/EPSONXP- but it didn't help... left it like that though, just in case.

Regards,

86
Applications / Re: Test build of dooble with qt5
« on: December 31, 2023, 06:27:58 pm »
Tellie,

  How about your settings - do you have --single-process set? How about 'Animated scrolling'? Might be worth comparing the settings on the desktop with the settings on your laptops...

Regards,

87
Networking / Re: Updated Samba Client
« on: December 31, 2023, 05:03:35 pm »
Paul,

 No, don't get anything to show up, although the share is mounted OK. I have now tried Linux Mint, Windows 7 and Windows 11 and they won't work either (Linux gave a 'software error', both Windows appeared to connect, but are blank). Tried starting just smbd.exe object but no help

 I'll attach a log and example exceptq file. The log shows many traps in smbd, but they are all almost exactly like the one uploaded. I started the server, then attached from my ArcaOS client, then tried to browse with the WPS, then did a 'dir' on the command line in the share root, then shut down the server and collected the log. Maybe there is a clue in there somewhere...

Regards,

88
Applications / Re: Test build of dooble with qt5
« on: December 31, 2023, 01:41:58 pm »
 Hi Tellie,

 You say only on your laptops... what happens if you plug in a USB mouse and use it - is it still slow? Maybe there is a mouse driver issue with your mouse pad... I don't see it here with my laptops though. There is a test Amouse driver at ArcaNoae you could try - I needed it for one of my laptops for other reasons.

Regards,

89
Applications / Re: Update of ScummVM possible?
« on: December 31, 2023, 02:53:19 am »
Hey Paul,

  Gave this one a try, and like the last one, it needs the contents of \scummvm\share\scummvm copied to the same directory as scummvm.exe. Once that is done, it starts up fine. Tried to run Drascula (which works with the last one), but I get this error:

[C:\programs\scummvm]scummvm
WARNING: initWithU32String: Fribidi not available, will use input strings as fallback.!
User picked target 'drascula' (engine ID 'drascula', game ID 'drascula')...
   Looking for a plugin supporting this target... Drascula: The Vampire Strikes Back
Running Drascula: The Vampire Strikes Back (DOS/English)
packet.001: c6a8697396e213a18472542d5f547cb4, 32847563 bytes.
WARNING: SDL_SetVideoMode: SDL_CreateRenderer() failed with VSYNC option, retrying without it...!
WARNING: SDL_SetVideoMode: SDL_CreateRenderer() failed with VSYNC option, retrying without it...!
WARNING: SDL_SetVideoMode says we can't switch to that mode (Surface already associated with window)!

 and it stopped there. FYI - I upgraded to ArcaOS 5.1 using UEFI since you made that last one, so don't know if that might be an issue here...

Regards,

EDIT: didn't work on a non-UEFI laptop either - same error message...

90
Networking / Re: Updated Samba Client
« on: December 31, 2023, 01:21:22 am »
 Paul,

  OK, thanks for that info. I still haven't been able to get 4.18 server to work, even with a pared down smb.conf. Always 0 files and directories with the WPS, and 'pipe has been ended' on command line, but 4.11 server works fine.

 How exactly do you start SAMBA? I have been using the Netlabs utilities to start and monitor the server and up to now they have worked well. Maybe they are interfering with 4.18 somehow?

 Also, what Heimdal needs to be installed? I have 'Heimdal' and 'Heimdal-libs' installed (7.7.0), but I notice there are other Heimdal packages available (but not installed). What do you have installed?

Regards,

Pages: 1 ... 4 5 [6] 7 8 ... 51