🚀 go-pugleaf

	katzer@esp68.nrl.navy.mil (D. Scott Katzer) writes:

	   I bought Warp v3 on floppies on Saturday (CD-ROMs were sold out) and
	tried to install it on this Micron 486/66 EISA/VLB system.  I've been
	unsuccessful.  I've been using OS/2 for Windows, Warp Beta 1 and Beta 2 on
	this system with no major problems (and no install problems of 
	consequence), but they were installed from the CD-ROM. I wouldn't think it matters.

	   Hardware:
	      Micron 486/66 EISA/VLB system
	      Phoenix BIOS
	      16 MB RAM - 1 SIMM
	      256 kB cache
	      Ultrastore 34F VLB SCSI-2 controller (PUN=7, LUN=0)
	      Diamond Stealth Pro (S3-928) VLB 1 MB video card
	      Teac siamese floppy drive
	      Chinon CDS-535 SCSI CD-ROM (PUN=6, LUN=0)
	      Conner 31370 1.3 GB hard disk (PUN=0, LUN=0)

	   I followed the instructions on p.336 of the "User's Guide to OS/2 Warp"
	manual for installing drivers for an unsupported SCSI controller.  I 
	deleted the IBM2*.* drivers (which are for MCA systems) from a copy of disk
	1 then copied ultra14.add (18992 bytes 06-16-93 9:30a, the latest I've
	found) to disk 1.  The config.sys on disk 1 was modified by adding
	basedev=ultra14.add and by REMming out the IBM2*.* lines.  (This has to be
	done because there's only 2 kB free on disk 1 and the ultra14.add driver won't fit otherwise.)

	   I tried using the simple install with 92 MB free on C: (a 120 MB 
	partition), and the advanced install on a freshly formatted 120 MB HPFS 
	partition D:.  Both failed the same way.

	   The installation goes fine as follows:
	       Installation disk 0
	       Modified Disk 1
	       Disk 2
	       Disk 3
	       Disk 4
	       Disk 5
	       Disk 6
	       Installation disk 0

	   The installer then asks for Disk 1.  I insert either the modified disk 1
	or the original disk 1 and it almost immediately fails with a red screen 
	saying a copy failed, look at the install.log, fix the problem and try
	again.  Here's the end of the install.log when trying to install on the D:
	HPFS drive:

	[...]
	D:\OS2\BOOK\PERFBK.INF
	D:\OS2\BOOK\APPLBK.INF
	D:\OS2\INSTALL\UNINSTAL.EXE
	D:\OS2\INSTALL\DATABASE.DAT
	System files are being copied to your fixed disk
	System file transfer is complete
	DISK 1
	SYS0002: The system cannot find the file specified.
	         Copy Error    An error occurred when System Installation tried to
	copy   a file.

	*** end install.log ***

	   The User's guide says that this copy error could be due to 3 things:

	   1.  The floppy is bad.
	   2.  Not enough free space is available.
	   3.  The hard disk contains errors.

---Forget this.  I had something similar.  You need to check the following:
1. Your A: drive is 3.5" 1.44Mb;
2. Delete absolutely EVERY file and directory associated with OS/2;
3. Delete or rename your AUTOEXEC.BAK and CONFIG.BAK files;
4. Re-install DOS (you could try repairing your AUTOEXEC.BAT & CONFIG.SYS
   files and re-installing OS/2, but it's quicker to re-install DOS than to
   find out if re-installing OS/2 might work);
5. Re-check point 3;
6. Re-install OS/2;
7. Edit your AUTOEXEC.BAT & CONFIG.SYS files for DOS.  Check that the
   last lines are not corrupted.  If they are, identify & separate the
   separate DOS statements by inserting a CR at the appropriate points.

See my last week's posting in aus.computers.os2 for more details.

	I don't believe any of these errors apply.  The hard disk isn't full and 
	chkdsk finds nothing wrong.  The floppy is a new 3M HD disk and chkdsk says
	there's nothing wrong with it either.

	   The SYS0002 error message says that it is looking for a file and can't
	find it.  I'd guess that it's trying to copy the IBM2*.* files or it is
	trying to copy the ULTRA14.ADD file.

	   I've racked my brain, but there seems to be no obvious way to solve this
	problem.  I've tried copying the ULTRA14.ADD to the install partition, but 
	the install always fails the same way.  In addition, for some reason, the 
	install always starts over from the beginning after one of these failures -
	that is, there appears to be no way to fix the problem and continue the
	installation once the problem has been fixed.

	   Anyone have any idea what the problem is?  Can someone figure out 
	what list of files the installer reads during the install?  What else 
	can I check?  I'm stumped.  :-(  This is the first time I've ever been able
	to install OS/2 (2.0, 2.0+SP1, 2.1 March Beta, 2.1, 2.11, 2.1 for Windows,
	Beta 1, and Beta 2) on a system.  :-<  :-<  :-<

	   Please reply by E-mail (to my ESTD account) if possible because our news
	spool fills up very quickly.  I'll post a summary.  I'll call IBM first
	thing in the morning Monday....