From: x27@sun0.urz.uni-heidelberg.de (T. Voelkering)
Subject: My NT nightmare
Organization: University of Heidelberg (Germany)
Date: Mon, 14 Dec 92 16:45:14 GMT

Hello out there

Here are my M$-Win eNTe adventures:

Some days ago I got the CD and decided to try it as just had a 
second 300MB virgin SCSI drive connected to my 1542. So why shouldn't I
give it a chance. On the first disk I had DOS and two HPFS partitions
and wanted to install the eNTe to the second disk as I did it some
times before with OS/2. Yes I have seen the hint that it would no 
coexist with the OS/2 bootmanager. But till than I thought that the second
drive could do it in any way.
Ok. I did begin the installation process...
It crashed (what else should I have expected)
But than:
   I was unable to boot from Harddisk!
	Tried FDISK from OS/2 and DOS to activate several partitions, re-
	install the Bootmgr - no go.
   No data was lost - only no boot from Harddisk.
   I remembered, that I had heared of an undocumented switch for dos-fdisk
   to write a new master boot record but did not remember what it was. So
   I took xtg to search fdisk.exe for something like that: fdisk /mbr 
   did it for me.

OK. My pc was ready for the next try:
   I removed my first HD and jumpered the second one for id0.
   Installed eNTe.
   (how great are Installation processes with an CD-rom: You answer 
    1000 questions and go to drink some coffees. After 45 minutes 
    everything is up and running.  --- M$ seems to have an other 
    understanding of that: Answer some questions, wait 4-7 minutes, answer
    some questions, wait ......
   )
   No Problem. I stayed at the computer and selected 8514 -- oh sorry - 
   not available (Its an IBM Standard) selected et4000, 1024x768x256 --
   oh sorry - not available - selected 1024x768x16.
   I selected NTFS ( the manual said: after a system crash the recovery
   of the filesystem will take only seconds but not minutes - sounds good)
   Then the system came up
   the eNTe - beta - hello screen.
   Press CTRL-ALT-DEL to log in
   Type name
   BEEP - Parity check ........................
   
   Reboot
   .....   The system detected an error with file xxxx.xxx
           Please boot whith repair disk
   No Problem (As I read, it will take only seconds. Never seen that 
               BS with the Floppy at OS/2 after a sys-crash, but why not )
   Boot-disk
   repair disk
              "This will take a longer while"
   Only 45 MINUTES later:
     The repair process reached the defective file and ....

                  CRASH

   Reboot
   .....   The system detected an error with file xxxx.xxx
           Please boot whith repair disk

     NO !!! NOT again.

I decided to reinstall
   Boot disk
   Where do you want to install: c:\winnt ?
   Yes
   NO!! There is already an eNTe ! Use an other directory
   c:\winnt2
   OK
   Installation (with standard VGA)
   
   IT WORKED.
		Only 73 MB used for the system on the drive !!!!
   
   After one or two minutes playing around with the system, I decided, tha
   VGA is BS and wanted et4000 again
   Setup
     et4000, 1024x768x16
   reboot
   BEEP - Parity check ...............
   reboot
 .....   The system detected an error with file xxxx.xxx
           Please boot whith repair disk

That was it for me. I reinstalled my other HD and used OS/2 FDISK to
set an end to that nightmare.
Now I have a LINUX on the disk and boot it with the bootmgr. It has
has no problems with coexisting with OS/2. 

Thomas



-- 


==========================================================================
	Thomas Voelkering	email:	x27@indigo0.urz.uni-heidelberg.de
Newsgroups: comp.os.os2.misc