06 January 2019, 17:03 | #1 |
Registered User
Join Date: Jan 2014
Location: Cambs / UK
Posts: 356
|
Cannot save startup-sequence
For some reason all of a sudden I cannot save my startup-sequence. The permissions are writable. If I copy the file to say startup-sequence1 using NOPRO I can then edit the new file. I then have to force delete the original file and copy startup-sequence1 to startup-sequence.
This gets me one edit, the next time I try to edit the startup sequence I cannot save it again. Anyone any ideas? It is driving me crazy. I have a feeling maybe my CF card is getting to the end of it's life. |
06 January 2019, 17:06 | #2 |
Coder/webmaster/gamer
Join Date: Oct 2001
Location: Canberra/Australia
Posts: 2,640
|
I was going to suggest that some program had a lock on the file. But if you can still delete it with DELETE s:startup-sequence FORCE, as apparently you can in this case, the issue must be something else.
|
06 January 2019, 17:12 | #3 |
Registered User
Join Date: Jan 2014
Location: Cambs / UK
Posts: 356
|
Well I just tried a cold boot without without startup-sequence and I still could not save the file using ed. That was a good idea Minuous I thought is was going to work.
|
06 January 2019, 17:27 | #4 |
Coder/webmaster/gamer
Join Date: Oct 2001
Location: Canberra/Australia
Posts: 2,640
|
I realized a minute or two later that the cause must be something else and edited my first post accordingly :-(
|
06 January 2019, 17:32 | #5 |
Registered User
Join Date: Jan 2014
Location: Cambs / UK
Posts: 356
|
Ah, yes. I can delete it with FORCE.
Just tried some other files in S: I can edit them all once, but cannot change any of them a second time unless I go through the procedure above. |
06 January 2019, 20:17 | #6 |
Registered User
Join Date: Aug 2014
Location: Brindisi (Italy)
Age: 70
Posts: 8,252
|
It could be a file system corruption, try to create a new "S" folder and try to create new files, after saving a few seconds and then double check the file.
|
06 January 2019, 20:47 | #7 |
Registered User
Join Date: Jan 2014
Location: Cambs / UK
Posts: 356
|
Well now I am confused. I copied a file to another physical disk in my system and still have the same problem!!
|
06 January 2019, 20:50 | #8 |
Registered User
Join Date: Jan 2014
Location: Cambs / UK
Posts: 356
|
Same even happens if I copy to Ram disk!! I can edit the file once and then never again.
|
06 January 2019, 21:08 | #9 |
Ex nihilo nihil
Join Date: Oct 2017
Location: CH
Posts: 4,884
|
Virus ?
(I have never heard about such behaviour for a virus but did you check ?) |
06 January 2019, 21:10 | #10 |
Registered User
Join Date: Jan 2014
Location: Cambs / UK
Posts: 356
|
Well that may well be my next check.
I have just ran PFSDoctor (PFS file system check) on my drives all comes up fine. Next I just cold booted from a Workbench 3.1 floppy disk (write protected so hopefully virus free) and still cant edit my startup-sequence on the hard drive! |
06 January 2019, 21:22 | #11 |
Registered User
Join Date: Aug 2014
Location: Brindisi (Italy)
Age: 70
Posts: 8,252
|
Can you attach the two files before and after saving it?
I suspect that the files after the first save have some corruption! Last edited by AMIGASYSTEM; 06 January 2019 at 21:29. |
06 January 2019, 22:18 | #12 |
Registered User
Join Date: Jan 2014
Location: Cambs / UK
Posts: 356
|
I really don't know what is going on!
I copied my startup-sequence to ram: Instead of suing Amiga ED, I used vim to edit the file instead. All went well. Edited multiple times in Vim and all was ok. So opened it up in ED and edited it multiple times!!! What the hell? So copied the file from ram back to S: No everything is fine. Just need to do the others I have edited like s:network-startup I have no idea what happened?? |
06 January 2019, 22:20 | #13 |
Ex nihilo nihil
Join Date: Oct 2017
Location: CH
Posts: 4,884
|
I did a quick try with Snoopdos to see what is happening while saving with ED (to be able to compare with what is happening on your side (if you have Snoopdos installed))..
Unfortunately under OS 1.3 Snoopdos report no line at all when saving (only ED call is visible, not the saving of the file, nor when quitting ED). Will check if under 3.1 something get reported by Snoopdos when saving. |
06 January 2019, 22:23 | #14 |
Registered User
Join Date: Aug 2014
Location: Brindisi (Italy)
Age: 70
Posts: 8,252
|
You should attach the two files I'm sure there are differences
|
06 January 2019, 22:25 | #15 |
Ex nihilo nihil
Join Date: Oct 2017
Location: CH
Posts: 4,884
|
By the way, did you try to rename your ED-Startup file if you have one ?
(I know you booted from floppy also, but worth a check ?) |
06 January 2019, 22:34 | #16 |
Registered User
Join Date: Jan 2014
Location: Cambs / UK
Posts: 356
|
I will try snoopdos now.
I have just replaced ed with the one from the OS3.9 cd rom and still no better. Also editpad cannot save the changes either! Only vim can! |
06 January 2019, 22:35 | #17 |
Registered User
Join Date: Jan 2014
Location: Cambs / UK
Posts: 356
|
|
06 January 2019, 22:38 | #18 |
Ex nihilo nihil
Join Date: Oct 2017
Location: CH
Posts: 4,884
|
In S:
Did you know that this "S" name is the abbreviation for Script ? |
06 January 2019, 22:47 | #19 |
Registered User
Join Date: Jan 2014
Location: Cambs / UK
Posts: 356
|
@AMIGASYSTEM - The two files are in the zone.
@malko - I did know S: was for script - Yes I do have a ED-Startup file. |
06 January 2019, 22:55 | #20 |
Registered User
Join Date: Jan 2014
Location: Cambs / UK
Posts: 356
|
Okay there is a SnoopDos.log in the zone. There is definitely something strange going on. It keeps referencing a file called :t/ed-backup. Should that not be t:ed-backup ??
Code:
SnoopDos logging started on Friday, 11-Nov-11 at 12:44:55 Count Process Name Action Target Name Options Res. ----- ------------ ------ ----------- ------- ---- 44 [5] ed Open RAW:0/0/639/199/Ed 2.00/CLO Write OK 45 [5] ed Open S:Ed-Startup Read OK 46 [5] ed Open S:startup-sequence Read OK 47 [5] ed Delete :t/ed-backup Fail 48 [5] ed Rename S:startup-sequence 49 [5] ed to --> :t/ed-backup Fail 50 [5] ed Open S:startup-sequence Write Fail Closed SnoopDos log at 12:45:15 Last edited by gazj82; 06 January 2019 at 23:11. |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
3.9 Startup Sequence | dannyp1 | Amiga scene | 2 | 04 January 2016 20:56 |
ed s:startup-sequence | Astrofra | Member Introductions | 2 | 24 February 2013 22:09 |
startup-sequence | mai | support.Other | 10 | 01 June 2010 21:39 |
Startup-Sequence | blade002 | support.Apps | 8 | 04 April 2008 19:06 |
Need help with startup-sequence | lopos2000 | support.Apps | 5 | 01 August 2005 11:54 |
|
|