MX Linux Forum

After many weeks of frustration I have finally cracked it.
The last Win10 upgrade switched off the required client. Under "turn Win features on and off" I just needed to check the box against SMB 1.0/CIFS option and all began working again.
I hope this helps someone else.

Thanks. But what's puzzling me is the required server name.
W10 sees the MX files fine, but the MX machine doesn't see the W10 files, pesumably because I have not nderstood the corect servername.

I have my main MX11 machine and a Win10 machine which used a Homegroup to talk to each other and read files both ways, no problems.
Then the last Windoze update wrecked all that, and I understand they have removed the homegroup facility.
I have been through the recommended settings in Win10 which ...

Thank you, that has explained it all.
And, yes, it was a typo, should have been MX16.

How frequently does synaptic check for updates, and is there any way of controlling the frequene of this on MX 11?

It's getting worse. I seem to have lost the original display format. But I have got a red record button now.
But playing from the camera now produces no display on the screen either - at least it was doing that OK.

In File Manager there's no sign of the video camera, so no hope yet of just ...

Interesting. Not sure how I get the advanced GUI?
At present, I see a Record option in the pull-down menu, but it's greyed-out, so not useable.

I got a couple of filenames which I had specified in vlc. They appeared afterwards as [fname].mpg4 but on trying to play them vlc continued for the length of the recording (short, to test it) but without any video shot being displayed. Suggests to me that they were blank files, at least as far as ...

I am trying to capture videos from a Panasonic camcorder (tapes) to my MX16 system using VLC Media Player.
I have got as far as being able to watch them in vlc, but I have failed to capture the video file to hard disk so that I can then edit the videos. The furthest i have got is to produce a file ...

I think I have found the cause of the problem.
So once again it's Thank You to all who offered help, and this thread can be regarded as closed.
It seems the problem was something to do with a faulty PS2-to-USB adaptor wich somehow caused the OS to see the mouse as a barcode reader instead of a mouse ...