Windows 7 error 0xc000000e

[A.D. Fundum]

What's required to have both Windows 7 and eCS 1.2 working with the
OS/2 bootmanager?

W7 installed first (worked), primary partition of 50 GB. Next the BM
was installed with several additional OS/2 partitions (1 primary), in
total 30 GB.

The best result so far is a working eCS 1.2 and W7 with error
0xc000000e. It's a solvable error by rebuilding some BCD store ith
W7's CMD.EXE, but then eCS is gone again. Of course Microsoft-based
solutions seem to be aimed at starting just W7 again, but not at
supporting another OS.


--

[James J. Weinkam]

Post by A.D. Fundum
What's required to have both Windows 7 and eCS 1.2 working with the
OS/2 bootmanager?
W7 installed first (worked), primary partition of 50 GB. Next the BM
was installed with several additional OS/2 partitions (1 primary), in
total 30 GB.
The best result so far is a working eCS 1.2 and W7 with error
0xc000000e. It's a solvable error by rebuilding some BCD store ith
W7's CMD.EXE, but then eCS is gone again. Of course Microsoft-based
solutions seem to be aimed at starting just W7 again, but not at
supporting another OS.
--

This sounds like the error that occurs if the partition number of the windows partition has changed. If this is your
problem you can fix it with DFSee:

File->Open object to work with->Partition (select windows partition)
Mode->Boot area fixes->Fix BOOT.INI partition index.

[A.D. Fundum]

Post by James J. Weinkam
This sounds like the error that occurs if the partition number
of the windows partition has changed. If this is your

Partition numbers aren't changed intentionally, I tried this anyway,
it couldn't find a BOOT.INI. After this operation the best result so
far is still matched, which is a working eCS 1.2 and OS/2 bootmanager,
and Windows 7 with a repeating cycle of error 0xc000000e and a Windows
7 bootmanager.

FTR:

1. Pre-installed XP installed again, wiping the 80 GB harddisk
2. Shrinked XP to 50 GB, first primary partition
3. So-called upgrade of XP to 7

4. OS/2 bootmanager installed, second primary partition
5. eCS 1.2 installed, C: of 2 GB as third and final primary partition
6. Also created D: (2 GB) and E: (~20 GB) partitions
7. Booting 7 with the OS/2 bootmanager results in boot error
0xc0000005

8. I can switch between a working eCS and 7 with a repair and/or a
boot CD/DVD, but it's XOR.

Hardware: "old". I've read the struggles with 7 @ Hobbes, but I'm
using a smaller IDE harddisk and my 7 wasn't pre-installed. A command
related to 7's BSD (sp?) didn't work, IIRC. Apparantly the M$ boot
method has changed since Vista, installing XP with steps 1-6 should
work.


--

[Shmuel (Seymour J.) Metz]

Post by A.D. Fundum
5. eCS 1.2 installed, C: of 2 GB as third and final primary partition

Why not a logical drive?

[Barry Landy]

On Mon, 10 Jun 2013, Shmuel (Seymour J.) Metz wrote:

:>In <o8uYFJ3iqTdG-pn2-***@localhost>, on 06/09/2013
:> at 01:18 PM, "A.D. Fundum" <***@neverm.ind> said:
:>
:>>5. eCS 1.2 installed, C: of 2 GB as third and final primary partition
:>
:>Why not a logical drive?
:>
:>

It is quite a long time back but when I experimented with Win7 I did it
on top of an existing installation with winxp and ECS (multiple!)

I had (still have) a primary C: Partition for windows to boot from
(boot.ini style), Winxp in a logical partition (E:), a second primary on
drive 2 (D:) for data shared between windows and ECS (this was once
upon a time also my maintenance boot but no longer); ECS in logicals.

So I did the natural thing: used DFSEE to allocate a large logical and
did the win7 install to there. That did work. I have not tried it since
(~18 months) as I had problems accommodating my working style to Win7
and so I am still using WinXP (and no longer have Win7 on the system)

[A.D. Fundum]

Post by Barry Landy
So I did the natural thing: used DFSEE to allocate a large logical and
did the win7 install to there. That did work.

I don't think creating a new logical partition with a W7 SP1 upgrade
is an option. The upgraded XP is a full version, but occupies the
whole harddisk. Creating a new partition means that the upgrade won't
find XP or a W7 install, so the upgrade cannot be installed. I have to
overwrite XP or W7.

Post by Barry Landy
I have not tried it since (~18 months) as I had problems accommodating
my working style to Win7 and so I am still using WinXP (and no longer
have Win7 on the system)

The "favorite" XP could remain in use here too, but the end-of-service
date may be the 8th of april 2014 and I had to buy versions which
still support my hardware. Preparing wasn't a bad idea in my case,
albeit I hardly use it. One of the hidden nasties was this fatal boot
error. I don't know if W8 will have the same problem, since I'm
waiting for an eCS 2.x NLS version for that system.


--

[A.D. Fundum]

Post by Shmuel (Seymour J.) Metz

Post by A.D. Fundum
5. eCS 1.2 installed, C: of 2 GB as third and final primary

partition

Post by Shmuel (Seymour J.) Metz
Why not a logical drive?

BTW, is there a message hidden in this question? So far everybody
seems to assume that a primary partition should work (too), but maybe
your message is that it won't work.


--

[Shmuel (Seymour J.) Metz]

Post by A.D. Fundum
BTW, is there a message hidden in this question?

"Why are you using a scarce resource?"

It's harder to run out of logical drives than to use up all four
primary partitions.

[ivan]

On Fri, 14 Jun 2013 19:06:57 UTC, Shmuel (Seymour J.) Metz

Post by Shmuel (Seymour J.) Metz

Post by A.D. Fundum
BTW, is there a message hidden in this question?

"Why are you using a scarce resource?"
It's harder to run out of logical drives than to use up all four
primary partitions.

You are totally missing the point here. A full win7 install dvd will
install win 7 to TWO primary partitions one is C: the other is hidden
unless there is only one primary left for it to install to.

It is these two partitions being required for win 7 to boot that
prevents BM from doing so.

To have a multi OS system where you select which OS to boot with a BM
requires that win 7 be confined to a single primary partition.

ivan
--

[A.D. Fundum]

Post by ivan

Post by Shmuel (Seymour J.) Metz
It's harder to run out of logical drives than to use up all four
primary partitions.

To have a multi OS system where you select which OS to boot with a
BM requires that win 7 be confined to a single primary partition.

That's "the" (OS/2) BM. My upgrade from XP to W7 is confined to XP's
former single partition, so "the" OS2 BM should work.

If W7 uses more than one primary partition, you'll have to use e.g.
AiRboot. The OS/2 BM hides all other partitions, including W7's second
primary partition, but AiRboot shouldn't do that. So "a" BM may work
in such a situation, but "the" OS/2 BM won't work.

So far no progress, and no informal Microsoft solution via their
"support" forum.


--

[Shmuel (Seymour J.) Metz]

Post by ivan
You are totally missing the point here. A full win7 install dvd will
install win 7 to TWO primary partitions one is C: the other is
hidden unless there is only one primary left for it to install to.

That's obscene. Is there a rational reason?

[ivan]

On Sun, 16 Jun 2013 02:36:24 UTC, Shmuel (Seymour J.) Metz

Post by Shmuel (Seymour J.) Metz

Post by ivan
You are totally missing the point here. A full win7 install dvd will
install win 7 to TWO primary partitions one is C: the other is
hidden unless there is only one primary left for it to install to.

That's obscene. Is there a rational reason?

None that I have been able to find other than an attempt at DRM - it
is Microsoft after all.

ivan
--

[Trevor Hemsley]

On Sun, 16 Jun 2013 02:36:24 UTC in comp.os.os2.ecomstation, Shmuel (Seymour J.)

Post by Shmuel (Seymour J.) Metz

Post by ivan
You are totally missing the point here. A full win7 install dvd will
install win 7 to TWO primary partitions one is C: the other is
hidden unless there is only one primary left for it to install to.

That's obscene. Is there a rational reason?

It uses a small, 100MB, primary partition that it sites within the first 1024
cylinders of the disk in the same way that OS/2's boot manager and Linux's /boot
are located there - so that the BIOS can boot them even if the machine does not
support booting from elsewhere on the disk. Its other partition can then be
located anywhere, even on other disks I believe.

[A.D. Fundum]

Post by Trevor Hemsley
It uses a small, 100MB, primary partition that it sites within the

first

Post by Trevor Hemsley
1024 cylinders of the disk

No, it doesn't. At least not if "it" is W7 (SP1). I installed it in my
former XP partition of 50 GB, the first physical partition. During the
"upgrade", there wasn't any error, message nor warning related to such
a W7 setup with a second W7 partition. During the most recent attempt
I selected this 50 GB partition and formatted it, so the installer
could create partitions at will. Even a 4th primary. But it just used
the former XP partition.

I haven't tried creating 2 partitions myself. XP occupies the whole
harddisk again (and full a re-install of eCS takes about long 2 days).
and the "upgrade" license requires an older version of Windows or W7
itself to be installed.

So far no answer at all from the Microsoft support forum community.
The underlying problem may be related to not having a second W7
partition indeed. Stand-alone it works, the only harddisk volume then
is C: (the only other volume or drive is the DVD drive, D:). That's
right and expected.

BTW, the Microsoft upgrade advisor, or whatever it's called, isn't
always reliable. IIRC it cliamed that W8 would work with an IBM
ThinkPad T42p. But W8 fails, stating that "the computer has to be
repaired". CPU too old, I'ld say. W7-32 will work on such a machine
with enough memory. The upgrade advisor tells you to visit Intel to
find a driver for its Intel 2200BG WLAN device. Intel will tell you
that there's no such driver, the product is no longer sold. Never
mind: it should work out-of-the-box, probably with a Vista or XP
driver. At least a ThinkPad T60p is capable of running W8. In a way W8
= W7 + commercial Microsoft tiles (Bing, Xbox, Live, SkyDrive,
providing personal information to Microsoft and partners) + certainly
not "Everything at once" + silly GUI to make your 30" monitor work
like a 2.5" mobile phone + the usual harddisk torture - no more
rounded corners - no more transparancy. I don't have a combination of
W8 and eCS yet, so I don't know if it will have the same fatal boot
error, but that;'s likely because Vista, W7 and W8 no longer use XP's
BOOT.INI technique. And yes, I do like to call Windows 8 "W8": W acht
-> Wacht -> Wait. Or Weight, that'll do too.


--

[A.D. Fundum]

Post by Shmuel (Seymour J.) Metz
"Why are you using a scarce resource?"

It's isn't, albeit it can be a scarce resource.

Post by Shmuel (Seymour J.) Metz
It's harder to run out of logical drives than to use up all
four primary partitions.

Something to remember, but this theory ignores another limitation in
an earlier stage: my harddisk is fully used, and the maximum number of
primary partitions I could ever use is 4. Any change to that situation
always requires harddisk repartitioning anyway, and I'm pretty sure a
traditional primary partition works in all situations.


--

[Peter Flass]

Post by A.D. Fundum

Post by Shmuel (Seymour J.) Metz

Post by A.D. Fundum
5. eCS 1.2 installed, C: of 2 GB as third and final primary

partition

Post by Shmuel (Seymour J.) Metz
Why not a logical drive?

BTW, is there a message hidden in this question? So far everybody
seems to assume that a primary partition should work (too), but maybe
your message is that it won't work.

This also begs another question - would running both Win7 and Warp as
VMs under a hypervisor simplify the system?

[ivan]

Post by Peter Flass

Post by A.D. Fundum

Post by Shmuel (Seymour J.) Metz

Post by A.D. Fundum
5. eCS 1.2 installed, C: of 2 GB as third and final primary

partition

Post by Shmuel (Seymour J.) Metz
Why not a logical drive?

BTW, is there a message hidden in this question? So far everybody
seems to assume that a primary partition should work (too), but maybe
your message is that it won't work.

This also begs another question - would running both Win7 and Warp as
VMs under a hypervisor simplify the system?

Peter that would depend on the type of hypervisor you are thinking
about.

Bare metal hypervisors (ESXi as an example) are usually run on
servers.

With Hosted hypervisors a lot depends on what you want for the host
system.

I don't recommend using the implementation of VirtualBox we have for
OS/2 (eCS) to run win 7. Unless someone has found a way of getting
the additions to run the mouse pointer has a tendency to jump all over
the place at the most inopportune times.

What is left? Using linux as host is fine, if you want to learn
linux, not everyone does.


ivan
--

[A.D. Fundum]

Post by James J. Weinkam
File->Open object to work with->Partition (select windows partition)
Mode->Boot area fixes->Fix BOOT.INI partition index.

Apparently BOOT.INI is XP. With Vista/7/8 it's replaced with EDLIN
2.0, a REGEDIT-like idea:

http://msdn.microsoft.com/en-us/windows/hardware/gg487520.aspx

"On BIOS-based computers that are running only Windows Vista, the
Boot.ini text file is gone (not hidden) and any remnants of it on
interim beta test builds are ignored."

I know as such it's off-topic, but more eCS users may face this
problem when they have to replace XP with e.g. W7.


--

[Allan]

Post by A.D. Fundum

Post by James J. Weinkam
File->Open object to work with->Partition (select windows partition)
Mode->Boot area fixes->Fix BOOT.INI partition index.

Apparently BOOT.INI is XP. With Vista/7/8 it's replaced with EDLIN

Search for EasyBCD - a free GUI app for Win, that handles the Win7 boot manager.

[A.D. Fundum]

Post by Allan
Search for EasyBCD - a free GUI app for Win, that handles the Win7 boot manager.

I've dumped the working (W7 works, BM/eCS' partition no longer set to
active) settings with it after installing W7 as the last OS, but
EasyBCD won't work when the boot error occurs.

In case of this boot error, repairing the BCD automatically with a W7
boot DVD won't work because "chkdsk" doesn't work (error 0x1f, IIRC).
It may be referring to the BM, I don't know. The only working option
is to go to the prompt. Suggested BCDEDIT commands won't work. I can
go to W7's C: and try to start this EasyBCD, but that fails with an
error 0xc0000135.

Maybe somebody with a working W7+BM+eCS can list the EasyBCD
(debug/detailed) settings? My original EasyBCD setting were,
abbreviated, right after installing W7:

Windows Boot Manager
--------------------
iden {GUID1}
devi partition=C:
desc Windows Boot Manager
loca nl-NL
inhe {GUID2}
defa {GUID3}
resu {GUID4}
disp {GUID3}
tool {GUID5}
time 30

Windows Boot Loader
-------------------
iden {GUID3}
devi partition=C:
path \Windows\system32\winload.exe
desc Windows 7
loca nl-NL
inhe {GUID6}
reco {GUID7}
reco Yes
osde partition=C:
syst \Windows
resu {GUID4}
nx OptIn


I don't know if that's right (assuming BM+eCS+w7), and I don't know
what the current settings (BM active, W7 boot error 0xc000000e, e.g.
"BCDEDIT /enum ALL" doesn't work) are.


--

[Norbert Dragon]

Post by A.D. Fundum
What's required to have both Windows 7 and eCS 1.2 working with the
OS/2 bootmanager?

Playing around with DFsee

http://www.dfsee.com/dfsee/

and my IBM X41-tablet with Windows 7, OS/2 and Debian Linux (squeeze)
I finally succeeded to boot each of them with the IBM bootmanager.

I had installed OS/2, partitioned the hard disk with the Logical Volume
Manager and DFsee such that the first primary partition starts at
CHS = 0-32-33, because earlier attempts had shown that Windows 7
chooses this offset and repartitions it if the primary partition starts
earlier.

It is advisable to use a second primary partition for an additional
operating system and the third for the IBM bootmanager. The additional
partitions are logical partitions in an extended partition, which by
construction is then the fourth primary partition. This prevents
Windows from creating an additional primary partition for its system
files, because a disk can have 4 primary partitions at most. A second
primary partition for Windows 7 would prevent it to boot with the IBM
bootmanager, as during boot the bootmanger hides all but the chosen
partition. This I learned from Jan van Wijk, the author of DFSee.

Next I created a bootable USB-stick with DFsee and FreeDos
to have access to the partition tables no matter which operation
system is installed and operative at the harddisk.

With DFsee I made a backup of the partition tables created under OS/2.

Then I installed Debian Linux (squeeze) and forced its bootmanger grub2
not only to install itself in the masterboot record (which one cannot
prevent during installation) but also in the bootrecord of its own
partition (sda6)

update-grub

grub-install /dev/sda6 --force (replace sda6 as appropriate)

Then I restored with DFsee the OS/2 partition tables with exception of
the partition boot records. This enabled dual boot of OS/2 or Debian
Linux with the IBM bootmanager who hands over to grub2.

It is not sufficient, to restore the first block (512 Byte)
of the masterboot record, as widespread recipes suggest. Grub2 changes
also the extended boot record and makes it unreadable for OS/2 LVM.

I used Linux to format partition 1 (sda1) with NTFS

mkfs.ntfs /dev/sda1

and included the Windows partition in the IBM bootmanger menu.

The Windows 7 installation accepted the partition 1 for installation
without any change and even proceeded without formatting it anew. It did
not create an additional partition (which it had done previously when
another primary partition was possible, because there were only three.)

Of course, Windows changed the partition tables such that the IBM
bootmanager did no longer take over at boot time.

But with the bootable USB-stick and and DFsee one can repair this. It
is not sufficient to set the startable flag with e.g. Knoppix to the
Bootmanager partition. The bootmanger does not start with the
bootrecord written by Windows.

Also one cannot just restore the OS/2 partition boot records, as then
Windows complains at bootup about a device which it cannot find, asks
to be repaired and after some minutes reports that the attempt to
repair failed.

To repair the boot record one has to execute in the DFsee menu

FDISK, OS/2 LVM and Bootmanger, BMGR W2K CHS and I13X fix

and

FDISK, Part-table cleanup repair, Cleanup partition table

and reboot via

File, Boot using IBM bootmanger, Windows

Of course, one has to remove the USB-stick before reboot.

Windows started with no trace of the bootmanger, but on the next
reboot the IBM bootmanger took over and allows now to boot
Windows 7 or OS/2 or Debian Linux.

Under Linux

update-grub

will find Windows 7 and enable to chainboot Windows if one boots
Linux with the IBM bootmanger. But if Windows 7 is installed in only
one partition this chainboot is not required.

Finally I made a backup of the partition tables of the working triple
boot installation.

[Peter Brown]

Hi

Post by A.D. Fundum
What's required to have both Windows 7 and eCS 1.2 working with the
OS/2 bootmanager?
W7 installed first (worked), primary partition of 50 GB. Next the BM
was installed with several additional OS/2 partitions (1 primary), in
total 30 GB.
The best result so far is a working eCS 1.2 and W7 with error
0xc000000e. It's a solvable error by rebuilding some BCD store ith
W7's CMD.EXE, but then eCS is gone again. Of course Microsoft-based
solutions seem to be aimed at starting just W7 again, but not at
supporting another OS.
--

Maybe AirBoot will work better than BootManager -
http://svn.netlabs.org/air-boot


Regards

Pete

[A.D. Fundum]

Post by Peter Brown
Maybe AirBoot will work better than BootManager -
http://svn.netlabs.org/air-boot

I don't think the BM is the problem. Descriptions ("taming W7") at
Hobbes show IBM's was used. Nevertheless I just tried 1.07, with the
same error. Besides that, W7 boots good enough to display the fatal
error message.

There's an EDLIN-beating W7 program, BCDEDIT. Which, of course,
doesn't work. At least not the very first commands a MBR BM-aware
website suggested. EasyBCD, which cannot be used in case of the error,
learns that W7's "device partition=C:" may be the cause. After all W7
boots, and the 0xc000000e error message description does mention that
a "device" cannot be found. So it may be a setting related to BCDEDIT
and related programs, essentially the same type of crap as WinOS/2's
INI files, but with a fine BCDEDIT interface. With XP it was a text
file (BOOT.INI), but since Vista that won't work with a BIOS-based
system.

Repairing the BCD data with the install DVD doesn't work because
"chkdsk" doesn't work, so something may be pointing to the BM
partition instead of the W7 C: disk. Nevertheless a "dir c:" displays
the data of W7's C: drive. I just tried installing W7 as the last OS,
but that didn't help at all. It's not aware of the BM, as usual it's
just disabled or deactived.

I do fear BCDEDIT is the key to some acceptable solution, but I may be
wrong.

The other, quite annoying solution is to use e.g. an eCS, GParted and
or DFSee CD to set the right partition as being active and/or not
hidden and/or to reinstall the IBM BM. Both OSes will keep working,
but you can only boot eCS (BM) XOR W7 (disabled BM), and using the CD
each time is a PITA.

FTR: I was just trying to "upgrade" XP to W7 (W8 didn't work on this
IBM ThinkPad T42p, claiming that it needed to be repaired), because
it's likely that a XP without updates will attract more fatal
time-waisting viruses as of (april?) 2014. I only use it when I'm
technically forced to use it, and using XP isn't an option because a
forced reinstall of XP OEM wipes out my main OS, eCS. The problem may
affect more users in the future, my situation should be quite typical.



--

[Norbert Dragon]

Post by A.D. Fundum
What's required to have both Windows 7 and eCS 1.2 working with the
OS/2 bootmanager?

The partition records of Windows 7 cannot be read by eCS 1.2
and the eCS bootmanager cannot boot a system which uses 2 partitions
at boottime -- as Windows 7 prefers to do.

Here is my recipe, to boot Windows 7, OS/2 and Debian Linux, using

http://www.dfsee.com/dfsee/

I had installed OS/2, partitioned the hard disk with the Logical Volume
Manager and DFsee such that the first primary partition starts at
CHS = 0-32-33, because earlier attempts had shown that Windows 7
chooses this offset and repartitions it if the primary partition starts
earlier.

It is advisable to use a second primary partition for an additional
operating system and the third for the IBM bootmanager. The additional
partitions are logical partitions in an extended partition, which by
construction is then the fourth primary partition. This prevents
Windows from creating an additional primary partition for its system
files, because a disk can have 4 primary partitions at most.
(If one hasnt used up enough partitions, then Windows 7 creates two
partitions partitions without asking, one partition of about 100 MB for
system files:) A second primary partition for Windows 7 prevent s
it to boot with the IBM bootmanager, as during boot the bootmanger
hides all but the chosen partition. This I learned from Jan van Wijk,
the author of DFSee.

Next I created a bootable USB-stick with DFsee and FreeDos
to have access to the partition tables no matter which operation
system is installed and operative at the harddisk.

With DFsee I made a backup of the partition tables created under OS/2.

Then I installed Debian Linux (squeeze) and forced its bootmanger grub2
not only to install itself in the masterboot record (which one cannot
prevent during installation) but also in the bootrecord of its own
partition (sda6)

update-grub

grub-install /dev/sda6 --force (replace sda6 as appropriate)

Then I restored with DFsee the OS/2 partition tables with exception of
the partition boot records. This enabled dual boot of OS/2 or Debian
Linux with the IBM bootmanager who hands over to grub2.

It is not sufficient, to restore the first block (512 Byte)
of the masterboot record, as widespread recipes suggest. Grub2 changes
also the extended boot record and makes it unreadable for OS/2 LVM.

I used Linux to format partition 1 (sda1) with NTFS

mkfs.ntfs /dev/sda1

and included the Windows partition in the IBM bootmanger menu.

The Windows 7 installation accepted the partition 1 for installation
without any change and even proceeded without formatting it anew. It did
not create an additional partition (which it had done previously when
another primary partition was possible, because at that time I had used
only three.)

Of course, Windows changed the partition tables such that the IBM
bootmanager did no longer take over at boot time.

But with the bootable USB-stick and and DFsee one can repair this. It
is not sufficient to set the startable flag with e.g. Knoppix to the
Bootmanager partition. The bootmanger does not start with the
bootrecord written by Windows.

Also one cannot just restore the OS/2 partition boot records, as then
Windows complains at bootup about a device which it cannot find, asks
to be repaired and after some minutes reports that the attempt to
repair failed.

To repair the boot record one has to execute in the DFsee menu

FDISK, OS/2 LVM and Bootmanger, BMGR W2K CHS and I13X fix

and

FDISK, Part-table cleanup repair, Cleanup partition table

and reboot via

File, Boot using IBM bootmanger, Windows

Of course, one has to remove the USB-stick before reboot.

Windows started with no trace of the bootmanger, but on the next
reboot the IBM bootmanger took over and allows now to boot
Windows 7 or OS/2 or Debian Linux.

Under Linux

update-grub

will find Windows 7 and enable to chainboot Windows if one boots
Linux with the IBM bootmanger. But if Windows 7 is installed in only
one partition this chainboot is not required.

Finally I made a backup of the partition tables of the working triple
boot installation.

[A.D. Fundum]

Post by Norbert Dragon
It is advisable to use a second primary partition for an additional
operating system and the third for the IBM bootmanager.

In that rather specific order?

My order, also the physical lay-out:

1st (the only possibility): primary, W7 C: (50 GB, NTFS)
2nd: primary, OS/2 BM
3rd: primary , eCS 1.2 C: (2 GB, HPFS)
4th: logical, eCS' D: (2 GB, HPFS)
5th: logical, eCS' E: (>20 GB, JFS)

Post by Norbert Dragon
(If one hasnt used up enough partitions, then Windows 7 creates two
partitions partitions without asking, one partition of about 100 MB for
system files:)

So far "upgrades" from XP to W7 didn't create extra partitions.


--

[Shmuel (Seymour J.) Metz]

Post by A.D. Fundum
3rd: primary , eCS 1.2 C: (2 GB, HPFS)

Why primary?

[ivan]

On Wed, 12 Jun 2013 21:06:18 UTC, Shmuel (Seymour J.) Metz

Post by Shmuel (Seymour J.) Metz

Post by A.D. Fundum
3rd: primary , eCS 1.2 C: (2 GB, HPFS)

Why primary?

To stop win 7 using two partitions which upsets BM.

--

[A.D. Fundum]

Post by ivan

Post by Shmuel (Seymour J.) Metz

Post by A.D. Fundum
3rd: primary , eCS 1.2 C: (2 GB, HPFS)

Why primary?

To stop win 7 using two partitions which upsets BM.

Besides that, there's probably nothing wrong with my partitions
(verified with DFSee's support). Let's summarize it as "it, an easy
setup, should work". The only option not directly related to W7 I saw
is to replace the BM with a second W7 test partition, and to use
AiRboot to avoid that problem of two W7 partitions. Maybe W7 expects 2
partitions. Lord knows. I've also posted the problem in some Microsoft
support forum (didn't work, "use another browser, not IE": Microsoft
+1), but so far there's no reply (Microsoft -1). I'll W8 (== W acht ==
Wacht == Wait) for an answer.


--

[A.D. Fundum]

Post by A.D. Fundum
so far there's no reply (Microsoft -1).

There's a reply. Too bad it's "Go back to the shop and ask for a
refund you won't get, but you can ask for it anyway.".


--

[A.D. Fundum]

Post by Norbert Dragon
Here is my recipe, to boot Windows 7, OS/2 and Debian Linux

And here's mine for Windows 7 (update of XP, Vista) and eCS 1.2. Some
steps may not be required.

1. Install XP (OEM, uses the whole harddisk)
2. Delete unneeded recovery partition
3. Shrink XP to the desired size
4. Create eCS partitions using the rest of the harddisk
5. Install eCS
6. Install AiR-BOOT (v1.10)
7. Upgrade XP to W7, while running XP
8. Use DFSee to recreate the MBR, keep the partition tables
9. Install eCS
10. Install AiR-boot (v1.10)
11. Boot eCS
12. Boot W7

Both eCS 1.2 and W7 use a primary partition. No BM, no 100 MB W7
System partition. In my case eCS uses 2 HPFS partition and one JFS
partition. No more boot error.


--

[Steve Wendt]

Post by A.D. Fundum
6. Install AiR-BOOT (v1.10)

I'm curious where this comes from, as 1.06 is the latest on SourceForge:
http://sourceforge.net/projects/air-boot/files/AiR-BOOT/

[A.D. Fundum]

Post by Steve Wendt

Post by A.D. Fundum
6. Install AiR-BOOT (v1.10)

I'm curious where this comes from, as 1.06 is the latest on SourceForge

http://svn.netlabs.org/air-boot

FTR: I haven't tried the combination of a single W7 partition, a
"repaired" MBR and older versions of AiR-BOOT. Even the OS/2 BM might
work. I just wanted to avoid the gazillionth re-install of full OSes,
restoring my eCS environment still isn't completed yet.


--

[Steve Wendt]

Post by Peter Brown

Post by Steve Wendt
I'm curious where this comes from, as 1.06 is the latest on SourceForge

http://svn.netlabs.org/air-boot

Thanks!

[Peter Brown]

Hi Steve

Post by Steve Wendt

Post by A.D. Fundum
6. Install AiR-BOOT (v1.10)

http://sourceforge.net/projects/air-boot/files/AiR-BOOT/

eCS2.1 ships with v1.07

eCS2.2 Beta ships with v1.08

After a bit of hunting I found the "AIR-BOOT versions for eComStation"
link on http://svn.netlabs.org/air-boot which leads here
http://www.bensbits.nl/ and an "AIR-BOOT v1.1.0 final" is shown.

Just to save you following the links:
http://bensbits.totalresults.nl/downloads/AiR-BOOT-v1.1.0-final.zip

I guess the question is: Should these builds also be available on
http://air-boot.sourceforge.net/


Regards

Pete

[Steven Levine]

On Sun, 23 Jun 2013 14:45:46 UTC, Peter Brown
<losepeteSPAM-ME-***@ntlworld.com> wrote:

Hi Peter,

Post by Peter Brown
I guess the question is: Should these builds also be available on
http://air-boot.sourceforge.net/

They could be if someone wants to do the work. This someone would
need commit access to the sourceforge AiRBoot project.

Steven

[Barry Landy]

On Mon, 24 Jun 2013, Steven Levine wrote:

:>On Sun, 23 Jun 2013 14:45:46 UTC, Peter Brown
:><losepeteSPAM-ME-***@ntlworld.com> wrote:
:>
:>Hi Peter,
:>
:>> I guess the question is: Should these builds also be available on
:>> http://air-boot.sourceforge.net/
:>
:>They could be if someone wants to do the work. This someone would
:>need commit access to the sourceforge AiRBoot project.

I raised this issue via bugtracker after I was pointed at 1.1.0 final
(perhaps because I was a beta tester of the changes to 1.0.7/.8)

Roderick Klein said it was a resource issue.

personally I think it is rather "off" to take something from sourceforge
and not have the courtesy to update it.

[A.D. Fundum]

Post by Barry Landy
personally I think it is rather "off" to take something from sourceforge
and not have the courtesy to update it.

I'm afraid there are a lot of hardly OS/2'ified (installer, icon, file
structure, ...) *nix-ports which aren't made known, nor added, to this
Sourceforge source. Perhaps it's a way for some people to contribute
to new developments, while not being a programmer (nor beta-tester,
like you)? I don't know if the maintainer of the Sourceforge page has
agreed, so I don't know if courtesy is an issue here. Apparently
AiR-BOOT isn't the only app which implies a choice between having it
or not having it, since evelopers are a limited resource. A
netlabs.org directory or a general software catalogue could have
helped too, AFAIK Martin Iturbide (sp?) of os2world.com is also trying
to avoid possibly disappearing websites with valuable software, which
in a way also is an effort to avoid Sourceforge -> Netlabs ->
mywebsite.com constructions.


--

[A.D. Fundum]

Post by A.D. Fundum
W7 installed first (worked), primary partition of 50 GB.

Some progress: a destructive upgrade. I removed all eCS and BM related
partitions. Just because I wanted to be sure, I did move the first and
only remaining partition, with Windows 7, to the middle of the disk,
using DFSee. This step may not be required, but I wanted to make sure
the first 1,024 cylinders were be available, regardless of the
bootability of this partition.

The remaining W7 partition doesn't have to boot, but the update DVD
has to be able to detect it's a legal upgrade or repair. Once that's
detect, it's possible to delete all partitions and to create a new
one. Next, there will be a message like "additional space may be
required for system files". The installer suddenly adds this "System"
partition of 100 MB. This partition won't be added

This silly system partition wasn't created when I first installed 50
GB of W7 in XP's 50 GB partition. If I would have choosen 49 GB, it
may worked too. Then there's at least 1 GB free for this silly system
partition, while the eCS partitions don't have to been deleted. I
haven't tried that, each attemp may waste at least hours, if not days.

The progress is that the "upgrade" DVD also can create this system
partition, which was a difference with (most) working installs or
instructions @ Hobbes. The natural thing to do is to select the XP
partition for the upgrade, but that will not create this silly system
partition. At least not in my case. Make room for that partition of
100 MB during the install of the "update".

I don't know yet if the progress means anything, at the moment I'm
still rerererererererererererererererererererere-installing, starting
from stratch.


--

[A.D. Fundum]

Post by A.D. Fundum
Some progress: a destructive upgrade.

What's the next step, after having created both W7's partition.
Install eCS, use AiRboot to avoid W7's number of non-logical
partitions, and add which W7 partition has to be used in AiRboot?


--

[A.D. Fundum]

Also works with XP, OS/2 BM, eCS 1.2; not all steps may be required:

1. Upgrade XP to W7, format partition or keep old files
2. Get rid of the OS/2 BM, recreate eCS partition(s)
3. DFSee: renew the MBR, keep tables.
4. Install eCS
5. Install AiR-BOOT
6. W7 doesn't boot, bootmgr error. Solvable with the W7 boot DVD
7. After fixing W7, both eCS and W7 did boot here

During step 1, you may note that the eCS boot partition may be seen as
type "System", which is the same type as the 100 MB partition W7 may
create when a new boot partition for W7 is created. I haven't seen the
boot error since I renewed the MBR after W7 could have touched that.
eCS was always installable after the MBR was renewed (not counting
other possible errors).

Regarding the second step, it may work with the OS/2 BM too, but I'm
expecting to upgrade to eCS 2.x anyway.


--

[A.D. Fundum]

Post by A.D. Fundum
The best result so far is a working eCS 1.2 and W7 with
error 0xc000000e.

Yet another hidden nasty, FTR, related to hardware which may be in use
in the eCS-community: no optimized video driver for your IBM ThinkPad.
The so-called "Windows Performance-Index" of e.g. a T42p running at
1600x1200 will be 1.0 out of 10, based on the video performance. If
needed, and there's an expected change from XP to W7/W8, then I'ld
recommend to install at least a 2 GHz CPU if you have to use Windows
to e.g. watch tv programmes. With a 1.8 GHz CPU, the load often tries
to exceed 100%. With a 2.0 GHz, the CPU load is pretty close to 100%.
I haven't tried other resolutions nor a 2.1 GHz CPU, but it seems to
be worth the effort.

Upgrading to an IBM/Lenovo T60p may also help, albeit then the
"Windows Performance-Index" may be just 2.0 out of 10, whatever that
means, again based on the video performance. A CPU upgrade is not
required for basic use, assuming there's enough memory available. Not
having an optimized video driver is the main reason to upgrade the CPU
of an eCS/Windows-notebook, which may involve the use of thermal
grease. Of course it's not required to upgrade the CPU before the OS
is installed, but you may have to consider it after installing W7/W8
with its VGA-based video driver.


--