Conference hydra::amiga_v1

    Check out NORSE""::amiga:[upload]  I put the only file that I could
    find on our local bbs's there.  It seems to be complete, the liscense
    info is there and everything

So what's special about it?

    I installed it on my A2620-based A2000, with no trouble.  I haven't
    tried everything yet, but everything I've tried still works.  Music-X
    still can't read bulk dumps from my TX802.
    
    The following is the ReadMe file.  It explains the changes.
        John Sauter
    ============================================================================
; This is the Commodore-Amiga update for Workbench 1.3.  These files
; are meant to replace some of the files in the Commodore Workbench 1.3
; distribution.
;
; The terms of this distribution are located in the file ReadBeforeUsing.
; Please read this agreement before installing the files on your system.
; 
;
;All of the following software, is
;Copyright 1989 Commodore-Amiga, Inc.  All Rights Reserved.
;
;This README notice must remain intact, unchanged, and must
;accompany the distribution of any or all of this software.
;
;The release contains new versions of the following programs:
;
;SetPatch, LoadWB, Eval, SetClock, Mount, DiskDoctor,
;Format, Diskcopy, FastMemFirst, NoFastMem, SetMap,
;CMD, ClockPtr, Pipe-Handler, Speak-Handler, FastFileSystem, 
;Aux-Handler, version.library, info.library, serial.device, 
;printer.device
;---------------------
;
;This is what was changed in each of the programs:
;
;C
;-
;SetPatch
;	a) Alert code fixed to work with 1 meg chip ram machines.
;	b) TrackDisk GetUnit patch added.
;	c) DOS Execute() patched that uses RUN from the resident list	.
;	d) UserState patch for 68010.
;
;LoadWB
;	a) LoadWB now closes icon.library.
;
;Eval
;	a) () added; also parses strings in a more relaxed manner.
;
;DiskDoctor
;	a) incorrect error message (out of memory) changed.
;	b) uses BufMemType so works with large hard drives.
;
;FF	: NOTE - NOT AVAILABLE FOR ELECTRONIC DISTRIBUTION
;	a) incorrect use of font flags fixed.
;
;SetClock
;	a) reset option now skips clock validity check.
;
;Mount
;	a) BAUD and CONTROL mountlist keywords added for multiserial use.
;	b) full option added to startup to create handler
;  	   entries with full environment support.
;
;System
;------
;Format
;	a) works with large hard drives (uses bufmemtype).
;	b) inhibit logic fixed.
;	c) secondary results are properly set.
;	d) better error messages.
;	e) only opens icon.library if it needs icon.library.
;	f) NOFFS keyword removed (was not useful)
;
;Diskcopy
;	a) uses fast memory in a single drive copy if chip ram is unavailable.
;	b) single disk copy on a 1 meg chip ram machine works.
;	c) verify by default; noverify option added.
;	d) Only opens icon library if it needs icon library.
;	e) If diskcopy fails, the failure cylinder is left showing.  
;	   on the screen.
;	f) secondary results are properly set.
;	g) better error messages.
;	h) MULTI keyword allows multiple copies of single disk
;
;FastMemFirst
;	a) tests for chip memory properly (it worked fine before;
;           however, it was incorrect).
;
;NoFastMem
;	a) changed to also specific divert calls on fast memory to public 
;	   memory.
;
;SetMap
;	a) kludge added to make sure that, under V34Kickstart  and below,
;	   a keymap never spans a 64K boundry.
;
;L
;-
;Pipe-Handler
;	a) names are now case-indifferent.
;
;Speak-Handler
;	a) no longer loses 10K when unknown packet received.
;        b) OPTs are now case indifferent.
;
;FastFileSystem
; 	a) File system no longer fails if the boot block of a disk contains
;	   a zero in the first longword.
;
;	b) Whenever a file not in the root was altered, the datestamp of the
;	root block would be altered.  This has been fixed, the last modified
;	date is now altered instead.
;
;	c) Due to a calculation error when writing out the bitmap the disk
;	would always validate on restart if it was >308Meg.  This has
;	been fixed.  New limit is REALLY 2.5 Gig.  Tested to 600Mb.
;
;Aux-Handler
;	a) Sets the flags to 0 on open of the serial.device.
;
;Utilities
;---------
;
;CMD
;	a) works with device names that have odd number of characters
;	b) QUERY functino added so works with printer drivers that
;	   query the printer.
;
;ClockPtr
;	a) switched over to the European version with the 24 hour option.
;
;Libs
;----
;
; info.library
;	a) no longer improperly combine tooltypes
;
;version.library
;	a) version number changed.
;
;devs
;----
;serial.device
;	a) no longer crashes on mismatched baud rate.
;	b) Refuses to open unavailable units.
;	c) Lower overhead.
;
;printer.device
;	a) support for multipass printers fixed.
;
;
;
; Before installing these files in your SYS: disk, it is a good idea
; to make a backup, in case problems arise later.
;
; We suggest unpacking the files in a directory in RAM, using the x//
; option to ZOO.  The directory should already exist.
; For example, to unpack in a directory called wb in RAM: (ZOO file called
; WB1.3.1 on DF0: )
;
; mkdir ram:wb
; cd ram:wb
; zoo x// df0:WB1.3.1
; copy ram:wb sys: all
;
; After unpacking the files, and placing the files in your SYS: disk,
; it will be necessary to correct the protection bits.  Execute this
; ReadMe file (the one you are currently reading) to do this, ie
;
; Execute Readme
;
; The files now have the proper protections for normal system operation.
;
;
;

protect c:Mount prwed
protect c:SetPatch rwed
protect c:DiskDoctor prwed
protect c:LoadWB rwed
protect c:SetClock prwed
protect c:Eval prwed
protect l:Pipe-Handler rwd
protect l:FastFileSystem rwd
protect l:Aux-Handler rwd
protect l:Speak-Handler rwd
protect devs:serial.device rwd
protect devs:printer.device rwd
protect libs:info.library rwd
protect libs:version.library rwd
protect sys:System/SetMap rwed
protect sys:System/Format rwed
protect sys:System/DiskCopy rwed
protect sys:System/FastMemFirst prwed
protect sys:System/NoFastMem rwed
protect sys:Utilities/ClockPtr rwed
protect sys:Utilities/CMD rwed
;
echo "Protection bits now set on files."
    

    I just installed 1.3.2 this weekend, it has worked fine so far, but I
    really didn't have any time to do any serious work.  I do have two
    concerns though.
    
    	1) c:Eval and c:Mount have created a problem because of ARP 1.3.
    		I have not replaced the ARP version, but I have renamed
    		the 1.3.2 versions to c:EvalNew and c:MountNew.
    
    	2) I aquired a version of the 1.3.2 update locally and compared it
    		to what I got from the net.  The ReadBeforeUsing and the
    		corresponding .info file were not on the local .zoo file.
    		This did not seem to be a big problem since that file seems
    		to be a copy of the file LICENSE.  But the file
    		version.library has different dates and my bdiff utility
    		reports that the files are different.

    
    Here's an odd twist; I logged onto PLINK this evening and was greeted
    by a message announcing the arrival of v1.3.2.  Following that was a
    message warning NOT to post this file on local BBSs.  The message
    claimed that the future of electronic upgrades from CBM would be put in
    jeopardy.
    
    So, I wonder what the official policy is?  Is Commodore only
    sanctioning commercial network distribution?  I wonder if they're
    afraid of widespread 'viral' tampering?
    
    It seems a little unfair to only allow posting to 'pay-for' nets, since
    a vast majority of users don't have access.  Then again, it's
    Commodore's software, so they get to say how it's distributed...
    
    Any inside poop from you developer types?
    
    Ed.
    
    
    

    Re: .5
    
    Nah, no poops from this developer type, but I'll try to clear the
    OFFICIAL latest and greatest upgrade for upload to the EasyNet.
    
    Hang in there,
    
    <CB>
    

    How do you upgrade an A2000 w/ an A2090 Autoboting HD SCSI Controller?
    I called The Memory Location but they didn't seem sure (although they
    agreed with my thoughts).
    
    Anyway, I have copied all the AmigaDOS V1.3.2 files to my Boot 
    Partition as well as the new V1.3.2 Tools disk.  My question is
    where do I go from here.  Do I run:
    
    	INSTALL DRIVE BOOT:
    
    Do I have to do anything to get the latest and greatest
    L:FastFileSystem to my harddrive?  Would doing the latter cause me to
    have to re-format? (NOTE: If answer is yes than V1.3 is fine with me).
    
    Having bought the unit 2nd hand I didn't go thru the initial steps and
    don't want to screw the system up.  The A2090 User's Guide doesn't
    mention INSTALL at all but mentions PREP.  The problem is PREP (it 
    seems) wants to erase everything and I can't believe that is necessary.
    
    I think Usenet mentioned something about using Add/Update File System
    from the HDToolBox drawer on some disk (presumably that came with the
    A2091).  I don't have this.  I have an A2090 Hard Disk Software disk
    that appears to have been bundled with the V1.3 Enhancer Kit.
    
    Any help would be appreciated!  Thanks!
    George
    

George,

I'm pretty sure that all you need to do is unpack the 1.3.2 file
into a subdirectory somewhere. Make sure you specify the option
necessary for the archiving program to create the original
subdirectories (I forget how 1.3.2 was packed - zoo, arc, lharc?)

	ex:	lharc -x x wb132
		zoo e// wb132

	etc.

Now you will have some directories whic are the same as normal amigados
ones (ie  libs,devs, l, etc) and they will contain the updated (1.3.2)
versions of whatever files have changed in those directories.

Simply copy the files to the existing system directories and reboot!

	ex:
		copy devs DEVS: ALL CLONE
		copy libs LIBS: ALL CLONE

	etc..


You definetly don't need to reformat/prep anything. INSTALL is for
floppies only - it makes them bootable.

Hope this helps!

john