Conference hydra::amiga_v1

    
    Hi Debbie...
    
    Couple of things... I'm assuming that you are using an LA50 printer
    driver...
    
    Your Amiga is using version 1.3 of the system software, including a
    file called SYS:Devs/printer.device.  The LA50 printer driver that you
    are using was written to conform with version 1.2 of the system
    software, not 1.3.  As far as I know, the LA50 driver has NOT been
    modified to work with the 1.3 printer.device.
    
    You'll need to replace printer.device with a version from 1.2 in order
    to get text and graphics to work properly.  Unfortunately, the 1.2
    printer output is not as good (and much slower) than the 1.3
    counterpart.  But it's better than --------------------
    
    As much as I'd like to help you immediately, we are expressly
    forbidden from posting Commodore system software on the e-net.  Any
    decent dealer should have a copy of a 1.2 Workbench disk lying around. 
    If you can't get to a dealer conveniently, send me mail and we'll
    figure out another way to help you.
    
    Ed.
    

    Since you are using an LA75 there is another possibility.  This is what
    I am doing currently.
    
    1) Put the LA75 into "Other" mode.  This is done with the Protocol
    button at the far left of the control panel.
    
    2) Copy the CBM_MPS1000 printer driver from the 1.3 Extras disk to the
    devs:Printers directory on Workbench disk.
    
    3) Use Preferences to select this new print driver.
    
    I have been using this setup for over a year now, and it works fine for
    text and graphics.
    

>    
>    Your Amiga is using version 1.3 of the system software, including a
>    file called SYS:Devs/printer.device.  The LA50 printer driver that you
>    are using was written to conform with version 1.2 of the system
>    software, not 1.3.  As far as I know, the LA50 driver has NOT been
>    modified to work with the 1.3 printer.device.
>    
>    You'll need to replace printer.device with a version from 1.2 in order
>    to get text and graphics to work properly.  Unfortunately, the 1.2
>    printer output is not as good (and much slower) than the 1.3
>    counterpart.  But it's better than --------------------

Just as a matter of interest, is anyone working on a 1.3 version of the LA50
driver? (I'd volunteer, but as a brand new user as well, I dont have the
expertise, or the compiler!).

Simon

    I am also in need of some help. I've been using the EMACS editor
    supplied on the Extras disk and have found it easy to use although
    I am unable to view the files I have created from the workbench
    screen. The files do exist because I can edit them again but only
    if I have remembered their name. Does anybody know why this is and 
    if so how do I get the new file to appear as an icon in the directory
    window?
    
    Thanks for any help,
    Barry.

    re: -.1
    
    You can't see the files from the workbench because memacs doesn't
    create icon (.info) files for the documents you've edited. The only
    way to see these files is to fire up a shell and use the 'dir' or
    'list' commands from the CLI. You can then edit them by using the
    command 'memacs myfile'. If you feel uncomfortable using the CLI
    (akin to DCL on a VAX or the DOS prompt on a MS-DOS system) then
    I'd suggest using (and that probably means buying) a wordprocessor
    or an editor which does create icons by default. 
    
    					Alan T.
    
    Just a passing thought; did I see a menu option somewhere giving
    an option of Icons on/off ??? Could it have been memacs ??
    
    

    Re: .4
    
    Barry,
    
    Open a CLI window and enter DIR (and hit Return). If you're at the
    top level of your workbench disk, you should see several directories
    and some files.
    Note the files with the ".info" extension. These files are the ones
    that contain the image data (and some more) that you see on the
    workbench directory windows. Only files with an associated ".info"
    file are visible like this. 
    Most applications can create those icon files for their projects,
    like NotePad.
    There are several Browser/Directory tools available that will allow
    you to see ALL files. And in the future (don't ask me when that
    will be), Workbench version 1.4 will allow you to see the files
    without an ".info" file, too.
    
    Regards,
    
    <CB>

    Many thanks to .5 & .6 
    
    I will be quite happy to see all my lost files using the CLI!
    
    Bye.
    Barry.

    re .5
    
    I know Platinum Scribble allows Icons On/Off.  Don't know of any other.
    
    ken

    While we're onto the subject of emacs, how do I create the initialization
    file (emacs_pro ?) that's read upon startup? The AmigaDOS manual that came 
    with the 500 doesn't mention anything about its format. Do I create it via 
    an editor (i.e. is it ascii? - if so, what's the format?) or do I just 
    change my key bindings via the define key command & assume emacs will save 
    any modified key bindings to this file for me? 

    I used emacs years ago when I did development on UNIX & MS-DOS & seem 
    to remember the existence of a startup file named .emacs_init 
    (& .emacs_ml ?) one of which was ascii & had a specific syntax. As I'm
    getting back into remembering & using emacs, I'd like to modify some key 
    bindings (specifically changing forward/backward word to ^F/^B) to 
    make life with it a lot easier. Thanks,

							-Dom

    The documentation that comes with the Amiga is really lousy as far as
    descriptions of some of the tools is concerned.  There is practically
    nothing on the Icon and Font editor and the info on EMACS leaves much
    to be desired.
    
    The format of the emacs_pro file is straight ascii and you can create
    it with any editor.  Good luck on defining the keys with the emacs_pro
    file.  I've tried and cannot figure out how to do it.  Can't find any
    info in the docs on this.  All the manual says about the emacs_pro file
    is that it exists.
    
    Ken

    Re: -.1
    
>    The format of the emacs_pro file is straight ascii and you can create
>    it with any editor.  Good luck on defining the keys with the emacs_pro
>    file.  I've tried and cannot figure out how to do it.  Can't find any
>    info in the docs on this.  All the manual says about the emacs_pro file
>    is that it exists.

    After a bit of experimenting, I got emacs_pro working. As mentioned, it
    is an ASCII file. I played around with the Bind-Key and Describe-Key
    commands to see what they used for syntax. Here's a short and simple
    emacs_pro file (can be placed in the s directory) to bind the Next-word
    and Previous-word commands to ^F & ^B (makes moving thru the file easier
    rather than having to stretch for the escape key & keep lifting my finger
    off of it :-).

    Bind-key Next-word ^F
    Bind-key Previous-word ^B

    Note: The ^F & ^B sequence must be inserted via the Quote-char command ^Q;
    the emacs commands must be typed exactly as entered.

    Experiment with your own (to modify the keypad keys, function keys the
    Set-key command must be used). I'll also try diddling around with using
    the set command to get emacs to start saving backup files in the t 
    directory.
							-Dom

    Some updates on this for those who are interested. The emacs_pro file
    belongs in the s:emacs directory, not the s: directory as I previously
    stated. And I have found a problem with my remapping of ^F & ^B via
    the previous example - the left & right cursor keys are also remapped
    to move forward & backward a word as well. Bummer. Back to late night
    fiddling and diddling.
							-Dom

    
    Does anyone know how the key designator for the desired key is passed
    to the "key to define:" question; when doing a set-key function? I
    was wondering if the emacs_pro file failing during startup could
    have anything to do with the function not seeing a valid key to
    define because it doesn't recognize the key we are trying to redefine.
    
    I'm I out in left field with this idea? Can anyone comment?
    
    							Dave