[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

4927.0. "Minix 1.5 problems" by SALSA::DUPRE (God is real (unless declared INTEGER)) Fri Jul 26 1991 18:05

Hi,
	I just received my Minix V1.5 order and I'm have a bit of a problem
	getting it running. I hope someone out there with a little more
	experience with Minix can help.

        First I copied the Minix BOOT disk and ran the Minstall1.3 script,
	that seemed to work fine. Then I formatted the 8 blank floppies to 
	copy the rest of the distribution with MSH messydosformat again all is
	well. Now this is where the problems start. The Doc's say that the
        distribution is in IBM 720kb format except for the BOOT disk but I
        can't get MSH to read the distribution floppies. So back to the Doc's
	I go. 
	
	Ok there are utilities. "Transfer" to format the disks in Minix
	format, and Diskcopy under Minix to do disk to disk coping.
	So I use the AmigaDos utility (Transfer -f) on the MINIX BOOT disk
	to format all the floppies. Then I boot-up Minix to run diskcopy.
	After the first two disks load Minix asks for the /usr disk I pop it
	in, hit return and I'm getting write error messages on the /usr disk.
	I'm thinking that's alright I have the write protect set on the disks.
	I'M NOT GOING TO WRITE ENABLE THESE SUCKERS UNTIL I HAVE THEN COPIED.
	After a few sec's I login as root get the $ prompt I do a cd / and
	then run diskcopy, it asks for the source disk and starts reading it
	in a few sec's the screen starts to fill with garbage.
	It looks like diskcopy is reading the source data into chip memory
	and its being displayed on the screen. It reads from the disk a
	little then a block of garbage gets put on the screen. This continues
	until the system hangs and I have to reboot.

	So I think, I'll try the Minix V1.5.10 boot images that I have 
	(Thanks to John Guineau). I copy the new V1.5.10 file to the BOOT disk
	and reboot the system. The problem now is if I try to do a ls -l /bin
	I get a error message NOT ENOUGH CORE. But I try diskcopy and it works.
	No more garbage on the screen and the disk is copied.

	Also I'm having a problem with the transfer program on both the
	Amiga side and the Minix side. Sometimes it works and sometimes
	it dosen't. On the Amiga side it seems to not like to transfer large
	files to the floppy.

	My system configuration is a A2000, 8UP memory card with 8 MB,
	1MB agnus, Hardframe/40mb Rodine, A2090 with two ST506 HD's.


	My questions now are.

	1. Can Minix V1.5 run on this configuration?

	2. Has anyone seen these problems before and have a fix?

	3. Am I suppose to be able to read/write Minix disk with MSH?

	4. Is there a Amiga program that will read/write Minix disks?

	5. Does this sound like bad distribution disk from P.H.?

	6. Are there any other Amiga utilities out there to copy from
	   AmigaDos to Minix?

Thanks in advance		Also posted to Minix notes.
Bob Dupre

T.R	Title	User	Personal Name	Date	Lines
4927.1		STAR::GUINEAU	but what was the question?	`Fri Jul 26 1991 18:16`	42
	> My questions now are. Ah yes, frustrations of long past :-) > 1. Can Minix V1.5 run on this configuration? Should run fine. Don;t expect to get hard disk though. The hard disk only supports A2091, A590 and the A3000 internal SCSI. > 2. Has anyone seen these problems before and have a fix? You should definelty use the latest stuff I posted (found on DFS::MINIX:) since it fixes many nasty bugs in the original version. I think I numbered this version wrong. The original was 1.5.10, the update is 1.5.10.1 (I think!) > 3. Am I suppose to be able to read/write Minix disk with MSH? No. Minix has it's own file system. MSH uses the MSDOS file system. The low level format is the same (IBM 720K) but the layout of data ("the file system") is different. > 4. Is there a Amiga program that will read/write Minix disks? No, not yet. The only way is to use transfer (which by the way is supposed to be much better on the update disk. Use that one and throw away the version that came with the original distribution). I believe you can also use the ST version of the copy program on the Minix side and use DOS2DOS (or something like that) on the amiga side. > 5. Does this sound like bad distribution disk from P.H.? There was a problem way back where PH was shipping bad disks. I'm not sure if they fixed it. It took me a coupel months to get new ones from a very nice person in the UK! > 6. Are there any other Amiga utilities out there to copy from > AmigaDos to Minix? No.
4927.2	Thanks for the help	SALSA::DUPRE	God is real (unless declared INTEGER)	`Tue Jul 30 1991 02:37`	44
	John, Thanks for the quick reply. I have three files that I copied from DFS:: Amiga_1_5_10_boot.lzh Amiga_1_5_10_src.tar a3000final.txt The boot lharc file is what I used to build my boot disk. It seems to still have some problems though. I have to chmem ls to 12k to get it to work and transfer is still flakey but at lease diskcopy works and I can backup the master disks. Also I can't get the files from A3000final.txt to unpack. When I run uudecode on it, it tells me it can't fined the end of file or end command or something like that. I was able to de-compress the output and get a tar file but it has some bad blocks in it. Is this the 1.5.10.1 release? > Should run fine. Don;t expect to get hard disk though. The hard disk only > supports A2091, A590 and the A3000 internal SCSI. Yes I did expect to use the hard disk. The extract below is from the amiga_1_5_10_src.tar. Or do yuo know of a problem with the A2090? /* "amwini.c" Author: Raymond Michiels * * This file contains a driver which supports the following hard disks: * * Commodore A590 XT / SCSI * Commodore A2090 SCSI (not ST-506!) * Commodore A2091 SCSI * Commodore A3000 SCSI * * The driver supports two operations: read a block and write a block. * It accepts two messages, one for reading and one for writing, * both using message format m2 and with the same parameters: Thanks again for your help John, You've saved some of my hair. Bob Dupre The only DECie AMIGAn in Tucson,AZ.
4927.3		STAR::GUINEAU	but what was the question?	`Tue Jul 30 1991 10:34`	16
	> Amiga_1_5_10_boot.lzh > Amiga_1_5_10_src.tar These are the 1.5.10.1 release. I'm not sure what's in a3000final.txt but everything you need is in the first 2 plus the original distrubution. The Amiga_1_5_10_src.tar file contains patches (diffs) to the original source. > Yes I did expect to use the hard disk. The extract below is from the > amiga_1_5_10_src.tar. Or do yuo know of a problem with the A2090? Maybe it works then. You'll know if, when you boot Minix, you get a hard disk partition table printed. If it does, they recognize the 2090 and you can try to set it up as they describe in the docs... john
4927.4	Your drives are ST-506?	HSSTPT::WILSONTL	Lead Trumpet (Read that...LEED!)	`Tue Jul 30 1991 13:13`	11
	Maybe I'm missing something...You said you DID expect it to work. > * Commodore A590 XT / SCSI > * Commodore A2090 SCSI (not ST-506!) > * Commodore A2091 SCSI ^^^^^^^^^^^ > * Commodore A3000 SCSI > * You said you had ST-506. Tony
4927.5	The A2090 and A2090a support SCSI and ST-506	PAMSRC::63653::BARRETT	Keith meister, making notes	`Tue Jul 30 1991 13:20`	0
4927.6		HSSTPT::WILSONTL	Lead Trumpet (Read that...LEED!)	`Tue Jul 30 1991 13:38`	2
	The A2090 et al. may support ST-506, but the driver in Minix may not. Just basing my comment on what the text said in the listing.
4927.7		STAR::GUINEAU	but what was the question?	`Tue Jul 30 1991 18:20`	4
	> The A2090 et al. may support ST-506, but the driver in Minix may not. > Just basing my comment on what the text said in the listing. I believe that's correct..