This is a multi-part message in MIME format.
------=_NextPart_000_0008_01C1F53C.CDEA93F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
At first i want to say "Thanks" for this great utility.
I helps me a lot. Only now i'm stuck on 1 piece.
I think this one is related to those BIOS that has problems. I have at =
work only IBM machines (and as anyone know IBM isn't 100% IBM Compatible =
:-)
Oh, before i go further, i'm using ISOLINUX v1.72 with Boot Scripter =
1.0 b9 and i'm not sure if i'm on the right address. I created a CD with =
2x memdisk 1.44, 1x memdisk 2.88 and the W2000 Pro loader (the i386 in =
root of CD). I created a menu 1 - 4 and as default (after 10 sec) it has =
to boot to the first HD. All disks working great, even the automated =
installation of W2000. After a reboot of the system i let it wait for =
the time out. And then it went wrong. If the CD tries to boot from local =
HD 0x80 i got the message "can't read device" and the CD restarts to the =
menu. Is this the 'Known' BIOS problem and if so can i overcome it.
kind regards,
Eddy Sweelssen
P.S. it took me some hours to read all the docs on the net, but =
'Whoooaa' it was wurth it. Now i know 20% more about my machine and what =
it is doing (wrong!) .
------=_NextPart_000_0008_01C1F53C.CDEA93F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2715.400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>At first i want to say "Thanks" for =
this great=20
utility.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I helps me a lot. Only now i'm stuck on =
1=20
piece.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I think this one is related to those =
BIOS that has=20
problems. I have at work only IBM machines (and as anyone know IBM isn't =
100%=20
IBM Compatible :-)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Oh, before i go further, i'm =
using ISOLINUX=20
v1.72 with Boot Scripter 1.0 b9 and i'm not sure if i'm on the right =
address. I=20
created a CD with 2x memdisk 1.44, 1x memdisk 2.88 and the W2000 Pro =
loader (the=20
i386 in root of CD). I created a menu 1 - 4 and as default (after 10 =
sec) it has=20
to boot to the first HD. All disks working great, even the automated=20
installation of W2000. After a reboot of the system i let it wait for =
the time=20
out. </FONT><FONT face=3DArial size=3D2>And then it went wrong. If the =
CD tries to=20
boot from local HD 0x80 i got the message "can't read device" and the CD =
restarts to the menu. Is this the 'Known' BIOS problem and if so can i =
overcome=20
it.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>kind regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Eddy Sweelssen</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>P.S. it took me some hours to read all =
the docs on=20
the net, but 'Whoooaa' it was wurth it. Now i know 20% more about my =
machine and=20
what it is doing (wrong!) .</FONT></DIV></BODY></HTML>
------=_NextPart_000_0008_01C1F53C.CDEA93F0--
------=_NextPart_000_0008_01C1F53C.CDEA93F0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
At first i want to say "Thanks" for this great utility.
I helps me a lot. Only now i'm stuck on 1 piece.
I think this one is related to those BIOS that has problems. I have at =
work only IBM machines (and as anyone know IBM isn't 100% IBM Compatible =
:-)
Oh, before i go further, i'm using ISOLINUX v1.72 with Boot Scripter =
1.0 b9 and i'm not sure if i'm on the right address. I created a CD with =
2x memdisk 1.44, 1x memdisk 2.88 and the W2000 Pro loader (the i386 in =
root of CD). I created a menu 1 - 4 and as default (after 10 sec) it has =
to boot to the first HD. All disks working great, even the automated =
installation of W2000. After a reboot of the system i let it wait for =
the time out. And then it went wrong. If the CD tries to boot from local =
HD 0x80 i got the message "can't read device" and the CD restarts to the =
menu. Is this the 'Known' BIOS problem and if so can i overcome it.
kind regards,
Eddy Sweelssen
P.S. it took me some hours to read all the docs on the net, but =
'Whoooaa' it was wurth it. Now i know 20% more about my machine and what =
it is doing (wrong!) .
------=_NextPart_000_0008_01C1F53C.CDEA93F0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2715.400" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>At first i want to say "Thanks" for =
this great=20
utility.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I helps me a lot. Only now i'm stuck on =
1=20
piece.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I think this one is related to those =
BIOS that has=20
problems. I have at work only IBM machines (and as anyone know IBM isn't =
100%=20
IBM Compatible :-)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Oh, before i go further, i'm =
using ISOLINUX=20
v1.72 with Boot Scripter 1.0 b9 and i'm not sure if i'm on the right =
address. I=20
created a CD with 2x memdisk 1.44, 1x memdisk 2.88 and the W2000 Pro =
loader (the=20
i386 in root of CD). I created a menu 1 - 4 and as default (after 10 =
sec) it has=20
to boot to the first HD. All disks working great, even the automated=20
installation of W2000. After a reboot of the system i let it wait for =
the time=20
out. </FONT><FONT face=3DArial size=3D2>And then it went wrong. If the =
CD tries to=20
boot from local HD 0x80 i got the message "can't read device" and the CD =
restarts to the menu. Is this the 'Known' BIOS problem and if so can i =
overcome=20
it.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>kind regards,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Eddy Sweelssen</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>P.S. it took me some hours to read all =
the docs on=20
the net, but 'Whoooaa' it was wurth it. Now i know 20% more about my =
machine and=20
what it is doing (wrong!) .</FONT></DIV></BODY></HTML>
------=_NextPart_000_0008_01C1F53C.CDEA93F0--