A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

My ReadOnly Problem



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old February 7th 18, 01:45 AM posted to alt.windows7.general
John B. Smith
external usenet poster
 
Posts: 47
Default My ReadOnly Problem

When I added Win7 to my XP install a year or so ago, I installed
Eudora7 on it. It’s pretty old and doesn’t work great but I still
like it and have ton of mailboxes in it and I’m FAMILIAR with it,
which is important to me. I just assured myself Win7 Eudora install
would work in Win7 (did not attempt to bring over all my mailboxes)
then did all email in XP where everything works.

Recently I had a reason to want to actually use Eudora in Win7 so I
attempted to xfer mailboxes over from XP. I had all mailboxes in a
folder I'd named mydata and Eudora install instructions said to
reference that folder during install. So I uninstalled/ reinstalled
Eudora and tried to do that. Alas, when I tried to run Eudora it said
it could not write to Eudora.log, it might be write protected. Right
clicking the mydata folder, Properties, it sure nuff was ReadOnly. But
there was a ReadOnly box that when clicked went clear and when I
Applied it, it looked like everything in mydata folder was having the
ReadOnly attribute removed. Eudora still wouldn’t run and when I
looked at mydata folder again it had turned back to ReadOnly. In fact
if you check it immediately after removing the attribute with
rightclick Properties you can see that it never changed. The mydata
folder resides in Win7 C:\mydata. What did I do wrong? Why can’t I
bring over the folder from XP without it becoming ReadOnly?
Ads
  #2  
Old February 7th 18, 02:11 AM posted to alt.windows7.general
Mayayana
external usenet poster
 
Posts: 6,438
Default My ReadOnly Problem

"John B. Smith" wrote

|In fact
| if you check it immediately after removing the attribute with
| rightclick Properties you can see that it never changed. The mydata
| folder resides in Win7 C:\mydata. What did I do wrong? Why can't I
| bring over the folder from XP without it becoming ReadOnly?

Readonly on folders doesn't mean anything. You need
to check whether the .log file is readonly.
The other things to check are permissions/restrictions
on the files/folder and whether Eudora is looking in the
right place.


  #3  
Old February 7th 18, 02:15 AM posted to alt.windows7.general
Mike S[_4_]
external usenet poster
 
Posts: 496
Default My ReadOnly Problem

On 2/6/2018 4:45 PM, John B. Smith wrote:
When I added Win7 to my XP install a year or so ago, I installed
Eudora7 on it. It’s pretty old and doesn’t work great but I still
like it and have ton of mailboxes in it and I’m FAMILIAR with it,
which is important to me. I just assured myself Win7 Eudora install
would work in Win7 (did not attempt to bring over all my mailboxes)
then did all email in XP where everything works.

Recently I had a reason to want to actually use Eudora in Win7 so I
attempted to xfer mailboxes over from XP. I had all mailboxes in a
folder I'd named mydata and Eudora install instructions said to
reference that folder during install. So I uninstalled/ reinstalled
Eudora and tried to do that. Alas, when I tried to run Eudora it said
it could not write to Eudora.log, it might be write protected. Right
clicking the mydata folder, Properties, it sure nuff was ReadOnly. But
there was a ReadOnly box that when clicked went clear and when I
Applied it, it looked like everything in mydata folder was having the
ReadOnly attribute removed. Eudora still wouldn’t run and when I
looked at mydata folder again it had turned back to ReadOnly. In fact
if you check it immediately after removing the attribute with
rightclick Properties you can see that it never changed. The mydata
folder resides in Win7 C:\mydata. What did I do wrong? Why can’t I
bring over the folder from XP without it becoming ReadOnly?


You might consider trying this
https://www.howtogeek.com/howto/wind...menu-in-vista/

Or you could start with this
https://answers.microsoft.com/en-us/...4a0d495?auth=1
  #4  
Old February 7th 18, 02:18 AM posted to alt.windows7.general
Char Jackson
external usenet poster
 
Posts: 10,449
Default My ReadOnly Problem

On Tue, 06 Feb 2018 19:45:34 -0500, John B. Smith
wrote:

Recently I had a reason to want to actually use Eudora in Win7 so I
attempted to xfer mailboxes over from XP. I had all mailboxes in a
folder I'd named mydata and Eudora install instructions said to
reference that folder during install. So I uninstalled/ reinstalled
Eudora and tried to do that. Alas, when I tried to run Eudora it said
it could not write to Eudora.log, it might be write protected. Right
clicking the mydata folder,


Perhaps a dumb question, but is Eudora.log located in your C:\mydata
folder? If not, you may be looking in the wrong place.

From your description, the issue is that Eudora.log might be
write-protected, rather than its parent folder. Verify the location of
Eudora.log and make sure it's not in a location that Eudora doesn't have
write access to (by default), such as the root folder of that partition
or either of the Program Files folders. If possible, configure Eudora to
put its log file somewhere else.

Properties, it sure nuff was ReadOnly. But
there was a ReadOnly box that when clicked went clear and when I
Applied it, it looked like everything in mydata folder was having the
ReadOnly attribute removed. Eudora still wouldn’t run and when I
looked at mydata folder again it had turned back to ReadOnly. In fact
if you check it immediately after removing the attribute with
rightclick Properties you can see that it never changed. The mydata
folder resides in Win7 C:\mydata. What did I do wrong? Why can’t I
bring over the folder from XP without it becoming ReadOnly?


Forget about a folder being marked Read-Only. That attribute really only
applies to files. At the folder level, it appears to indicate that this
is a special folder in some way.

Read more he
https://support.microsoft.com/en-us/help/326549/you-cannot-view-or-change-the-read-only-or-the-system-attributes-of-fo

See the Cause section:
The Read-only and System attributes is only used by Windows Explorer to
determine whether the folder is a special folder, such as a system
folder that has its view customized by Windows (for example, My
Documents, Favorites, Fonts, Downloaded Program Files), or a folder that
you customized by using the Customize tab of the folder's Properties
dialog box. As a result, Windows Explorer does not allow you to view or
change the Read-only or System attributes of folders.


--

Char Jackson
  #5  
Old February 7th 18, 03:11 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default My ReadOnly Problem

John B. Smith wrote:
When I added Win7 to my XP install a year or so ago, I installed
Eudora7 on it. It’s pretty old and doesn’t work great but I still
like it and have ton of mailboxes in it and I’m FAMILIAR with it,
which is important to me. I just assured myself Win7 Eudora install
would work in Win7 (did not attempt to bring over all my mailboxes)
then did all email in XP where everything works.

Recently I had a reason to want to actually use Eudora in Win7 so I
attempted to xfer mailboxes over from XP. I had all mailboxes in a
folder I'd named mydata and Eudora install instructions said to
reference that folder during install. So I uninstalled/ reinstalled
Eudora and tried to do that. Alas, when I tried to run Eudora it said
it could not write to Eudora.log, it might be write protected. Right
clicking the mydata folder, Properties, it sure nuff was ReadOnly. But
there was a ReadOnly box that when clicked went clear and when I
Applied it, it looked like everything in mydata folder was having the
ReadOnly attribute removed. Eudora still wouldn’t run and when I
looked at mydata folder again it had turned back to ReadOnly. In fact
if you check it immediately after removing the attribute with
rightclick Properties you can see that it never changed. The mydata
folder resides in Win7 C:\mydata. What did I do wrong? Why can’t I
bring over the folder from XP without it becoming ReadOnly?


The ReadOnly flag on a folder is not a ReadOnly flag.

It is "overloaded" by Microsoft, as an indicator that
folder customization is present. It is not intended to
control access to folders. When folder customization is
present, File Explorer can go looking in desktop.ini
for information about just what customization is desired.
You may see a line with "shell32.dll" and a number, and
the number indicates the "view" type to use.

Instead, in NTFS, folders and files have security
settings you can see by doing properties on the items.
Changing who owns the files, from a "mysterious" SID that
Windows 7 doesn't have an entry for in its table, to
your Windows 7 account name SID, may make the contents
usable in Windows 7.

Even when two OSes have an account "Paul" with password "12345678",
they're not the same person. Each account has a long string
of digits. Three clusters of random digits, plus an account
number on the end. Perhaps I'm 1111111111-2222222222-3333333333-1000
on WinXP and on Windows 7 I'm 4444444444-5555555555-6666666666-1001.
So when I mechanically move an NTFS folder from one OS C: to
another OS C:, the owners are in fact quite different. It pays
then, to verify who owns the contents of the folder and
take ownership. You can do this from the Properties of
a file or folder.

User accounts start at 1000. Administrator should be 500. The
groups of digits are randomly assigned during OS installation,
with the intention that no two OSes have exactly the same SID strings.
It's not a GUID, but it's damn close to it in terms of collision
potential.

When you're in a domain (something I might have used at work), there's
a better chance of some consistency seen when you "roam". However,
if you parachute folders from one OS to another in your non-domain
home setup, you should occasionally check to see who owns them.

For example, say I have a well-beaten folder, that's "been everywhere"
in my computer room. I check the permissions and I see.

Owner 1111111111-2222222222-3333333333-1000
Owner 4444444444-5555555555-6666666666-1001
Owner 7777777777-8888888888-9999999999-1000
Owner Paul === the "real" Paul

That would mean that the SID for Paul, the numeric quantity,
the OS could look that up and see that the symbolic name of
the owner is Paul. Whereas for the other three stamps, those
were applied while three other OSes were booted and I was doing
stuff to the folder. Perhaps I needed administrator permissions
to thwart the ownership and move the folder around. And now
there is multiple ownership.

That doesn't hurt anything.

And the only reason for ever mentioning this, is to
have you look in Properties of a folder or file,
to see what kind of a mess is in there. There might
actually be an explanation for "why I can't write that".
Maybe you're not actually an owner. And the numeric
SIDs sitting there, the ones the OS doesn't recognize,
aren't your friends and they're not going to help you.
It's the one with familiar names like Paul, Administrator,
System, that matter more.

You can obviously override things as Administrator or
using the SYSTEM account, but that's just making a mess
for no reason.

And if you use TakeOwn, even that may not have the
desired effect. I don't have this loaded in all my OSes,
mainly because the results have been mixed. *Do Not*
apply that to the top level of C: . You may apply it
to a data-only partition if you want, but even that
is likely to be dangerous. This tool is intended for
exactly the situation you're in - a single folder
that is slightly borked on permissions.

https://www.sevenforums.com/tutorial...-shortcut.html

*******

You can "save" the permissions on a partition with this.

icacls c:\ /save "%userprofile%\Downloads\ntfsCdrive.txt" /t /c

Once you've got the file, you change the (blank!) top line to

..

a single period, which means "current working directory".
That modification to the file is necessary if restoring
the permissions to an entire partition. Like this.

cd /d c:

icacls c:\ /restore %userprofile%\Downloads\ntfsCdrive.txt

Normally, to restore permissions, you must be one level
*above* the object you're restoring. The hack to change
the first line of the file to a period, is intended to
correct that situation and let you do it anyway. As otherwise,
you can't be "one level above C:" as there is no such thing.

I found mention of that issue, here, near the end of the thread.

https://social.technet.microsoft.com...backup-restore

You can play back permissions, to correct them. Things
like Junction Points, icacls won't descend them, but that's
OK because the area you would descend to, gets covered anyway
by other lines in the file.

That's how professionals work on a partition, without
leaving footprints all over the place. The people in these
groups, aren't that careful, and so when someone has
been messing around with their registry or file system,
a forensics person can discover the permissions have been
altered, and figure out what they've been doing. The tools
that allow playback of permissions are there, so everything
is neat and tidy when you're finished :-)

If you want to discover what the SIDs are on the current OS,
you can try:

wmic useraccount get name,sid

The "whoami" command is also good when you're working
in a Command Prompt that you want to verify what credentials
you're using when you go to run a command. You can do more
damage with the SYSTEM account, than any other account
on the computer :-) For example, using pstools.zip from
sysinternals.com, you can become SYSTEM.

psexec64 -msi cmd.exe

... in the new command window

reg delete HKLM\SYSTEM\CurrentControlSet\Enum /f

... Profit!!!

I tried that on my Win10 install, and it actually survived
on a reboot. The purpose of that, is to make Win10 discover
all the hardware over again. That's a trick from the
Win2K/WinXP era. I hope it's still doing what it's
supposed to do.

So start by doing a Properties on the folder and files
first. You don't really need to know anything about
the stuff above, but it doesn't hurt to be curious
about how stuff might work.

Paul
  #6  
Old February 7th 18, 03:56 PM posted to alt.windows7.general
John B. Smith
external usenet poster
 
Posts: 47
Default My ReadOnly Problem

On Tue, 06 Feb 2018 21:11:58 -0500, Paul
wrote:

John B. Smith wrote:
When I added Win7 to my XP install a year or so ago, I installed
Eudora7 on it. It’s pretty old and doesn’t work great but I still
like it and have ton of mailboxes in it and I’m FAMILIAR with it,
which is important to me. I just assured myself Win7 Eudora install
would work in Win7 (did not attempt to bring over all my mailboxes)
then did all email in XP where everything works.

Recently I had a reason to want to actually use Eudora in Win7 so I
attempted to xfer mailboxes over from XP. I had all mailboxes in a
folder I'd named mydata and Eudora install instructions said to
reference that folder during install. So I uninstalled/ reinstalled
Eudora and tried to do that. Alas, when I tried to run Eudora it said
it could not write to Eudora.log, it might be write protected. Right
clicking the mydata folder, Properties, it sure nuff was ReadOnly. But
there was a ReadOnly box that when clicked went clear and when I
Applied it, it looked like everything in mydata folder was having the
ReadOnly attribute removed. Eudora still wouldn’t run and when I
looked at mydata folder again it had turned back to ReadOnly. In fact
if you check it immediately after removing the attribute with
rightclick Properties you can see that it never changed. The mydata
folder resides in Win7 C:\mydata. What did I do wrong? Why can’t I
bring over the folder from XP without it becoming ReadOnly?


The ReadOnly flag on a folder is not a ReadOnly flag.

It is "overloaded" by Microsoft, as an indicator that
folder customization is present. It is not intended to
control access to folders. When folder customization is
present, File Explorer can go looking in desktop.ini
for information about just what customization is desired.
You may see a line with "shell32.dll" and a number, and
the number indicates the "view" type to use.

Instead, in NTFS, folders and files have security
settings you can see by doing properties on the items.
Changing who owns the files, from a "mysterious" SID that
Windows 7 doesn't have an entry for in its table, to
your Windows 7 account name SID, may make the contents
usable in Windows 7.

Even when two OSes have an account "Paul" with password "12345678",
they're not the same person. Each account has a long string
of digits. Three clusters of random digits, plus an account
number on the end. Perhaps I'm 1111111111-2222222222-3333333333-1000
on WinXP and on Windows 7 I'm 4444444444-5555555555-6666666666-1001.
So when I mechanically move an NTFS folder from one OS C: to
another OS C:, the owners are in fact quite different. It pays
then, to verify who owns the contents of the folder and
take ownership. You can do this from the Properties of
a file or folder.


That's interesting as my next question, after we've solved this little
problem was why my transfer of XP Firefox Profile to Win7 Firefox
Profile (Firefox Help put me onto how to copy it over but they may not
be thinking I want to do it between 2 OS's) After the Profle folder
was copied in (had to relearn how to do this simple task in Win7 cause
Microsoft firgures it must be complicated and arcane to demonstrate
you really do have a new, different and oh so much better OS) Win7
Firefox came up with all the tons of Bookmarks that XP Firefox has
been toting for years. I was encouraged, it worked!, until I tried to
use the download passwords for various sites. The download screen
comes up with my correct user name and the 'remembered' password all
filled in as usual. Unfortunately the site still doesn't recognize me,
or maybe the password, and won't allow me to download.


User accounts start at 1000. Administrator should be 500. The
groups of digits are randomly assigned during OS installation,
with the intention that no two OSes have exactly the same SID strings.
It's not a GUID, but it's damn close to it in terms of collision
potential.

When you're in a domain (something I might have used at work), there's
a better chance of some consistency seen when you "roam". However,
if you parachute folders from one OS to another in your non-domain
home setup, you should occasionally check to see who owns them.

For example, say I have a well-beaten folder, that's "been everywhere"
in my computer room. I check the permissions and I see.

Owner 1111111111-2222222222-3333333333-1000
Owner 4444444444-5555555555-6666666666-1001
Owner 7777777777-8888888888-9999999999-1000
Owner Paul === the "real" Paul

That would mean that the SID for Paul, the numeric quantity,
the OS could look that up and see that the symbolic name of
the owner is Paul. Whereas for the other three stamps, those
were applied while three other OSes were booted and I was doing
stuff to the folder. Perhaps I needed administrator permissions
to thwart the ownership and move the folder around. And now
there is multiple ownership.

That doesn't hurt anything.

And the only reason for ever mentioning this, is to
have you look in Properties of a folder or file,
to see what kind of a mess is in there. There might
actually be an explanation for "why I can't write that".
Maybe you're not actually an owner. And the numeric
SIDs sitting there, the ones the OS doesn't recognize,
aren't your friends and they're not going to help you.
It's the one with familiar names like Paul, Administrator,
System, that matter more.

You can obviously override things as Administrator or
using the SYSTEM account, but that's just making a mess
for no reason.

And if you use TakeOwn, even that may not have the
desired effect. I don't have this loaded in all my OSes,
mainly because the results have been mixed. *Do Not*
apply that to the top level of C: . You may apply it
to a data-only partition if you want, but even that
is likely to be dangerous. This tool is intended for
exactly the situation you're in - a single folder
that is slightly borked on permissions.

https://www.sevenforums.com/tutorial...-shortcut.html

*******

You can "save" the permissions on a partition with this.

icacls c:\ /save "%userprofile%\Downloads\ntfsCdrive.txt" /t /c

Once you've got the file, you change the (blank!) top line to

.

a single period, which means "current working directory".
That modification to the file is necessary if restoring
the permissions to an entire partition. Like this.

cd /d c:

icacls c:\ /restore %userprofile%\Downloads\ntfsCdrive.txt

Normally, to restore permissions, you must be one level
*above* the object you're restoring. The hack to change
the first line of the file to a period, is intended to
correct that situation and let you do it anyway. As otherwise,
you can't be "one level above C:" as there is no such thing.

I found mention of that issue, here, near the end of the thread.

https://social.technet.microsoft.com...backup-restore

You can play back permissions, to correct them. Things
like Junction Points, icacls won't descend them, but that's
OK because the area you would descend to, gets covered anyway
by other lines in the file.

That's how professionals work on a partition, without
leaving footprints all over the place. The people in these
groups, aren't that careful, and so when someone has
been messing around with their registry or file system,
a forensics person can discover the permissions have been
altered, and figure out what they've been doing. The tools
that allow playback of permissions are there, so everything
is neat and tidy when you're finished :-)

If you want to discover what the SIDs are on the current OS,
you can try:

wmic useraccount get name,sid

The "whoami" command is also good when you're working
in a Command Prompt that you want to verify what credentials
you're using when you go to run a command. You can do more
damage with the SYSTEM account, than any other account
on the computer :-) For example, using pstools.zip from
sysinternals.com, you can become SYSTEM.

psexec64 -msi cmd.exe

... in the new command window

reg delete HKLM\SYSTEM\CurrentControlSet\Enum /f

... Profit!!!

I tried that on my Win10 install, and it actually survived
on a reboot. The purpose of that, is to make Win10 discover
all the hardware over again. That's a trick from the
Win2K/WinXP era. I hope it's still doing what it's
supposed to do.

So start by doing a Properties on the folder and files
first. You don't really need to know anything about
the stuff above, but it doesn't hurt to be curious
about how stuff might work.

Paul


You guys have been helpful, as usual, but I think I'll first try to
copy that folder over to Win7 from within Win7 and see if that'll cure
it. I had done the copy while in XP before. I think I'll place it in
the x86 folder this time rather that C: root.

Yes Char, that Eudora.log does exist in the mydata folder. I haven't
looked at individual files yet though. Of course I'm typing this in XP
where I still do most of my stuff.
  #7  
Old February 7th 18, 09:11 PM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default My ReadOnly Problem

John B. Smith wrote:


That's interesting as my next question, after we've solved this little
problem was why my transfer of XP Firefox Profile to Win7 Firefox
Profile (Firefox Help put me onto how to copy it over but they may not
be thinking I want to do it between 2 OS's) After the Profle folder
was copied in (had to relearn how to do this simple task in Win7 cause
Microsoft firgures it must be complicated and arcane to demonstrate
you really do have a new, different and oh so much better OS) Win7
Firefox came up with all the tons of Bookmarks that XP Firefox has
been toting for years. I was encouraged, it worked!, until I tried to
use the download passwords for various sites. The download screen
comes up with my correct user name and the 'remembered' password all
filled in as usual. Unfortunately the site still doesn't recognize me,
or maybe the password, and won't allow me to download.


"Migrate site and master passwords and logins from Firefox to Light"

https://support.mozilla.org/en-US/questions/1011196

"key3.db and cert8.db"
"Firefox 30 created key4.db and cert9.db"

I wonder if the machine-to-machine transfer would work
better if you use the same version on both platforms,
moved and tested the passwords, then updated FF
on the target platform to the desired version ?
You can get any version of Firefox you want.
[This is to illustrate the layout of the server...]

http://releases.mozilla.org/pub/fire.../en-US/Firefox Setup 46.0.exe

I'm guessing that perhaps the two versions involved,
don't use the same containers or something.

*******

https://support.mozilla.org/en-US/kb...ores-user-data

Your passwords are stored in the key3.db, key4.db, and logins.json files.
For more information, see "Password Manager - Remember, delete, change
and import saved passwords in Firefox".

[However, this article doesn't really help with migration as such...]

https://support.mozilla.org/en-US/kb...nge-and-import

Paul

  #8  
Old February 10th 18, 05:33 PM posted to alt.windows7.general
John B. Smith
external usenet poster
 
Posts: 47
Default My ReadOnly Problem

On Wed, 07 Feb 2018 15:11:01 -0500, Paul
wrote:

John B. Smith wrote:


That's interesting as my next question, after we've solved this little
problem was why my transfer of XP Firefox Profile to Win7 Firefox
Profile (Firefox Help put me onto how to copy it over but they may not
be thinking I want to do it between 2 OS's) After the Profle folder
was copied in (had to relearn how to do this simple task in Win7 cause
Microsoft firgures it must be complicated and arcane to demonstrate
you really do have a new, different and oh so much better OS) Win7
Firefox came up with all the tons of Bookmarks that XP Firefox has
been toting for years. I was encouraged, it worked!, until I tried to
use the download passwords for various sites. The download screen
comes up with my correct user name and the 'remembered' password all
filled in as usual. Unfortunately the site still doesn't recognize me,
or maybe the password, and won't allow me to download.


"Migrate site and master passwords and logins from Firefox to Light"

https://support.mozilla.org/en-US/questions/1011196

"key3.db and cert8.db"
"Firefox 30 created key4.db and cert9.db"

I wonder if the machine-to-machine transfer would work
better if you use the same version on both platforms,
moved and tested the passwords, then updated FF
on the target platform to the desired version ?
You can get any version of Firefox you want.
[This is to illustrate the layout of the server...]

http://releases.mozilla.org/pub/fire.../en-US/Firefox Setup 46.0.exe

I'm guessing that perhaps the two versions involved,
don't use the same containers or something.

*******

https://support.mozilla.org/en-US/kb...ores-user-data

Your passwords are stored in the key3.db, key4.db, and logins.json files.
For more information, see "Password Manager - Remember, delete, change
and import saved passwords in Firefox".

[However, this article doesn't really help with migration as such...]

https://support.mozilla.org/en-US/kb...nge-and-import

Paul


Finally got my Eudora to work in Win7 using my idea of copying the
data file folder mydata over from XP from within (booted up in) Win7.
However I did a bunch of stumbling around with various malfunctions
till I finally figured out you have to REBOOT Win7 after a de-install
before any more experimenting. Eudora seems to be working in Win7 now.
I did try installing Thunderbird during the depths of my desperation.
Thunderbird is only able to import the top layer of Eudora mailboxes.
That is where my 'people' are. The three folders under them (where the
businesses are, it completely ignored. Goes to show why people are
still trying to use Eudora even though the company went out of
business.

Regarding Firefox, my XP Firefox is 52.60 (32 bit) and Win7 Firefox is
58.0.2 (64 bit) so overlaying Profiles is probably hopeless. I did get
my BookMarks xferred though and that's the main thing i wanted.

Thanks for the help guys.
  #9  
Old February 12th 18, 07:28 AM posted to alt.windows7.general
tesla sTinker
external usenet poster
 
Posts: 134
Default My ReadOnly Problem

that's not the way your suppose to install it.
Besides Eudora 7 is a piece of ****.
OSE, which is much older, is much much better.
even permitting the operator header editing. Lets see you do that with
Eudora 7. You cant.

Your making a mess of your manifest in your log files.
You need to remove the thing with an uninstall, then run a
registry editor. Let it clean up the machine. Then reinstall what
you want the right way.

On 2/7/2018 6:56 AM, John B. Smith scribbled:
On Tue, 06 Feb 2018 21:11:58 -0500,
wrote:

John B. Smith wrote:
When I added Win7 to my XP install a year or so ago, I installed
Eudora7 on it. It’s pretty old and doesn’t work great but I still
like it and have ton of mailboxes in it and I’m FAMILIAR with it,
which is important to me. I just assured myself Win7 Eudora install
would work in Win7 (did not attempt to bring over all my mailboxes)
then did all email in XP where everything works.

Recently I had a reason to want to actually use Eudora in Win7 so I
attempted to xfer mailboxes over from XP. I had all mailboxes in a
folder I'd named mydata and Eudora install instructions said to
reference that folder during install. So I uninstalled/ reinstalled
Eudora and tried to do that. Alas, when I tried to run Eudora it said
it could not write to Eudora.log, it might be write protected. Right
clicking the mydata folder, Properties, it sure nuff was ReadOnly. But
there was a ReadOnly box that when clicked went clear and when I
Applied it, it looked like everything in mydata folder was having the
ReadOnly attribute removed. Eudora still wouldn’t run and when I
looked at mydata folder again it had turned back to ReadOnly. In fact
if you check it immediately after removing the attribute with
rightclick Properties you can see that it never changed. The mydata
folder resides in Win7 C:\mydata. What did I do wrong? Why can’t I
bring over the folder from XP without it becoming ReadOnly?


The ReadOnly flag on a folder is not a ReadOnly flag.

It is "overloaded" by Microsoft, as an indicator that
folder customization is present. It is not intended to
control access to folders. When folder customization is
present, File Explorer can go looking in desktop.ini
for information about just what customization is desired.
You may see a line with "shell32.dll" and a number, and
the number indicates the "view" type to use.

Instead, in NTFS, folders and files have security
settings you can see by doing properties on the items.
Changing who owns the files, from a "mysterious" SID that
Windows 7 doesn't have an entry for in its table, to
your Windows 7 account name SID, may make the contents
usable in Windows 7.

Even when two OSes have an account "Paul" with password "12345678",
they're not the same person. Each account has a long string
of digits. Three clusters of random digits, plus an account
number on the end. Perhaps I'm 1111111111-2222222222-3333333333-1000
on WinXP and on Windows 7 I'm 4444444444-5555555555-6666666666-1001.
So when I mechanically move an NTFS folder from one OS C: to
another OS C:, the owners are in fact quite different. It pays
then, to verify who owns the contents of the folder and
take ownership. You can do this from the Properties of
a file or folder.


That's interesting as my next question, after we've solved this little
problem was why my transfer of XP Firefox Profile to Win7 Firefox
Profile (Firefox Help put me onto how to copy it over but they may not
be thinking I want to do it between 2 OS's) After the Profle folder
was copied in (had to relearn how to do this simple task in Win7 cause
Microsoft firgures it must be complicated and arcane to demonstrate
you really do have a new, different and oh so much better OS) Win7
Firefox came up with all the tons of Bookmarks that XP Firefox has
been toting for years. I was encouraged, it worked!, until I tried to
use the download passwords for various sites. The download screen
comes up with my correct user name and the 'remembered' password all
filled in as usual. Unfortunately the site still doesn't recognize me,
or maybe the password, and won't allow me to download.


User accounts start at 1000. Administrator should be 500. The
groups of digits are randomly assigned during OS installation,
with the intention that no two OSes have exactly the same SID strings.
It's not a GUID, but it's damn close to it in terms of collision
potential.

When you're in a domain (something I might have used at work), there's
a better chance of some consistency seen when you "roam". However,
if you parachute folders from one OS to another in your non-domain
home setup, you should occasionally check to see who owns them.

For example, say I have a well-beaten folder, that's "been everywhere"
in my computer room. I check the permissions and I see.

Owner 1111111111-2222222222-3333333333-1000
Owner 4444444444-5555555555-6666666666-1001
Owner 7777777777-8888888888-9999999999-1000
Owner Paul=== the "real" Paul

That would mean that the SID for Paul, the numeric quantity,
the OS could look that up and see that the symbolic name of
the owner is Paul. Whereas for the other three stamps, those
were applied while three other OSes were booted and I was doing
stuff to the folder. Perhaps I needed administrator permissions
to thwart the ownership and move the folder around. And now
there is multiple ownership.

That doesn't hurt anything.

And the only reason for ever mentioning this, is to
have you look in Properties of a folder or file,
to see what kind of a mess is in there. There might
actually be an explanation for "why I can't write that".
Maybe you're not actually an owner. And the numeric
SIDs sitting there, the ones the OS doesn't recognize,
aren't your friends and they're not going to help you.
It's the one with familiar names like Paul, Administrator,
System, that matter more.

You can obviously override things as Administrator or
using the SYSTEM account, but that's just making a mess
for no reason.

And if you use TakeOwn, even that may not have the
desired effect. I don't have this loaded in all my OSes,
mainly because the results have been mixed. *Do Not*
apply that to the top level of C: . You may apply it
to a data-only partition if you want, but even that
is likely to be dangerous. This tool is intended for
exactly the situation you're in - a single folder
that is slightly borked on permissions.

https://www.sevenforums.com/tutorial...-shortcut.html

*******

You can "save" the permissions on a partition with this.

icacls c:\ /save "%userprofile%\Downloads\ntfsCdrive.txt" /t /c

Once you've got the file, you change the (blank!) top line to

.

a single period, which means "current working directory".
That modification to the file is necessary if restoring
the permissions to an entire partition. Like this.

cd /d c:

icacls c:\ /restore %userprofile%\Downloads\ntfsCdrive.txt

Normally, to restore permissions, you must be one level
*above* the object you're restoring. The hack to change
the first line of the file to a period, is intended to
correct that situation and let you do it anyway. As otherwise,
you can't be "one level above C:" as there is no such thing.

I found mention of that issue, here, near the end of the thread.

https://social.technet.microsoft.com...backup-restore

You can play back permissions, to correct them. Things
like Junction Points, icacls won't descend them, but that's
OK because the area you would descend to, gets covered anyway
by other lines in the file.

That's how professionals work on a partition, without
leaving footprints all over the place. The people in these
groups, aren't that careful, and so when someone has
been messing around with their registry or file system,
a forensics person can discover the permissions have been
altered, and figure out what they've been doing. The tools
that allow playback of permissions are there, so everything
is neat and tidy when you're finished :-)

If you want to discover what the SIDs are on the current OS,
you can try:

wmic useraccount get name,sid

The "whoami" command is also good when you're working
in a Command Prompt that you want to verify what credentials
you're using when you go to run a command. You can do more
damage with the SYSTEM account, than any other account
on the computer :-) For example, using pstools.zip from
sysinternals.com, you can become SYSTEM.

psexec64 -msi cmd.exe

... in the new command window

reg delete HKLM\SYSTEM\CurrentControlSet\Enum /f

... Profit!!!

I tried that on my Win10 install, and it actually survived
on a reboot. The purpose of that, is to make Win10 discover
all the hardware over again. That's a trick from the
Win2K/WinXP era. I hope it's still doing what it's
supposed to do.

So start by doing a Properties on the folder and files
first. You don't really need to know anything about
the stuff above, but it doesn't hurt to be curious
about how stuff might work.

Paul


You guys have been helpful, as usual, but I think I'll first try to
copy that folder over to Win7 from within Win7 and see if that'll cure
it. I had done the copy while in XP before. I think I'll place it in
the x86 folder this time rather that C: root.

Yes Char, that Eudora.log does exist in the mydata folder. I haven't
looked at individual files yet though. Of course I'm typing this in XP
where I still do most of my stuff.

  #10  
Old February 12th 18, 01:22 PM posted to alt.windows7.general
John B. Smith
external usenet poster
 
Posts: 47
Default My ReadOnly Problem

On Sun, 11 Feb 2018 22:28:31 -0800, tesla sTinker
wrote:

that's not the way your suppose to install it.
Besides Eudora 7 is a piece of ****.

Indeed, nowadays, cause it's way out of date. Only email client that
allows me to organize my mailboxes that I've found though.

OSE, which is much older, is much much better.
even permitting the operator header editing. Lets see you do that with
Eudora 7. You cant.

My Google Search comes up with Microsoft OSE or president of hell.
Unhelpful.


Your making a mess of your manifest in your log files.
You need to remove the thing with an uninstall, then run a
registry editor. Let it clean up the machine.


Auto Registry clean-ups scare the crap out of me. Not with a ten foot
pole.

Then reinstall what
you want the right way.

 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 06:19 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.