| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 5682.1 | run ECU | SAPEC3::BACHOFER |  | Wed Feb 12 1997 05:59 | 8 | 
|  | Hello,
had the same problem on an AS2100.
After running ECU the installation of NT works properly.
HJ Bachofer
DEC/SAP Engineering Walldorf/Germany
 | 
| 5682.2 | There are TWO ECU diskettes | CSC32::K_MEADOWS |  | Wed Feb 12 1997 06:00 | 5 | 
|  |     You haven't run the WNT ECU - that needs to be done before you will get
    Windows NT installed.  Sounds like this is a older system that has been
    running VMS or Unix - check the firmware while you're at it.
    
    
 | 
| 5682.3 |  | METSYS::GOODWIN | Pete Goodwin, DEC/EDI Engineering | Wed Feb 12 1997 06:25 | 10 | 
|  |     It's been running UNIX V4.0 - I thought I could add another disk and
    build an NT system on it. When I ran ARCINST it trashed device 0 which
    was the UNIX boot disk!
    
    I did run the ECU V1.5 for Windows NT but it made no difference.
    
    What revision of the firmware should it be - and where do I find this
    information?
    
    Pete
 | 
| 5682.4 |  | 2954::FOLEY | http://axel.zko.dec.com | Wed Feb 12 1997 07:48 | 5 | 
|  | 
	Start with http://www.windows.digital.com/support/driver.htp
							mike
 | 
| 5682.5 |  | MPOS01::naiad.mpo.dec.com::mpos01::cerling | I'[email protected] | Wed Feb 12 1997 07:56 | 10 | 
|  | 
	You are way out of date with your ECU.  As .-1 says, look for the
	latest stuff.  Current ECU is 1.9, I believe.  1.5 is about 3 years
	old.
	The only way I could see see ARCINST trashing anything is that you
	told it to.  It doesn't do anything without first asking what is
	to be done.
tgc
 | 
| 5682.6 |  | METSYS::GOODWIN | Pete Goodwin, DEC/EDI Engineering | Wed Feb 12 1997 08:30 | 12 | 
|  |     ARCINST didn't ask me which disk to use - I had five disks installed at
    the time and it zapped disk 0. I wasn't asked which drive to use at any
    point.
    
    The ARC firmware announces itself as V3.50 - sounds like I need to
    upgrade to V4.50.
    
    I'd like to keep the UNIX disks in this time - drives 0, 1, 2 and 3 and
    the NT disk to be 4 - can I install like this? I found the only way to
    run ARCINST was to remove all disks and make the NT disk drive 0.
    
    Pete
 | 
| 5682.7 |  | 2954::FOLEY | http://axel.zko.dec.com | Wed Feb 12 1997 09:01 | 8 | 
|  | 
	You want to remove all the disks anyways for the installation.
	Just to be on the safe side. Remember when you get it installed
	and run the Disk Administrator, it's going to ask you if
	it can write on the disk. Just say No.
							mike
 | 
| 5682.8 |  | MPOS01::naiad.mpo.dec.com::mpos01::cerling | I'[email protected] | Wed Feb 12 1997 14:00 | 11 | 
|  | 
	Not only will you want to remove the disks for installation; you will
	have to remove the disks for installation.  The install crashes if
	it finds unformatted disks.
	re: ARCINST zapping disk 0.  Interesting... Every time I have run
	ARCINST it made me chose which disk I wanted to work on and then how
	to partition it.  Maybe it zapped it because you hadn't run the
	proper ECU?  Just a guess...
tgc
 | 
| 5682.9 | Standalone RAID software no longer works! | METSYS::GOODWIN | Pete Goodwin, DEC/EDI Engineering | Thu Feb 13 1997 00:55 | 22 | 
|  |     I successfully upgraded the firmware to V4.50, everything seemed fine.
    
    I took out the disks, put in the NT disk and it reported a read error
    on device 0 (correct - I took the disk out!).
    
    I tried to run the MYLEX RAID software: 'This version of the ARC
    firmware is not supported'.
    
    *GROAN*
    
    The version I have is V1.0, where do I find a version that works with
    ARC V4.50?
    
    I found the ECU V1.9 software but it has no instructions, just a zip
    file. The contents are just CFG files, no EXE etc. What do I do with
    it? Put it on a floppy and hope for the best?
    
    WHY IS THIS SO HARD TO DO???
    
    Getting fed up,
    
    Pete
 | 
| 5682.10 |  | METSYS::GOODWIN | Pete Goodwin, DEC/EDI Engineering | Thu Feb 13 1997 04:53 | 4 | 
|  |     OK, found a V3.2 RAID standalone disk and fixed the disks - however the
    'setup error 4' is still there.
    
    Pete
 | 
| 5682.11 |  | CSC32::K_MEADOWS |  | Thu Feb 13 1997 06:35 | 6 | 
|  |     of course you do need the .exe for the ECU.  If you pulled the zip file
    from the EXTERNAL website it only has the cfg files.  Check out the 
    ntsg site (ntnone.zso.dec.com) - I've heard that the .exe is there.
    (I haven't been able to connect to it all week so I cannot confirm.)
    
    km
 | 
| 5682.12 |  | METSYS::GOODWIN | Pete Goodwin | Sat Feb 15 1997 08:29 | 9 | 
|  |     Well, I solved my problem - I went to a different machine, one without
    a raid controller. Everything worked fine this time, ARCINST correctly
    listed the drives available for formatting (unlike it did on the 2100)
    and NT installed and is working fine.
    
    The only bizarre thing is this alpha reports a 'boot settings' error
    which doesn't appear to cause any problems at all!
    
    Pete
 | 
| 5682.13 | Other boot entries? | GIDDAY::cscds704.stl.dec.com::Harkness |  | Sun Mar 09 1997 02:56 | 17 | 
|  | Pete,
You can most likely get rid of your final problem by deleting the 
other boot options that would have been created by you other attempts 
at installs.
This will give you an error, but will not hampre the operation of the 
machine....
You also have the option of being able to check and dump the entries. 
If you are not too confident at doing this, make sure that you write 
the entries down before doing any deletions.
Good luck,
Greg Harkness
Sydney CSC
 |