Jim Fleig - CNC Services wrote:
>
> Can anyone shed any light on why I'm getting these "tray open..." messages,
>
Is there any possibility you have the IDE cables swapped, and the CD is
on IDE1 and the hard drive on IDE2?
Some BIOS's may be able to boot an existing OS like that, but may be
un
Jim Fleig - CNC Services wrote:
> Hi Stuart,
>
> I don't mind the redundancy. Sometimes things are tried twice (or more) in
> order to get them right once. :-)
>
> Machine B will not boot from the CD at all. hal91 on floppy will boot every
> time from the floppy. hal91 files on a CD will no
Maybe just as easy(?). Remove the hard drive from the machine that
won't (isn't) booting the CD and install it in the box
that can come up under 'Live'. Go thru the installation process and
then move the disk back to the other machine.
There is a possible issue here and that is getting X window
Jim,
One more redundant question. When you boot MachineA from the CD are
you then running Linux? If so is it possible to remove the CD from
MachineA and put it into MachineB?
thanks
Stuart
--
you can lead a person to knowledge
but you cannot make him think
und the "dd" command,
and messages disappears. Nice to have in muLinux.
I am using hal91 instead of muLinux but will the commands work the same?
Thanks for your interest and help.
Have a good day,
Jim
- Original Message -
From: "Stuart Stevenson"
To: "Enhanced Machi
Hm. The BIOS in most motherboards I have used (Dell, Intel, Nvida, Via)
will allow you to SPECIFY the order in which boot devices will be attempted.
In my daily non-EMC context, I usually set this to Floppy first, CD second,
HDD third. When setting up EMC this allows me to boot the LiveCD to do
wh
ready
> hdc : tray open
> [hal91 -=- /] _
>
> Are there other commands that would provide useful information?
>
> Thanks for your questions and advice.
>
> Hopefully this is closer to working.
>
> Have a good night,
>
> Jim
>
>
> ----- Original Message -
&g
On Tue, 2009-04-21 at 08:56 -0700, Rafael Skodlar wrote:
... snip
> PC is going to bootup from CD regardless of what's on the hard drive so
> all that playing with partitions won't make a difference if drive is not
> recognized.
>From my experience, I have had trouble with booting new Linux
instal
mands that would provide useful information?
Thanks for your questions and advice.
Hopefully this is closer to working.
Have a good night,
Jim
- Original Message -
From: "Stuart Stevenson"
To: "Enhanced Machine Controller (EMC)"
Sent: Tuesday, April 21, 2009 9
Jim,
Have you booted the CD in another computer? If not, you need to be
able to boot the CD. When you are able to boot the CD then the
installation process will identify the hard drive and partition it for
you. It will do an automatically generated configuration or you can do
a manual configurat
fdisk -l Enter
displays the following:
The number of cylinders for this disk is set to 1027.
This is larger than 1024, and may cause problems with:
1) software that runs at boot time (e.g., LILO)
2) booting and paritioning software form other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Segmentation f
The tower has booted!
Thank you for all of the replies. I read (but did not understand) all of
them. It seemed to make sense to me to focus on trying to boot with a
floppy because the DBAN floppy would boot every time. It took a long time
to find and then a couple of attempts to get hal91 to
has it yet been determined that the cd is in fact working and bootable?
I've seen people download the iso with winrar or a similar compression
program installed, see the icon and open and extract the files to a folder,
then burn the dir to a cd. autorun works, but no bootability.
another issue th
Jon wrote:-
<>
That was really my intention with the suggestion I made -
boot from a utility floppy and partition the hard drive so
that it won't wait around looking for partitions - plus, you
at least have the reassurance that you are doing something
positive!! We know from Jim's original pos
Jon Elson wrote:
> Rafael Skodlar wrote:
>> computers DO NOT SEE drives because of the partition. BIOS code knows
>> nothing about the partitions when it makes PC send low level commands to
>> hard drive: reset, read disk configuration (heads, cyl, sec/track),
>> seek, read raw sectors, transfer th
Rafael Skodlar wrote:
> computers DO NOT SEE drives because of the partition. BIOS code knows
> nothing about the partitions when it makes PC send low level commands to
> hard drive: reset, read disk configuration (heads, cyl, sec/track),
> seek, read raw sectors, transfer that data to memory, etc.
Ian W. Wright wrote:
> Jim,
>
> As you have probably worked out by now, your problems stem
> from the fact that DBan erases everything on the hard drive
> including the partition tables which are the index to the
> 'filing cabinet'. Your easiest way to get going again would
> be to start by cr
Jim,
As you have probably worked out by now, your problems stem
from the fact that DBan erases everything on the hard drive
including the partition tables which are the index to the
'filing cabinet'. Your easiest way to get going again would
be to start by creating a new primary partition of a
BRIAN GLACKIN wrote:
> To all,
>
> Jim,
>> this is way beyond EMC support ... You need seek help for BASIC PC setup
>> elsewhere. However
>
>
> While this is true, many of the people coming to EMC are from a different
> planet (windoze) and learning to walk in a new land takes time and
> patien
To all,
Jim,
>
> this is way beyond EMC support ... You need seek help for BASIC PC setup
> elsewhere. However
While this is true, many of the people coming to EMC are from a different
planet (windoze) and learning to walk in a new land takes time and
patience. This very stumbling block has tr
--- Original Message -
> From: "Rafael Skodlar"
> To: "Enhanced Machine Controller (EMC)"
> Sent: Monday, April 20, 2009 1:54 PM
> Subject: Re: [Emc-users] Linux installation problem
>
>
>> Jim,
>>
>> this is way beyond EMC support ... You ne
-
From: "Rafael Skodlar"
To: "Enhanced Machine Controller (EMC)"
Sent: Monday, April 20, 2009 1:54 PM
Subject: Re: [Emc-users] Linux installation problem
> Jim,
>
> this is way beyond EMC support ... You need seek help for BASIC PC setup
> elsewhere. Howe
Jim,
this is way beyond EMC support ... You need seek help for BASIC PC setup
elsewhere. However
Jim Fleig - CNC Services wrote:
> Hi Ian,
>
> Thank you for the reply.
>
> The boot sequence was set to CDROM, A, C.
>
> I downloaded Ranish, unzipped and copied to a floppy. The boot sequence was
Hi Jim,
Since it will boot from a floppy at least it is not dead.
You might try setting the boot sequence (again) so CDROM is first;
nothing after that does you any good.
If you have a known good bootable CD then try that.
I have had trouble with some CD drives. Swapping drives often
fixes things.
Hi Ian,
Thank you for the reply.
The boot sequence was set to CDROM, A, C.
I downloaded Ranish, unzipped and copied to a floppy. The boot sequence was
changed to A, C, SCSI (no A, C, CDROM choice). When the computer is turned
on the boot screen lists Pri. Master Disk: LBA, UDMA 66, 8455MB, P
25 matches
Mail list logo
