LVM and WinXP

Hello All;
	Does anyone know if it is possible to install WinXP and eCS2.0 beta 2,
and if so how?
	I am trying to install WinXP and eCS on a ASUSA8V, with an AMD Athlon
64 X2 4200, 1G of Dual Channel DDR, a Saphire ATI 256MB AGP video card
and a Seagate 300G drive. Win2000 Pro does not recognize the correct
drive size and will not install in any partition created by DFSee v 8.03
or the LVM. If I let Win2000 create the partitions and then try and
install eCS, LVM reports a corrupted MBR and cannot continue until the
Win2000 partitions are deleted. It looks like the only way I can get
Win2000 and eCS v2.0 beta 2 is to add another smaller hard drive and
install Win2000 to that drive.
	If I can install WinXP and eCS on the same large hard drive, how do I
go about it? What do I install 1st? What should I use to create the
partitions, DFSee, LVM or MS FDISK?
	I have tried using DFSee but could be using it wrong. When I create the
Bootmanager its size is 2.5MB but the LVM version wants 8MB and when I
try to set up a partition to install eCS to I get the corrupted MBR error.
	If I use LVM to set up the partitions and install bootmanager, WinXp
will install, but after I install eCS and make the BootManager
startable, eCS starts 'OK' but WinXP starts up and gets to the green bar
and then reboots. eCS 2.0 will boot fine at this point.
Any suggestion or pointers would be greatly appreciated.

Alex Taylor wrote:
> On Wed, 12 Jul 2006 16:37:28 UTC, Keith Marjerison
<k.marjerisonstopspam@sasktel.net> 
> wrote:
> 
>> 	If I use LVM to set up the partitions and install bootmanager, WinXp
>> will install, but after I install eCS and make the BootManager
>> startable, eCS starts 'OK' but WinXP starts up and gets to the green
bar
>> and then reboots. eCS 2.0 will boot fine at this point.
> 
> Sounds like it might be related to the BOOT.INI issue in Windows.  DFSee
> has a fix for that too, I belive.
> 
Hello All;
	By god I think I've got it. I'm not real sure that DFSee fixed it or I
just payed more attention to what I was doing. I still have to power
right off and then cold boot WinXP to get it up and running. I think it
might be a BIOS problem. The bios reports my Seagate drive as a 25.6G
but both eCS 2.0 and WinXP see 288166 MB. If I boot DFSee with option
'1' it reports a drive with 7 25G partitions even though none have been
set. If I power the machine off and boot to the DFSee disk with the '2'
option it sees the same as eCS or WinXP.
	I used LVM to add the BootManager to the drive and then a 20G partition
for WinXP. I then removed the BootManager and rebooted and installed
WinXP. I rebooted using the eCS v2.0 beta 2 CD and used LVM to
re-install the BootManager and another primary partition for eCS v2.0
and 3 logical partitions, one of which was a compatibility volume for
WinXP. I then used DFSee to fix the W2K problem and rebooted to WinXP.
It was at this point that I discovered a cold boot would start WinXP.
	I can live with an occasional cold boot every now and then. It looks
like ASUS has several good BIOS update options, but I will have to
install a 3.5" floppy drive to use the safest method.
	On another note, should I update the BIOS before adding SMP support or
after?
	Just to let all who are interested know, the ASUS A8V installed right
out of the box in eCS 2.0 beta 2. I did forget that you have to use the
'Advanced' option to get Networking installed and had to reinstall. The
Uniaud drivers recognized the ALC850 audio and I had downloaded the
Yukon Gigabit driver from Hobbes and installed the drivers when prompted
in the Networking install portion. I can access the internet and my
small network. I am a happy camper, for now. Like I said, I plan to
purchase SMP support and use the eCSMT to install it. Any comments on
the best procedure for doing this would be greatly appreciated.

On Wed, 12 Jul 2006 16:37:28 UTC, Keith Marjerison
<k.marjerisonstopspam@sasktel.net> 
wrote:

> 	If I use LVM to set up the partitions and install bootmanager, WinXp
> will install, but after I install eCS and make the BootManager
> startable, eCS starts 'OK' but WinXP starts up and gets to the green bar
> and then reboots. eCS 2.0 will boot fine at this point.

Sounds like it might be related to the BOOT.INI issue in Windows.  DFSee
has a fix for that too, I belive.

-- 
Alex Taylor                                        
http://www.cs-club.org/~alex

Servus Keith!

KM> From: Keith Marjerison <k.marjerisonstopspam@sasktel.net>

KM> Hello All;
KM>     Does anyone know if it is possible to install WinXP and eCS2.0 beta 
KM> 2, and if so how?

First of all, wipe out the whole harddisk! You can use LVM (CD or Floppy boot)
but you will need more than one boot (delete all partitions, than REBOOT and
repeat these steps, till LVM shows an empty harddisk and useable disk capacity.

Second, if LVM shows empty disk, install BOOTMANAGER at the beginning of the
harddisk.

Third, create (physical view) at least the following partions:

Primary, C: as tiny as possible and format with FAT16. This is for the Win??
bootloader (NTLOADER) and the partition should be startable in BOOTMANAGER
menu.
Secondary partition, with - at least - the following two logical drives:

D: should not exceed 8GB barrier, for OS/2 or eCs :-), HPFS, starable in
BOOTMANAGER. 

E: as large as you want it, do not format under OS/2, install Win?? and use
this as the installation partition. Format it with FAT32 (up to 32GB) or NTFS.

After installing Win??, the BOOTMANAGER is inaccessable, C: would be the active
partition. Under Win??, ComputerAdministration-HarddiskMaintainance (or
similar), you could make BOOTMANAGER make active again.

And after all this is done, install eCs or OS/2 on D:

NEVER use other tools than LVM and use only 'virgin' harddisk.

At all FORMAT actions, use LONG (/L) format, to erase all old data. 

Herzliche Gruesse, Harald

Hi Keith,

On Wed, 12 Jul 2006 23:50:53 UTC, Keith Marjerison
<k.marjerisonstopspam@sasktel.net> wrote:

>         By god I think I've got it. I'm not real sure that DFSee fixed it
or I
> just payed more attention to what I was doing. 

:-)

>I still have to power  right off and then cold boot WinXP to get it 
>up and running. I think it.  might be a BIOS problem. 

I have seen that mentioned several times with the eCS 2.0 beta 
on some motherboards. It may be related to the DANIS506
release used. The problem seems to be that eCS (DANI ?) leaves 
the disk-controller in a state that Windows does not like.
A power-off (cold- boot) resets all hardware so bypasses the problem ...

You could try the latest DANIS506 to seen if that makes a difference. 

>The bios reports my Seagate drive as a 25.6G
> but both eCS 2.0 and WinXP see 288166 MB. 

The BIOS seems to report a 'modulo 32 GiB' value.
Mif=ght be different after a cold boot though ...

>If I boot DFSee with option '1' it reports a drive with 7 25G 
>partitions even though none have been set

That is the (FreeDOS) version with the ultra-DMA driver loaded.

> set. If I power the machine off and boot to the DFSee disk with the '2'
> option it sees the same as eCS or WinXP.

That is using the motherboad BIOS ...

The other (OS2 or Windows) version of DFSee would show
whatever LVM or the Windows disk-manager would show too.
This behaviour depends more on the OS than DFSee :-)

>         I used LVM to add the BootManager to the drive and then a 20G
partition
> for WinXP. I then removed the BootManager and rebooted and installed
> WinXP. I rebooted using the eCS v2.0 beta 2 CD and used LVM to
> re-install the BootManager and another primary partition for eCS v2.0
> and 3 logical partitions, one of which was a compatibility volume for
> WinXP. I then used DFSee to fix the W2K problem and rebooted to WinXP.

OK, good.

> It was at this point that I discovered a cold boot would start WinXP.
>         I can live with an occasional cold boot every now and then. > 

Sure, as said, you may want to check for a DANI update ...

Regards, JvW

--