On Sun, 8 Jan 2012, the wise Polytropon wrote:
Does this image boot successfully?
Unfortunately this is also a no go. I think Intel has done something
special to their iso's, considering that I'm missing 7MB of data.
Regards,
Marco
--
Men have as exaggerated an idea of their
rights as wom
On Sun, 8 Jan 2012, the wise Polytropon wrote:
Does this image boot successfully?
I don't know yet because I've used all my cd-r's :-(.
Within a few days I'm expecting some new cd-rw's and I'll let you know how
things went.
If you compare your ISO with the original one, file sizes
should b
On Sun, 8 Jan 2012 01:11:30 +0100 (CET), Marco Beishuizen wrote:
> On Sun, 8 Jan 2012, the wise Polytropon wrote:
>
> > If this is depending on the name "[BOOT]", there are
> > two ways to deal with special characters in file names,
> > if you need to specify them on the command line:
> >
> > a) u
On Sun, 8 Jan 2012, the wise Polytropon wrote:
If this is depending on the name "[BOOT]", there are
two ways to deal with special characters in file names,
if you need to specify them on the command line:
a) use escape sequences:
-b \[BOOT\]/Bootable_HardDisk.img
b) use quoting:
On Fri, 6 Jan 2012 17:22:57 +0100 (CET), Marco Beishuizen wrote:
> After that I tried to create the iso with:
> root@yokozuna:/data2/tmp# mkisofs -r -J -b [BOOT]/Bootable_HardDisk.img
> -hard-disk-boot -o raid.iso /data2/tmp
> which gives an error: mkisofs: No match
>
> First I thought the direct
Hi,
I have an Intel SRCU42X raid controller that currently has firmware
version 414D. The bios flash was done by a "system update package", from
Intel which is an iso file that you can burn to a cd. The upgrade to 414D
went fine.
But the newest firmware version is 414I and is not available a
