[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:AMIGA NOTES
Notice:Join us in the *NEW* conference - HYDRA::AMIGA_V2
Moderator:HYDRA::MOORE
Created:Sat Apr 26 1986
Last Modified:Wed Feb 05 1992
Last Successful Update:Fri Jun 06 1997
Number of topics:5378
Total number of notes:38326

1786.0. "AmigaDOS 1.3 on a 512K Machine" by NAC::PLOUFF (Cider Season Has Begun) Tue Oct 18 1988 10:25

    Well, the new 1.3 operating system package is sure chock-full of
    nice features, but using the Workbench disk out of the box is hard
    on us cheapsk... err, frugal persons who have 512K machines.  I
    personally own a stock A1000.  So this note is for discussion of
    1.3 configurations that run well on a 512K machine.  All ideas,
    suggestions and results will receive serious consideration from
    yours truly.
    
    First of all, my customized 1.2 Workbench boots me up with about 380K
    of free memory (with DMouse installed).  Popping a CLI takes this down
    to about 360K.  The default 1.3 startup sequence boots to 350K free,
    and popping a shell with DMouse brings it down to roughly 310K.  This
    is little free RAM!  Much of the OS seems to have grown slightly.
    Here two identifiable culprits are the shell-segment and the resident
    commands.  Over the weekend I will try various combinations of the
    new console (NEWCON:), the Dillon/Drew shell and Conman, to see
    if something can be made smaller.
    
    Forget about running the recoverable ram disk RAD: in 512K. 
    
    Two questions aside:
    
    1.  The startup assumes you have a real-time clock.  I don't.  Does
    anybody remember the syntax to get input to the DATE command when
    it is called in the startup-sequence script?  These don't work:
    
    		DATE < CON:
    		DATE < *
    
    2.  Anybody know where to get 1 Mbit DRAMs cheap (only half :-).
    
    Wes Plouff
T.RTitleUserPersonal
Name
DateLines
1786.1already there?WOODRO::LEIMBERGERTue Oct 18 1988 10:514
    I thought 1.3 had a shell,command line editing etc... built in.i
    haven't upgraded yet so I am not sure but it sounds like some may
    have redundent tasks out there.
    							bill
1786.2Thanks for the memoriesCSSE::WARDTue Oct 18 1988 11:249
    I finally gave in.  A minimum system with caching a hard drive
    is best done with a one meg min.  Survival Ram disks is a poor
    mans hard disk - you need memory for that too.
    
    I have an A1000 with memory expansion that can be hung off a A2000.
    The problem is the supply and appearance of the internal 8 meg
    from Commodore. [Less chips]
    
    Good luck... Its' like shopping for a car.
1786.3DATE ?AYOV10::ATHOMSONC&#039;mon, git aff! /The Kelty ClippieTue Oct 18 1988 11:4211
    The date command is 
    
    .
    .
    DATE ?
    .
    .
    
    Has anyone outside the US seen 1.3 yet ???
    
    					Alan T.
1786.4Remember when 256K DRAMs were $2.00?NAC::PLOUFFCider Season Has BegunTue Oct 18 1988 11:5613
    re: .1 (?) built-in shell
    
    Yes, 1.3 comes with a shell that has command-line editing, command
    history and configurable RAM-resident commands.  My gripe in .0
    is that all this takes too much memory on my system, and I want
    to be selective about features.  Will report my results as they
    happen.
    
    re: .3
    
    Thanks.  Will try "DATE ?".
    
    Wes
1786.5V1.3MTWAIN::MACDONALDWA1OMM 7.093/145.05/223.58 AX.25Tue Oct 18 1988 14:1025
    I wonder if anyone has had an opportunity to compare V1.3's Shell
    with Dillon's V2.10 Shell. Are they one in the same?
    
    The Clockptr is cute. Dunno why they didn't add a colon to the display
    and perhaps an arrow.
    
    I assume that V1.3 FFS doesn't require a hard disk reformat if the
    hard disk was previously formatted using a Beta test version of
    FFS. Anyone know for sure?
    
    DosType keyword doesn't seem to be recognized on my Mountlist, although
    I understand it's not necessary to have it.
    
    Hmmm ... the FED (font editor) now recognizes ALL fonts in the font
    directory.
    
    No apparent changes to BASIC (the filesize is exactly the same as
    V1.2). Anyone know of any changes?
    
    The manual that comes with 1.3 is nice. It's about time they started
    providing that type of detailed information.
    
    Now, where is V1.3 of ARP????
    
    Paul
1786.6Shell 2.10?LOWLIF::DAVISThat&#039;s not a BUG, it&#039;s a FEATURE!Wed Oct 19 1988 00:343
Drew/Dillon Shell 2.10?  I've only seen up to 2.07.  Am I falling behind??

...richard
1786.7First pass startup sequence for small machineNAC::PLOUFFCider Season Has BegunThu Oct 20 1988 10:5991
    Here is a v1.3 startup sequence suitable for 512K A1000 machines.  It's
    a quick midnight hack done in the two days since v1.3 came on sale in
    this area.  Do whatever you like with it, but reports and suggestions
    are welcome. 
    
    The problem with the default startup is that it uses too much RAM. Here
    are the free RAM totals using my v1.2 Workbench disk and the v1.3 disk
    straight from the Enhancer box. Configuration:  A1000, 512K, DMouse
    running, disks inserted in DF0: and DF1:, measured just after reboot. 

					CLI/	CLI/Shell 
				WB only	Shell	running
				-------	-----	-------
	v1.2			381248	  C	372912
	v1.3 as distributed	348232	  S	314600
		 (no DMouse)

    Plainly v1.3 is oriented toward 1 meg and larger machines, not the
    obsolete A1000.  I wanted the command line editing and history features
    of the new shell. I wasn't concerned about command aliases and didn't
    think I could afford much memory for resident commands.  Turns out that
    the desirable features are part of the NEWCON: handler, while the rest
    depends on the shell-segment.  So l:Shell-Seg and much of the
    s:StartupII file got pitched.  Without the shell-segment there seems to
    be no difference between Newshell and NewCLI. 

    At the end of this message is my personal startup-sequence, distilled
    from the two default startup scripts.  The only things I customized
    were the DMouse and assign ARCTEMP: commands.  I evaluated the memory
    cost of each of the six features discussed below, and chose all except
    FastFonts (FF).  The free memory totals are: 

	no features enabled	379552	  C	371176
	all features enabled	366744	  C	347512
	final version		369976	  C	350744

    Here is the memory cost of each feature: 

	setpatch			3224
	addbuffers DF0: 10		5464
	FF enabled			3232
	NEWCON: mounted			  88
	NEWCON: running		       10856 vs. CON:
	2 makedirs and 3 assigns to RAM: 712

    Now, astute readers will notice 88 bytes misplaced between the free RAM
    comparison and the total of the cost table.  But it's close enough to
    make decisions.  Any feature can be disabled by commenting it out with
    a ';' at the beginning of the line.  If NEWCON: is not mounted, be sure
    to change the reference to it in the DMouse command line. 

    Perhaps someone could do a comparison of this setup versus using CON:
    with either the Dillon/Drew shell, or ConMan plus WShell. 

    Since DMouse does not inherit a search path, I have also included my
    CLI startup script.  Happy hacking! 
    
    Wes

---s:startup-sequence-----------cut here-------------cut here-----------
;Small memory v1.3 startup   NWP 10-20-88
Addbuffers df0: 10
c:SetPatch >NIL: ;patch system functions
c:cd c:
echo "A1000 512K Workbench disk.  Release 1.3 version 34.20*N"
BindDrivers
echo "Last date set: " NOLINE
date < NIL:
echo "Set new date: " NOLINE
date ?
;FF >NIL: -0 ;speed up Text
mount newcon:
;
makedir ram:t
makedir ram:env ; set up ENV: directory
assign T: ram:t ;set up T: directory for scripts
assign ENV: ram:env
assign ARCTEMP: ram:
;
dmouse -A0 -m25 -C "NewCLI newcon:0/100/640/100/NewCLI"
;
SYS:System/SetMap usa1 ; Works even on A1000
path ram: c: sys:utilities sys:system s: add ;set path for Workbench
LoadWB
endcli >NIL:
--------cut here----------------cut here-------------cut here-----------

---s:CLI-Startup----------------cut here-------------cut here-----------
c:prompt "%N> "
c:path ram: sys:utilities sys:system add
--------cut here----------------cut here-------------cut here-----------
1786.8BAGELS::BRANNONDave BrannonThu Oct 20 1988 11:187
    re: .7
    
    do you need that SetPatch?  I thought that was just the fix for
    the no Guru bug in the 1.2 ROM for systems with C0000000 memory,
    like the A2000 and 1Meg A500s (formerly known as SetAlert).
    
    -Dave