bpendlet@esunix.UUCP (02/06/87)
[]
I starting to get serious about doing some development on my Amiga. I've had
it for almost a year and my two year old had used it more than I have. I
must admit that I have been amazed by how much fun a young child can have
just dragging the kermit icon around the screen.
My question is this; How much of the stuff on the workbench disk can be
junked? I want to build a workbench disk that has emacs, a compiler (TDI
Modula-2), and the TDI and Amiga libraries needed to compile and link a
program. The idea, obviously, is to have the tools in one drive and the
sources for my current project in the other on my two drive system.
I know I can junk the device drivers for printers I don't have. But what
about fonts? Can I dump all the fonts? Or, must I keep at least one. What
about the system commands? Most of the system commands look like they can be
dumped, I can always load a different disk if I need something other than
cd, dir, or delete, right? How wrong am I and what have I missed?
Happy Hacking
Bob Pendleton
--
---
Bob Pendleton
Evans & Sutherland Computer Corporation
UUCP Address: {decvax,ucbvax,ihnp4,allegra}!decwrl!esunix!bpendlet
Alternate: {ihnp4,seismo}!utah-cs!utah-gr!uplherc!esunix!bpendlet
hacking code, hacking code.
sometimes happy, sometimes bored,
almost lost in a pile of spode.
tell the people "I'm only hacking code."
---
I am solely responsible for what I say.
---dillon@CORY.BERKELEY.EDU.UUCP (02/09/87)
I've found the best thing to do is to have a 'compile' disk and a 'source' disk, neither being the workbench. With two drives, you boot the machine with your workbench, then replace it with your compile disk and re-assign C: (via some automatic script, of course). Your source disk is in the other drive. Thus, you can devote your entire source disk to.. well, source. -Matt
higgin@cbmvax.UUCP (02/09/87)
In article <352@esunix.UUCP> bpendlet@esunix.UUCP (Bob Pendleton) writes:
$[]
$...about desire to start developing and the need to strip down a workbench
$...disk.
$My question is this; How much of the stuff on the workbench disk can be
$junked? I want to build a workbench disk that has emacs, a compiler (TDI
$Modula-2), and the TDI and Amiga libraries needed to compile and link a
$program.
$
$I know I can junk the device drivers for printers I don't have. But what
$about fonts? Can I dump all the fonts? Or, must I keep at least one. What
$about the system commands? Most of the system commands look like they can be
$dumped, I can always load a different disk if I need something other than
$cd, dir, or delete, right? How wrong am I and what have I missed?
$ Bob Pendleton
$ Evans & Sutherland Computer Corporation
$UUCP Address: {decvax,ucbvax,ihnp4,allegra}!decwrl!esunix!bpendlet
$Alternate: {ihnp4,seismo}!utah-cs!utah-gr!uplherc!esunix!bpendlet
$I am solely responsible for what I say.
$---
The minimal workbench disk:
directory c
cd dir delete rename copy (maybe a couple of others...I don't even
have any of these, I use a shell) AN EDITOR which DOESN't need an 'empty'
directory or whatever.
directory s
startup-sequence (mine starts at least 2 CLI's and gets rid of
the original so the new ones have sizes/names of my pref).
directory devs
printer, serial, parallel
system-configuration
directory l
ram-handler port-handler disk-validator
fonts: NUKE the entire thing unless you use notepad. The fonts you THOUGHT
you needed are in Kickstart (topaz 8/9).
That's about it. You might want preferences, but usually, once you set it
up, you can forget it.
Note - change your startup-sequence so it doesn't "loadwb" because in
general, you don't need this for development, and if you do during your
sessions you can just type in loadwb yourself. I blow away all the "echos"
too because they just slow down power-up.
If you have spare ram - use it! This may mean copying some commands into
ram and setting your path to look there first, or making your compiler
put its temporary files there, etc. Such tweaks can greatly improve
productivity. If you have a hard drive, the above becomes somewhat of
a different story.
My development system consists of an Amiga 1000 with 2Meg on the side, plus
MicroForge (ain't as bad as the critics say... I wish the driver were
updated to 1.2, but the company's history as I understand...) 20Mb hard
disk, and I use Perry's recoverable ram disk to make reboots quick. With
that lot I can really cook.
Paul.
Disclaimer: I work for Commodore but opinions expressed are mine only.mjp@spice.cs.cmu.edu.UUCP (02/12/87)
Keywords: If you want to strip down your Workbench disk, you can do the following: * If you don't use the workbench, trash loadwb and all .info files. Kill all instances of Trashcan and its .info files. * get rid of all the demo programs like lines, spots and dots. * go to the System directory and trash things there you're not likely to use, like IconEd. I kept Diskcopy, Format, Setmap, GraphicDump and moved Preferences to the System directory. * go to devs/keymaps and trash all the keymap files except usa0 (the 1.1 default keymap). Keep usa2 if you want dvorak. * go to devs/printers and kill all printer drivers except for the one you're using. * go to c and trash Ed and Edit. Replace them with a decent editor like Emacs, MED or TxEd. * go to fonts and remove the directories and files corresponding to the fonts you won't be using. I still have my fonts, until I really find a need for them to go. * go to utilities. If you have an aversion to the Calculator or the Notepad, kill them. I still have both, but I'm thinking about nuking Notepad so I can have Matt's Shell and Perry's RRD around on my Workbench disk. * If you have no need for speech in your programs, get rid of devs/narrator.device and libs/translator.library. I keep these around because I like to play Reversi every now and then, which talks. Following these suggestions, you can free up about 256K-300K on your Workbench disk for other things. I load that space up with mg1a, vt100, shar, arc, the uu twins, and other handy utilities. I still have the full complement of AmigaDos commands at my disposal as well as full use of the system libraries and devices (which you shouldn't touch unless you're sure you don't need them). -- +----------------------------------------------------------------------------+ | Mike Portuesi / Carnegie Mellon University Computer Science Department | | | | ARPA: mjp@spice.cs.cmu.edu | | UUCP: {harvard | seismo | ucbvax | decwrl}!spice.cs.cmu.edu!mjp | | | | ``Amiga hackers do it graphically, with lots of sound effects'' | +----------------------------------------------------------------------------+