Welcome, Guest. Please login or register.

Author Topic: Bizarre OS3.9 problem with Ed  (Read 1418 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline golemTopic starter

  • Sr. Member
  • ****
  • Join Date: May 2002
  • Posts: 432
    • Show only replies by golem
Bizarre OS3.9 problem with Ed
« on: July 04, 2010, 03:50:50 PM »
I have had this problem with two installs now I think;
When you Ed a file it sets the protection bits on that file to just read. Therefore when you come to save it it can't and you have to change the bits to rwed again. Very annoying and I can't for the life of me figure out why. I've checked the protection bits on the Ed executable itself and it is prwed. Ed-startup in S: is rwed.
Why oh why?...anybody had the same?
                                                             
A1200 desktop, Blizzard 1260, OS3.9BB2, Indivision Mk II, SCSI Jaz, Ethernet
A1200 desktop, Blizzard 1230, OS3.1, Ethernet
A500, OS1.3
 

Offline Matt_H

Re: Bizarre OS3.9 problem with Ed
« Reply #1 on: July 04, 2010, 05:55:40 PM »
What filesystem are you using?

Try renaming/deleting/moving ed-startup.
 

Offline golemTopic starter

  • Sr. Member
  • ****
  • Join Date: May 2002
  • Posts: 432
    • Show only replies by golem
Re: Bizarre OS3.9 problem with Ed
« Reply #2 on: July 04, 2010, 06:31:42 PM »
Filesystem is 45.13 (3.8.2001). Tried it without an Ed-startup. Same. Ed version is 37.11 which is what comes with the CD I think. Tried same version of Ed on my WinUAE install which is vanilla OS3.9 and not a copy of my main system and it works fine. Strange. Whoever said computers are logical )
                                                             
A1200 desktop, Blizzard 1260, OS3.9BB2, Indivision Mk II, SCSI Jaz, Ethernet
A1200 desktop, Blizzard 1230, OS3.1, Ethernet
A500, OS1.3
 

Offline CSixx

  • Sr. Member
  • ****
  • Join Date: Jan 2006
  • Posts: 315
    • Show only replies by CSixx
Re: Bizarre OS3.9 problem with Ed
« Reply #3 on: July 04, 2010, 08:49:17 PM »
I had the same problem when I was using one of the pre-packaged wb setups. I dont remember exactly which package I used, ClassicWB maybe...

Either way, I reinstalled bare 3.9 and the issue went away. I believe it's due to some 3rd party program but never figured out which one.