I wanted to express my thanks to those who made LanMan98 freely
available.
The drive in my NAS failed at the weekend and I had been using it with SunFish from RISC OS but have had to resort today to sharing folders on a WinPC instead, like the olden days. I couldn't get LanManFS in Omni to
make a connection (grrrrrrrr) as I think that it only works with SMB (?)
and Win7-64's default seems to not provide it and only CIFS which
LanMan98 understands.
I'm sure I could configure Windows to SMB or install an NFS server but I
have spent long enough rebuilding a few things that weren't backups and I have wasted time on those two things before!!
I think that's the first occasion I have ever managed to network to a PC
at the first attempt (though I did follow the read-me).
If ever it's likely to be updated, there is one bit of functionality
that seems to be missing from the stand-alone version: files dropped on
the iconbar icon are not saved to the root of the share.
Thanks again though. Lifesaver!
I wanted to express my thanks to those who made LanMan98 freely
available.
In rebuilding my single-(failed)-drive NAS, 12,849 files consisting of
about 11GB has to be transferred from a RISC OS (Iyonix) hard drive to
the new RAID1 NAS. Whether a copy is attempted in one lump or one-by-one
of ten tree-topping directories each of about the same size, LanMan98
barfed and lost its connection part-way though the transfer *every* time. [rage face]
In message <[email protected]> Tim Hill <[email protected]>
wrote:
LanMan98 barfed and lost its connection part-way though the
transfer *every* time. [rage face]
Check LanMan98 Run file
and comment out the following line and try again
:
Set LanMan98$ReadRaw ""
As documented Raw Reads can cause issues and it resulted in copying
failures on my NAS and once I commented out that line and rebooted i
had no issues since and thats with over 400Gb of data backed up.
In article <[email protected]>, Doug Webb <[email protected]> wrote:
In message <[email protected]> Tim Hill <[email protected]>
wrote:
[Snip]
LanMan98 barfed and lost its connection part-way though the transfer *every* time. [rage face]
Check LanMan98 Run file
Oh, duh. I was looking for something in !Help or a settings file about writing files!
and comment out the following line and try again :
Set LanMan98$ReadRaw ""
As documented Raw Reads can cause issues and it resulted in copying failures on my NAS and once I commented out that line and rebooted i had
no issues since and thats with over 400Gb of data backed up.
Thanks for the pointer and reassurance, Doug. I have made the bulk transfer so will have to wait and see how this pans out. I don't know whether raw reads affect writing to the NAS.
In message <[email protected]> Tim Hill <[email protected]>
wrote:
Thanks for the pointer and reassurance, Doug. I have made the bulk
transfer so will have to wait and see how this pans out. I don't know whether raw reads affect writing to the NAS.
I routinely use LanMan98 to back up gigabytes to NAS, without trouble.
I can confirm that the line is commented out in my installation.
I routinely use LanMan98 to back up gigabytes to NAS, without trouble.
I can confirm that the line is commented out in my installation.
I wanted to express my thanks to those who made LanMan98 freely
available.
I looked in Boot.Choices and no LanMan so I presume all its parameters
are stored within the programme.
Any help and advice gratefully received.
On 17 Jun, Chris Newman <[email protected]> wrote:
I looked in Boot.Choices and no LanMan so I presume all its
parameters are stored within the programme. Any help and advice
gratefully received.
The settings are stored within the !LanMan98.Discs folder.
I would suggest backing that up before installing the later version
just in case.
I think that may depend on how LM98 is installed - standalone or
within Omni. My !LanMan98.Discs directory is empty, but mine is
installed for use within Omni. All my mounts are stored within the
normal Choices:Omni.Mounts file. I will try and dig deeper tomorrow.
On 17 Jun, Martin <[email protected]> wrote:
I think that may depend on how LM98 is installed - standalone or
within Omni. My !LanMan98.Discs directory is empty, but mine is
installed for use within Omni. All my mounts are stored within the
normal Choices:Omni.Mounts file. I will try and dig deeper tomorrow.
I'm using it stand-alone.
In message <[email protected]>
Brian Howlett <[email protected]> wrote:
On 17 Jun, Martin <[email protected]> wrote:
I think that may depend on how LM98 is installed - standalone or
within Omni. My !LanMan98.Discs directory is empty, but mine is
installed for use within Omni. All my mounts are stored within the
normal Choices:Omni.Mounts file. I will try and dig deeper tomorrow.
I'm using it stand-alone.
Indeed I do as well.
From the Readme file with LanMan 2.08, it says the following:
Installation for use as a standalone application ================================================
LanMan98 2.07 onwards is supplied ready-to-use as a standalone RISC OS application, and does not need to be modified in any way before use.
Simply copy !LanMan98 to your main drive - perhaps in the Network(ing) folder, or Apps. Whenever you wish to use !LanMan98, just double-click
the application, or better still place the application in your !Boot,
inside the Choices.Boot.Tasks directory, so that it will be invoked automatically when you switch on your computer.
In article <507bd22e5c.chris@mytardis>,
Chris Hughes <[email protected]> wrote:
In message <[email protected]>
Brian Howlett <[email protected]> wrote:
On 17 Jun, Martin <[email protected]> wrote:
I think that may depend on how LM98 is installed - standalone or
within Omni. My !LanMan98.Discs directory is empty, but mine is
installed for use within Omni. All my mounts are stored within the
normal Choices:Omni.Mounts file. I will try and dig deeper tomorrow.
I'm using it stand-alone.
Indeed I do as well.
From the Readme file with LanMan 2.08, it says the following:
Installation for use as a standalone application
================================================
LanMan98 2.07 onwards is supplied ready-to-use as a standalone RISC OS
application, and does not need to be modified in any way before use.
Simply copy !LanMan98 to your main drive - perhaps in the Network(ing)
folder, or Apps. Whenever you wish to use !LanMan98, just double-click
the application, or better still place the application in your !Boot,
inside the Choices.Boot.Tasks directory, so that it will be invoked
automatically when you switch on your computer.
Yes. I've read all that.
I use LanMan stand alone. It is loaded using the Run list in
Configuration.
If I drop the new LanMan over the old will it update nicely or will I
lose Local Name, Server name, Share etc that I set up when first using it?
I use LanMan stand alone. It is loaded using the Run list in
Configuration.
If I drop the new LanMan over the old will it update nicely or will I
lose Local Name, Server name, Share etc that I set up when first using it?
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 714 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 141:26:24 |
| Calls: | 12,087 |
| Files: | 14,998 |
| Messages: | 6,517,442 |