[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

2628.0. "LATTICE-C V5.0.1 WONT COPY???? " by SHRARA::BAKER (Mt. Rushmore, "Headtime for Ron-zo") Wed Jun 07 1989 03:16

	I received my Lattice-C V5 upgrade the other day, its certainly a LOT
more comprehensive package than the V4.0 system.
	
	I read the user's guide and it stated:
		1. The 5 disks are unprotected
		2. You should be kind to yourself and make working copies of the
diskettes, using the normal workbench copy.
		3. The 1st disk is bootable

So I plonked in the kickstart disk (V1.2, it said it ran with V1.2 of the 
workbench), put in the disk-1 at the workbench prompt, it went away to think 
about it, and lo the insert workbench disk sreen appears again.
So, no luck with claim 3

I boot using my workbench disk, and put the disk-1 into df1:, the big square 
Lattice-C disk icon appears. It does so for all 4 of the other disks as well.

I try them in df0: and to a disk every one of them comes up df0:BAD, great.
Yet I can read them on df1:

I try a copy on df1:, this results in "This is not a copyable disk" message.
So df1: will read the disk, but it wont copy it.

I thought to myself it may be a drive alignment problem with one of my drives,
but I've never had a problem reading disks made by this system or for that 
matter disks produced on other Amigas. Could the wonderful people at Lattice
have a batch of dud disks or one reproduction machine a little askew?
I copied another of my disks to test out the two and no problem.



Has anyone got any ideas on this?
I dont think my warranty would be real together if I have to ship the damn things
from Australia to the US for replacement (seems to be no distributor here), and 
they seem to be readable on df1: except for copy.

Thanks for any help,
John
SWS/E, Sydney
T.RTitleUserPersonal
Name		DateLines
2628.1Try TurboBackup#FRAMBO::BALZERChristian Balzer DTN:785-1029Wed Jun 07 1989 08:148
    If you have access to it, try TurboBackup from Fish #139.
    It will tell you exactly where problems are and allow you to retry
    as often you desire. Also try both directions (df0: <-> df1:).
    In case TBm can't do it, you're in for the big shipping action '89.
    ;-) :-(
    
    Regards,
    	<CB>
2628.2Had no problem copying them myselfGLDOA::APPLEMANSat Jun 10 1989 17:047
    I have Version 5 and know for a fact that it is not copy-protected
    and will copy with any standard copy program.  If your disks are
    coming up bad, then the problem is either in your disk drives or
    the way that you are copying them.  The standard amiga copy program
    should work (drag the disk icon onto a blank disk).
    
    Ken
2628.3I had the same!JGO::CHAPMANMon Jun 12 1989 07:267
    Funny, I had exactly the same message when I first got 5.0 out the
    box, and I never did figure out why. I tried 'duplicate' from the
    workbench menus on all 4 discs, same result. Since I have one floppy
    and a hard drive, I had to copy each disc to a separate directory
    on the hard drive and then copy back to df0:. This way I had no
    problem (except it took about 2 hours!).  As I say I didn't investigate
    too far.
2628.4Life with one floppyTLE::RMEYERSRandy MeyersThu Jun 15 1989 22:0914
Re: .3

>Since I have one floppy and a hard drive, I had to copy each disc
>to a separate directory on the hard drive and then copy back to df0:. 

It turns out you didn't have to do this.  DiskCopy from the CLI
or Workbench (using the duplicate menu) is smart enough to copy a
floppy on a one drive system.  It will read several tracks from
the source disk, and then pause for you to insert the target disk.
You keep swapping disks when prompted by the system until the
disk is copied.

I don't know what problems folks had with the Lattice disks.  Mine
were fine.
2628.5The exact detailsJGO::CHAPMANTue Jun 20 1989 07:0332
    Re .4
    
    Yes, maybe I wasn't clear. I use and never have a problem with diskcopy
    and swapping disks following the prompts - but these discs wouldn't
    copy with diskcopy !
    
    .4 mentioned using diskcopy from Worknench and CLI. It reminde me
    I probably didn'y try it from the CLI, only Workbench. So last night
    I tried again to copy them. Note I'm using my COPIES of the masters,
    made use COPY as per .3. The results were identical to my first
    attempts, and the same for all five disks - so I don't think it
    is the disks.
    
    1) Using Duplicate from the Workbench menu:
    
    THe screen immediately gives an error flash, and the message "This
    disk cannot be copied" appears on the title bar.
    
    2) using Diskcopy from CLI. This worked! (on my copies at least,
    I didn't try it on the original)
                           
    3) Copy from the CLI worked.
    
    4) Copying by dragging icons worked.
    
    
    Any ideas ?
    
    I'm using KS1.2 and WB1.2. I meant to try WB1.3 Diskcopy, but didn't
    have time. Is it any different?
    
    Colin
2628.6Icon ProblemTLE::RMEYERSRandy MeyersTue Jun 20 1989 08:3318
Re: .4

I got an idea from your description.  I just checked the disk icon for
the first Lattice V5 disk, and it bore out my theory.

Lattice didn't set the default tool for the disk.  When you try to
duplicate a disk or copy it by dragging, the Workbench looks at the
default tool stored in the disk icon to figure out what program to use.

A proper disk icon has a default tool of:

	SYS:System/DiskCopy

Since the Workbench couldn't find the default tool, it couldn't
duplicate the disks!

You can use "Info" from the Workbench menu to set the default tool
for the disk.  You can then copy it using the Workbench.
2628.7A light goes onJGO::CHAPMANWed Jun 21 1989 06:466
    Aaaaaaaaaaaaah,
    
    Obvious when you know. Thanks a lot.
    
    Colin
2628.8ANT::JANZENcf. ANT::CIRCUITS,ANT::UWAVESWed Jun 21 1989 12:487
    My Lattice disk 1 came up bad last night, but later it acted good.
    The other disks were good.  They wouldn't copy from workbench, even
    after I set the default tool to SYS:System/DiskCopy
    .
    So I used CLI and that worked.  
    I am NOT very impressed with Lattice so far...
    Tom
2628.9Finally used my headBERAQ::BAKERMt. Rushmore, &quot;Headtime for Ron-zo&quot;Mon Jun 26 1989 02:4016
    I finally switched my brain up a gear and copied from DF1 to DF1 the
    whole lot without any problems. The copies boot fine (the originals
    didnt).
    
    I'm happy now, the product looks excellent and the attention to detail
    in the documentation is great.
    
    I'm still not sure that I wouldnt have been happier changing to
    Modula-2, but I guess that's just my mindset towards C rather than
    anything to do with the Lattice environment. I've already stated what
    I think of Lattice in other notes, hopefully this product is going to
    soften my attitude.
    
    Thanks again for the help,
    John
    SWS/E, Sydney.