Andre Baron wrote:
At 00:01 12/03/99 EST, you wrote:
In a message dated 3/11/99 8:50:32 PM Pacific Standard Time,
[EMAIL PROTECTED] writes:
I would have imagined that /dev would cause problems (a simple cp in
/dev will quickly fill your destination directory... that /dev/zero file
In a message dated 3/11/99 8:50:32 PM Pacific Standard Time,
[EMAIL PROTECTED] writes:
I would have imagined that /dev would cause problems (a simple cp in
/dev will quickly fill your destination directory... that /dev/zero file
just never ends...)
i ment in windows
At 00:01 12/03/99 EST, you wrote:
In a message dated 3/11/99 8:50:32 PM Pacific Standard Time,
[EMAIL PROTECTED] writes:
I would have imagined that /dev would cause problems (a simple cp in
/dev will quickly fill your destination directory... that /dev/zero file
just never ends...)
i ment
I don't mean to be rude or question whether this really works. I don't
have extra space, else I'd try it myself. Can anyone confirm that this
works??
No it won't work. You are perfecly right with the problems in dev and the
boot sector. What you have to do is use the dd command to make a
At 15:06 11/03/99 -0800, you wrote:
A very good test to see if it's memory or bios-too-"optimized" related is
to compile something big (a kernel for example) several times in a row. If
your system succeeds to do so without any error, your system can be
considered clean on that point and you
At 00:01 12/03/99 EST, you wrote:
In a message dated 3/11/99 8:50:32 PM Pacific Standard Time,
[EMAIL PROTECTED] writes:
I would have imagined that /dev would cause problems (a simple cp in
/dev will quickly fill your destination directory... that /dev/zero file
just never ends...)
i ment
A very good test to see if it's memory or bios-too-"optimized" related is
to compile something big (a kernel for example) several times in a row. If
your system succeeds to do so without any error, your system can be
considered clean on that point and you can start to think about a new hard
In a message dated 3/11/99 3:23:17 PM Pacific Standard Time,
[EMAIL PROTECTED] writes:
? Maybe the disk is starting to go bad.
no, but this happens with floppy boot as well.
I think it is your RAM. I once had this problem as well. RAM seems to be
causing a lot of this kind of
I have sucessfully used a program called Ghost to mirror hard drives. It
is made by Symantec but I know Powerquest also makes one.
Jeffrey Chen wrote:
On Thu, 11 Mar 1999, Kuraiken wrote:
Is this booting from a floppy? Maybe the disk is starting to go bad.
no, but this happens with
[EMAIL PROTECTED] wrote:
then drag the first hard drive icon to the second and let it copy the data
Does this actually work?!
I would have imagined that /dev would cause problems (a simple cp in
/dev will quickly fill your destination directory... that /dev/zero file
just never ends...)
And
Hi Guys,
I am having a strange problem. When I boot into Linux, I get a
"CRC Error -- System Halted" error when vmlinuz is being loaded. The
strange thing is that it only happens sometimes; if I reset the machine
2 or 3 times in a roll, the kernel boots just fine. No error once the
kernel got
On Wed, 10 Mar 1999, you wrote:
Hi Guys,
I am having a strange problem. When I boot into Linux, I get a
"CRC Error -- System Halted" error when vmlinuz is being loaded. The
strange thing is that it only happens sometimes; if I reset the machine
2 or 3 times in a roll, the kernel boots
12 matches
Mail list logo
