Welcome, Guest. Please login or register.

Author Topic: Editing the startup sequence in WB 1.3  (Read 880 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline AmigaFreakTopic starter

  • Sr. Member
  • ****
  • Join Date: Apr 2004
  • Posts: 291
    • Show only replies by AmigaFreak
Editing the startup sequence in WB 1.3
« on: March 26, 2005, 05:19:29 PM »
Hey guys need some help

I remember a time when I was younger where i had the startup sequence of my WB 1.3 disk make the OS go into the ram so you could take out the disk reboot it, and the OS would load automatically. BUT I lost the book that tells you how to do it... its a small book that says AMIGA DOS for A500/A2000 does anyone know the script for doing that?
-- Joshua E. Horn

"Um... I think my computer let out the blue smoke! What should I do?!?!?"
 

Offline bloodline

  • Master Sock Abuser
  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 12113
    • Show only replies by bloodline
    • http://www.troubled-mind.com
Re: Editing the startup sequence in WB 1.3
« Reply #1 on: March 26, 2005, 05:29:28 PM »
I think you are talking about stting up a RAD:

Offline Generale

  • Full Member
  • ***
  • Join Date: Feb 2005
  • Posts: 233
    • Show only replies by Generale
    • http://members.dodo.com.au/~izabellion
Re: Editing the startup sequence in WB 1.3
« Reply #2 on: March 26, 2005, 06:41:07 PM »
Sounds like the one. Its already there in the default mountlist for wb1.3
I think I saw that amiga dos book on aussie ebay yesterday. not sure though.

Wouldnt it be a matter of mounting rad/ramb0, and dumping across files? Then assigning the core directories to ramb0: and a path reset I think?
A500 (salvo): 1Mb RAM (512k chip, 512k SlowFast)
1x880k Floppy Disk, 1xIBM 540Mb 3.5\\"HDD KS1.3, WB1.3
1084S monitor. AT Keyboard!
A500 (Whitey): 512k RAM, 1x880k Floppy Disk, KS1.2, WB1.3
 

Offline bloodline

  • Master Sock Abuser
  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 12113
    • Show only replies by bloodline
    • http://www.troubled-mind.com
Re: Editing the startup sequence in WB 1.3
« Reply #3 on: March 26, 2005, 07:16:50 PM »
yeah:
Mount RAD:
Copy df0: RAD:

:-D

Offline AmigaFreakTopic starter

  • Sr. Member
  • ****
  • Join Date: Apr 2004
  • Posts: 291
    • Show only replies by AmigaFreak
Re: Editing the startup sequence in WB 1.3
« Reply #4 on: March 26, 2005, 09:41:25 PM »
How do I implemnt that.. I dont even remember how to get into the start up editor without the book. and I remember it being alot more complicated.. well atleast a longer process.
-- Joshua E. Horn

"Um... I think my computer let out the blue smoke! What should I do?!?!?"
 

Offline Merc

  • Sr. Member
  • ****
  • Join Date: Apr 2002
  • Posts: 312
    • Show only replies by Merc
    • http://chebucto.ns.ca/~ah210/Profile.html
Re: Editing the startup sequence in WB 1.3
« Reply #5 on: March 26, 2005, 10:57:01 PM »
Quote

AmigaFreak wrote:
Hey guys need some help

I remember a time when I was younger where i had the startup sequence of my WB 1.3 disk make the OS go into the ram so you could take out the disk reboot it, and the OS would load automatically.


Ok, this is from memory, but I think you first have to edit the entry for the RAD: drive so that it has 79 cylinders.
Then when you mount it, it will be the same size as a regular floppy, AND you can use diskcopy to quickly copy your WB disk to it.  If you add a "bootpri=6" line to the RAD: entry then it will always override any bootable floppies you might have inserted.

You can edit the startup-sequence in the s directory (and the mountlist in devs) with the "ed" editor, for the startup-sequence you probably just need to add at the beginning:

if not exists rad:s/startup-sequence
then
  mount rad:
  diskcopy from df0: to rad: noverify
  rad:c/assign c: rad:c
  assign sys: rad:
  assign s: sys:s
  assign l: sys:l
  assign devs: sys:devs
  assign libs: sys:libs
  execute s:startup-sequence
endif

...  and I *think* you'll be in business..  it's been a while since I wrote an AmigaDOS script so I may have a few things wrong :)
 

Offline Merc

  • Sr. Member
  • ****
  • Join Date: Apr 2002
  • Posts: 312
    • Show only replies by Merc
    • http://chebucto.ns.ca/~ah210/Profile.html
Re: Editing the startup sequence in WB 1.3
« Reply #6 on: March 27, 2005, 04:09:25 AM »
Ok, I got curious and tried it in UAE, and had to make a few tweaks  :-D

failat 11
mount > nil: rad:
if not exists rad:s/startup-sequence
sys:system/diskcopy from df0: to rad: noverify
rad:c/assign c: rad:c
assign sys: rad:
assign s: sys:s
assign l: sys:l
assign devs: sys:devs
assign libs: sys:libs
cd rad:
execute rad:s/startup-sequence
endif

--

Only problem is it stops to ask you to press enter before the diskcopy starts.
 

Offline red_orion

  • Newbie
  • *
  • Join Date: Mar 2005
  • Posts: 28
    • Show only replies by red_orion
Re: Editing the startup sequence in WB 1.3
« Reply #7 on: March 27, 2005, 07:32:42 AM »
I use to do the same thing on my A500. I'll look and see if I can find my old Workbench disk that has that startup-sequence.
 

Offline davide405

  • Newbie
  • *
  • Join Date: Feb 2005
  • Posts: 27
    • Show only replies by davide405
Re: Editing the startup sequence in WB 1.3
« Reply #8 on: March 27, 2005, 08:04:27 AM »
This much I do remember:

Editing the startup sequence was fairly painless.  Any word processing program (i.e. Kindwords) that could save as an ASCII file would do the trick.
 

Offline blobrana

  • Hero Member
  • *****
  • Join Date: Mar 2002
  • Posts: 4743
    • Show only replies by blobrana
    • http://mysite.wanadoo-members.co.uk/blobrana/home.html
Re: Editing the startup sequence in WB 1.3
« Reply #9 on: March 27, 2005, 11:43:37 AM »
@Merc

LOL!
Thats superb.

@AmigaFreak

yeah i remember, (before i got a Hard Drive), that i used to just copy the libs: and c: drawer (or any weird font etc) into memory just to speed up floppy operation.

copy dfo:libs Ram:
copy DF0:c Ram: or copy DF0:c Ram:c

And entering the path into the `add path` bit

Or use the `resident` command that`ll keep the c: stuff in menory (only pure files can be made resident, though).


Path >NIL: RAM: Rad: Mad: ram:c SYS:Utilities etc

but i suppose thats its better to use the ASSIGN C:  RAM:C and copy the c: drawer into a tidy drawer in the ram disk and like wise for the libs:,,, that`ll keeps all the files from getting mixed up... ;)


---------------------------------
Disclaimer: loss of data using Ram & rebooting is not my fault, i would urge using Rad: where ever possibe ;)