OSS goes one's own

[SOLVED] OSS goes one's own

EDIT :
I solved the problem by installing OSS from one of the 3 OS (the one on the first partition) and by manually editing the bootwiz.oss file to bypass the nasty grayed options that buggy OSS has set.



Hello,

OSS is making me going completely nuts

Here is my configuration:
Hard Drive 0:
Partition 1: Primary NTFS Partition: Windows XP (Work)
Partition 2: Primary NTFS Partition: Windows XP (Games) (True Image of Partition 1)
Partition 3: Primary NTFS Partition: Windows Vista Business

Using Disk Director, i can successfully boot on any of the 3 OS by setting its partition active and others hidden.

The problem is that as soon as in install OSS, it is messing with system in partition 2 :
- the black/white flag indicating which partition will be booted on is set on partition 1
- a windows flag is set on the partition 2 instead of the black/white flag that should be set on it
- active/hidden checkboxes are disabled on partition 1 and so OSS don't let me hide the partitions i wanna be hidden.

Systems on partition 1 and 3 are perfectly bootable.
System on partition 2 boot with an "autocheck.exe" not found.

If i uninstall OSS i can boot again on system 2 by activating its partition and hidding the two others.

What is more weird is that yesterday, during testing, i managed to make the full stuff run well, i mean the 3 OS loading from OSS with the good partitions hidden. But i did not understand how i did it...

I had to redo the full setup for another reason and then im not able to make OSS run as it should do.

Acronis is not really serious : no technical documentation explaining really how oss is proceeding is available.
I cannot find myself a solution without information helping me understanding how the program proceeds.

Can anyone help me to understand how the full thing runs?
Thanks in advance for your help!
Regards,
Eric ORLUC

 

Re: [SOLVED] OSS goes one's own

A VERY BIG BUG with OSS and has been around for a LONG time.

I don't know why Acronis doesn't fix it.

The booting "active" partition should not be "forced" into a hidden state, even if it's hidden when OSS detects the OS.

Glad you found the solution. When using OSS, it seems that the easiest way to fix things is to edit the bootwiz.oss file manually.