Sage Line50

I have Sage Line 50 installed on two virtual machines (Win-10 an XP) on
my Linux host system.

The data files are held on Samba shares mapped to drives G, R, S, & T in
both virtual machines.

I can open and run Sage in XP but since trying to do so in Win-10 after
many months of not doing so, I hit trouble.

The first problem was an unexpected request for a log-on password that
has never existed. This was due to a Win-10 update bug that was
eventually overcome.

The second problem is that I cannot access my network drives. They are
physically on the same machine but mapped to Windows drives G to T as
outlined above.

I have tried setting the security to full access for each drive but they
do not become visible from inside Sage.

I have run out of steam. Time for informed advice.

TIA

pinnerite wrote:
I have Sage Line 50 installed on two virtual machines (Win-10 an XP) on
my Linux host system.

The data files are held on Samba shares mapped to drives G, R, S, & T in
both virtual machines.

I can open and run Sage in XP but since trying to do so in Win-10 after
many months of not doing so, I hit trouble.

The first problem was an unexpected request for a log-on password that
has never existed. This was due to a Win-10 update bug that was
eventually overcome.

The second problem is that I cannot access my network drives. They are
physically on the same machine but mapped to Windows drives G to T as
outlined above.

I have tried setting the security to full access for each drive but they
do not become visible from inside Sage.

I have run out of steam. Time for informed advice.

TIA

In Control Panels : Programs and Features : Windows Features,
are you turning on filesharing via SMB 1.0 feature ?

I don't know the software you're using, so can't guess at
whether that would be a factor or not.

From the Start : Run menu, you can enter "control.exe" or
similar (just "control") and that should cause the Control Panels
to appear. You can right-click the taskbar icon and select
"Pin to Taskbar" and this will make it easier to locate Control Panels
in the future.

While something could have happened to the VirtualBox network settings,
I'd check the SMB 1.0 setting as well.

There doesn't seem to be any "plumbing check" in Windows, that can
tell you things about whether file sharing is working. If an SMB
operation is successful, there is a command to give details
about a successful session. But nothing to help you debug
when something is broken. The Troubleshooter items in
Control Panels, aren't thorough enough to find everything.
So most of the time, you are left to your own devices when
something breaks.

Of the three lines in the SMB section of Windows Features, one
is a tick box that *automatically* causes the other software
to be removed. You don't want that line to be ticked...

Paul

On Wed, 16 Oct 2019 21:40:00 -0400, Paul wrote:

pinnerite wrote:
I have Sage Line 50 installed on two virtual machines (Win-10 an XP) on
my Linux host system.

The data files are held on Samba shares mapped to drives G, R, S, & T
in both virtual machines.

I can open and run Sage in XP but since trying to do so in Win-10 after
many months of not doing so, I hit trouble.

The first problem was an unexpected request for a log-on password that
has never existed. This was due to a Win-10 update bug that was
eventually overcome.

The second problem is that I cannot access my network drives. They are
physically on the same machine but mapped to Windows drives G to T as
outlined above.

I have tried setting the security to full access for each drive but
they do not become visible from inside Sage.

I have run out of steam. Time for informed advice.

TIA

In Control Panels : Programs and Features : Windows Features,
are you turning on filesharing via SMB 1.0 feature ?

I don't know the software you're using, so can't guess at whether that
would be a factor or not.

From the Start : Run menu, you can enter "control.exe" or
similar (just "control") and that should cause the Control Panels to
appear. You can right-click the taskbar icon and select "Pin to Taskbar"
and this will make it easier to locate Control Panels in the future.

While something could have happened to the VirtualBox network settings,
I'd check the SMB 1.0 setting as well.

There doesn't seem to be any "plumbing check" in Windows, that can tell
you things about whether file sharing is working. If an SMB operation is
successful, there is a command to give details about a successful
session. But nothing to help you debug when something is broken. The
Troubleshooter items in Control Panels, aren't thorough enough to find
everything.
So most of the time, you are left to your own devices when something
breaks.

Of the three lines in the SMB section of Windows Features, one is a tick
box that *automatically* causes the other software to be removed. You
don't want that line to be ticked...

Paul

Thank you Paul,
It was a brilliant reply but not the correct one as it turns out.

The answer was that it was a known fault that required a registry hack.
I am so looking forward to see what the next update breaks.
Forever the cynic!

https://www.winability.com/how-to-ma...ams-recognize-
network-drives/

Last year I hit the SMB 1 issue with samba and had to find the
instructions to amend smb.conf to get Windows to 'see' my Linux folders.

Thanks for your efforts. Much appreciated.

Regards, Alan