HD not detected

HD not detected

[Charles Hallenbeck]

I hope someone may have an explanation or a suggestion for this
one:

My friend has a Gateway machine with Windows 98 on a 12 GB disk
which works fine. She wants to move on up to Linux, and purchased
a second HD, a Maxtor 40 GB disk. She knows even less about
hardware than I do, and together we proceeded to just put the
disk in the machine and cable it up, without even looking at its
jumpers.

The machine now still boots fine into Windows, and Windows can
see the second drive okay. However, Linux cannot see either the
old drive or the new one. She is going to install Slackware 8.0
on her second disk, but when the installation boot disk and root
disk are run, and we have the login invitation as root, neither
fdisk nor cfdisk can 'open' any of the four HD devices, not even
/dev/hda.

Reviewing the boot messages for the ramdisk installation system,
there is no mention of any HD either. It does find her CD drive
on /dev/hdc, but no other /dev/hdx devices are found.

Anybody have any idea where to look for this problem?

Thanks - Chuck

*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
Visit me at http://www.mhonline.net/~chuckh
The Moon is Waxing Crescent (24% of Full)

Re: HD not detected

[Tommy Moore]

Hi Chuck, try removing the second drive and see what you get, if it 
doesn't find the first device then she may be using one of those udma 
cards. See what you get with just the first drive in the machine and if 
that works then change jumpers on second drive to slave and then see if 
that fixes the problem.

Tommy

Re: HD not detected

[Charles Hallenbeck]

Thanks, Tommy,

We will give those suggestions a try.

Chuck


On Fri, 18 Jan 2002, Tommy Moore wrote:

> Hi Chuck, try removing the second drive and see what you get, if it
> doesn't find the first device then she may be using one of those udma
> cards. See what you get with just the first drive in the machine and if
> that works then change jumpers on second drive to slave and then see if
> that fixes the problem.
>
> Tommy
>
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
Visit me at http://www.mhonline.net/~chuckh
The Moon is Waxing Crescent (24% of Full)

Re: HD not detected

[Kerry Hoath]

did you connect both drives to the one ide cable?
If so they are probably both master on the one cable
and it is even money which the bios/os will find and won't find.
If the second drive is on the second cable with the cdrom;
then again you probably have the cdrom as master (hdc you did say) and the maxtor
as master as well. Change t he cdrom to slave. this is often done
by moving the jumper as follows:
With the ide connector of the cdrom facing you working from right to left you 
have:
4-pin power connector, 40-pin ide connector master/slave jumpers mode jumpers red-book
audio conector 4-pin.
The master/slave jumper usually has 6 pins or mone in  a row of 2
excuse the poor ascii art but like this:
***
***

The jumper closes 2 pins and sits straight up and down. settings are 
given from the *right*
right-most pins: drive is slave.
middle pins: drive is master
Left hand set of pins: drive is set to cable select.
In summary from the right: master, slave cable select.
This is often written on the drive as MA SL CS from the right or
CS SL MA fromt heleft above or below the jumper block.
Put the cdrom as slave and connect the maxtor as master to the secondary controller.

Hope t hishelps.

Regards, Kerry.
On Fri, Jan 18, 2002 at 03:16:22PM -0500, Charles Hallenbeck wrote:
> I hope someone may have an explanation or a suggestion for this
> one:
> 
> My friend has a Gateway machine with Windows 98 on a 12 GB disk
> which works fine. She wants to move on up to Linux, and purchased
> a second HD, a Maxtor 40 GB disk. She knows even less about
> hardware than I do, and together we proceeded to just put the
> disk in the machine and cable it up, without even looking at its
> jumpers.
> 
> The machine now still boots fine into Windows, and Windows can
> see the second drive okay. However, Linux cannot see either the
> old drive or the new one. She is going to install Slackware 8.0
> on her second disk, but when the installation boot disk and root
> disk are run, and we have the login invitation as root, neither
> fdisk nor cfdisk can 'open' any of the four HD devices, not even
> /dev/hda.
> 
> Reviewing the boot messages for the ramdisk installation system,
> there is no mention of any HD either. It does find her CD drive
> on /dev/hdc, but no other /dev/hdx devices are found.
> 
> Anybody have any idea where to look for this problem?
> 
> Thanks - Chuck
> 
> *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
> Visit me at http://www.mhonline.net/~chuckh
> The Moon is Waxing Crescent (24% of Full)
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au

Re: HD not detected

[Richard Villa]

Well,

First off, you need to make sure that the drives are set up correctly.  
The jumpers need to be configured so that the first drive is the master, 
and the second drive is the slave.
Next I would boot the machine with a dos floppy to make sure that the 
system sees both drives.
TThen you need to partition the new drive, and if you are going to want 
any dos partitions one the drive allocate and format them.

Now you should be able to do your install.

Richard

On Fri, 18 Jan 2002, Charles Hallenbeck 
wrote:

> I hope someone may have an explanation or a suggestion for this
> one:
> 
> My friend has a Gateway machine with Windows 98 on a 12 GB disk
> which works fine. She wants to move on up to Linux, and purchased
> a second HD, a Maxtor 40 GB disk. She knows even less about
> hardware than I do, and together we proceeded to just put the
> disk in the machine and cable it up, without even looking at its
> jumpers.
> 
> The machine now still boots fine into Windows, and Windows can
> see the second drive okay. However, Linux cannot see either the
> old drive or the new one. She is going to install Slackware 8.0
> on her second disk, but when the installation boot disk and root
> disk are run, and we have the login invitation as root, neither
> fdisk nor cfdisk can 'open' any of the four HD devices, not even
> /dev/hda.
> 
> Reviewing the boot messages for the ramdisk installation system,
> there is no mention of any HD either. It does find her CD drive
> on /dev/hdc, but no other /dev/hdx devices are found.
> 
> Anybody have any idea where to look for this problem?
> 
> Thanks - Chuck
> 
> *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
> Visit me at http://www.mhonline.net/~chuckh
> The Moon is Waxing Crescent (24% of Full)
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: HD not detected

[Kerry Hoath]

You only want the first drive as master and second drive as slave if they are on the same cable;
and in fact considering that an ide drive will
latch the bus and not allow another drive to do a transferr whilst it is busy
unless overlap ata is supported it is best to put both high-speed
devices i.e. drives on separate cables and slave your cdrom to  the
secondary channel if possible. This way data flow is not stalled
if one drive is allways beeing accessed and you want to access the other drive at the same time.
This also lets you do  RAID on ide drives
with maximum efficency without buying an ide raid card i.e. software RAID.

Regards, Kerry.
On Fri, Jan 18, 2002 at 03:59:04PM -0600, Richard Villa wrote:
> Well,
> 
> First off, you need to make sure that the drives are set up correctly.  
> The jumpers need to be configured so that the first drive is the master, 
> and the second drive is the slave.
> Next I would boot the machine with a dos floppy to make sure that the 
> system sees both drives.
> TThen you need to partition the new drive, and if you are going to want 
> any dos partitions one the drive allocate and format them.
> 
> Now you should be able to do your install.
> 
> Richard
> 

-- 
Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au

Re: HD not detected

[Charles Hallenbeck]

Kerry -

Many thanks. That is very helpful. We will give it another shot
later this evening.

Chuck

On Sat, 19 Jan 2002, Kerry Hoath wrote:

> did you connect both drives to the one ide cable?
> If so they are probably both master on the one cable
> and it is even money which the bios/os will find and won't find.
> If the second drive is on the second cable with the cdrom;
> then again you probably have the cdrom as master (hdc you did say) and the maxtor
> as master as well. Change t he cdrom to slave. this is often done
> by moving the jumper as follows:
> With the ide connector of the cdrom facing you working from right to left you
> have:
> 4-pin power connector, 40-pin ide connector master/slave jumpers mode jumpers red-book
> audio conector 4-pin.
> The master/slave jumper usually has 6 pins or mone in  a row of 2
> excuse the poor ascii art but like this:
> ***
> ***
>
> The jumper closes 2 pins and sits straight up and down. settings are
> given from the *right*
> right-most pins: drive is slave.
> middle pins: drive is master
> Left hand set of pins: drive is set to cable select.
> In summary from the right: master, slave cable select.
> This is often written on the drive as MA SL CS from the right or
> CS SL MA fromt heleft above or below the jumper block.
> Put the cdrom as slave and connect the maxtor as master to the secondary controller.
>
> Hope t hishelps.
>
> Regards, Kerry.
> On Fri, Jan 18, 2002 at 03:16:22PM -0500, Charles Hallenbeck wrote:
> > I hope someone may have an explanation or a suggestion for this
> > one:
> >
> > My friend has a Gateway machine with Windows 98 on a 12 GB disk
> > which works fine. She wants to move on up to Linux, and purchased
> > a second HD, a Maxtor 40 GB disk. She knows even less about
> > hardware than I do, and together we proceeded to just put the
> > disk in the machine and cable it up, without even looking at its
> > jumpers.
> >
> > The machine now still boots fine into Windows, and Windows can
> > see the second drive okay. However, Linux cannot see either the
> > old drive or the new one. She is going to install Slackware 8.0
> > on her second disk, but when the installation boot disk and root
> > disk are run, and we have the login invitation as root, neither
> > fdisk nor cfdisk can 'open' any of the four HD devices, not even
> > /dev/hda.
> >
> > Reviewing the boot messages for the ramdisk installation system,
> > there is no mention of any HD either. It does find her CD drive
> > on /dev/hdc, but no other /dev/hdx devices are found.
> >
> > Anybody have any idea where to look for this problem?
> >
> > Thanks - Chuck
> >
> > *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
> > Visit me at http://www.mhonline.net/~chuckh
> > The Moon is Waxing Crescent (24% of Full)
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>

*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
Visit me at http://www.mhonline.net/~chuckh
The Moon is Waxing Crescent (24% of Full)

Re: HD not detected

[Gregory Nowak]

First, I think the jumpers should defenetly be loooked at, and set as master and slave appropriately. Once that is done, look at cmos/bios setup, and set options for both drives there approperiately. I am also assuming here that both drives are on the same primary controller, and that the ribbon is cabled to the drives and motherboard correctly.
Greg


On Fri, Jan 18, 2002 at 03:16:22PM -0500, Charles Hallenbeck wrote:
> I hope someone may have an explanation or a suggestion for this
> one:
> 
> My friend has a Gateway machine with Windows 98 on a 12 GB disk
> which works fine. She wants to move on up to Linux, and purchased
> a second HD, a Maxtor 40 GB disk. She knows even less about
> hardware than I do, and together we proceeded to just put the
> disk in the machine and cable it up, without even looking at its
> jumpers.
> 
> The machine now still boots fine into Windows, and Windows can
> see the second drive okay. However, Linux cannot see either the
> old drive or the new one. She is going to install Slackware 8.0
> on her second disk, but when the installation boot disk and root
> disk are run, and we have the login invitation as root, neither
> fdisk nor cfdisk can 'open' any of the four HD devices, not even
> /dev/hda.
> 
> Reviewing the boot messages for the ramdisk installation system,
> there is no mention of any HD either. It does find her CD drive
> on /dev/hdc, but no other /dev/hdx devices are found.
> 
> Anybody have any idea where to look for this problem?
> 
> Thanks - Chuck
> 
> *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
> Visit me at http://www.mhonline.net/~chuckh
> The Moon is Waxing Crescent (24% of Full)
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: HD not detected

[Gregory Nowak]

Why would you expect a DOS floppy to see the drives if Linux does not?
Greg


On Fri, Jan 18, 2002 at 03:59:04PM -0600, Richard Villa wrote:
> Well,
> 
> First off, you need to make sure that the drives are set up correctly.  
> The jumpers need to be configured so that the first drive is the master, 
> and the second drive is the slave.
> Next I would boot the machine with a dos floppy to make sure that the 
> system sees both drives.
> TThen you need to partition the new drive, and if you are going to want 
> any dos partitions one the drive allocate and format them.
> 
> Now you should be able to do your install.
> 
> Richard
> 
> On Fri, 18 Jan 2002, Charles Hallenbeck 
> wrote:
> 
> > I hope someone may have an explanation or a suggestion for this
> > one:
> > 
> > My friend has a Gateway machine with Windows 98 on a 12 GB disk
> > which works fine. She wants to move on up to Linux, and purchased
> > a second HD, a Maxtor 40 GB disk. She knows even less about
> > hardware than I do, and together we proceeded to just put the
> > disk in the machine and cable it up, without even looking at its
> > jumpers.
> > 
> > The machine now still boots fine into Windows, and Windows can
> > see the second drive okay. However, Linux cannot see either the
> > old drive or the new one. She is going to install Slackware 8.0
> > on her second disk, but when the installation boot disk and root
> > disk are run, and we have the login invitation as root, neither
> > fdisk nor cfdisk can 'open' any of the four HD devices, not even
> > /dev/hda.
> > 
> > Reviewing the boot messages for the ramdisk installation system,
> > there is no mention of any HD either. It does find her CD drive
> > on /dev/hdc, but no other /dev/hdx devices are found.
> > 
> > Anybody have any idea where to look for this problem?
> > 
> > Thanks - Chuck
> > 
> > *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
> > Visit me at http://www.mhonline.net/~chuckh
> > The Moon is Waxing Crescent (24% of Full)
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: HD not detected

[Kirk Wood]

The first thing I would say is that I would lay odds that you have a
conflict on what device is master on one of your IDE channels. Did you put
the new drive on with the first drive, or with the CD? This is what I can
say for sure:
The CD is a master drive on the second IDE chanel.
The original hard drive has been acting as a master on the first.

You may have cable select jumpered on one or more drives, but probably
don't have cable select cables. (If you do they have some of the wires
twisted just like a floppy cable.) I would start with resolving the jumper
problem you most certainly introduced.

=======
Kirk Wood
Cpt.Kirk@1tree.net

Nowlan's Theory:
        He who hesitates is not only lost, but several miles from
        the next freeway exit.

Will DecTalk work with with Speak Up?

[Sean murphy]

Hi All.

Will DecTalk PC work with SpeakUp?  If so, what are the steps to install?

The other option I had is DoubleTalk Pc instead of the Dectalk.  

My knowledge with Linux is not that high, at this point of time.

Linux redhat 7.1 running earlier version of the kernal.

Sean.

Re: Will DecTalk work with with Speak Up?

[Georgina]

Hi

Either of your cards will work but if you want some help you'll have to provide 
much more information and people here will be glad to help.  Here's some 
of the questions I have that will help us to help you:

Is it Redhat you wish to Install?  Or do you have a Redhat installation 
on which you wish to install a speakup enabled kernel?

Do you already have a set of disks from which you wish to install?

Do you have a cable connection, or know someone who is willing to download 
large files for you?

Do you still have linux partitions?  Do you have enough disk space?  Do you 
wish to maintain Windows partitions? 
Gena



>Hi All.
>
>Will DecTalk PC work with SpeakUp?  If so, what are the steps to install?
>
>The other option I had is DoubleTalk Pc instead of the Dectalk.  
>
>My knowledge with Linux is not that high, at this point of time.
>
>Linux redhat 7.1 running earlier version of the kernal.
>
>Sean.
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: Will DecTalk work with with Speak Up?

[Geoff Shang]

On Sat, 19 Jan 2002, Georgina wrote:

> Either of your cards will work

This is WRONG!

The dectalk PC card is *NOT* supported at this time.  This is a common
question so I'll repeat it - the  dectalk PC is NOT supported.  The reason
for this is that the dec PC needs to have its software loaded into it by
the screenreader before it will work.  As it is right now, speakup
synthesiser drivers must be initialised at boot time and of course, there
are no filesystems mounted from which to load the dec PC's internal
software in order to send it to the synth.  I presume that the size of this
software makes putting it in speakup itself prohibitive.  It's situations
like this that provide strong insentive for modularisation of speakup
drivers, as people have been wanting dec PC support for as long as I can
remember, at least since the external dectalks became supported.

I should add that the doubletalk PC is well and truly supported, it being
the first synth to work with speakup.

Geoff.

Re: HD not detected

[Richard Villa]

Well,

If anyone looks at the origin of the PC and how it boots, they will find 
that the DOS boot is still used to get the beast going no matter what OS 
you are going to load.

Richard
On Fri, 18 Jan 2002, Gregory Nowak wrote:

> Why would you expect a DOS floppy to see the drives if Linux does not?
> Greg
> 
> 
> On Fri, Jan 18, 2002 at 03:59:04PM -0600, Richard Villa wrote:
> > Well,
> > 
> > First off, you need to make sure that the drives are set up correctly.  
> > The jumpers need to be configured so that the first drive is the master, 
> > and the second drive is the slave.
> > Next I would boot the machine with a dos floppy to make sure that the 
> > system sees both drives.
> > TThen you need to partition the new drive, and if you are going to want 
> > any dos partitions one the drive allocate and format them.
> > 
> > Now you should be able to do your install.
> > 
> > Richard
> > 
> > On Fri, 18 Jan 2002, Charles Hallenbeck 
> > wrote:
> > 
> > > I hope someone may have an explanation or a suggestion for this
> > > one:
> > > 
> > > My friend has a Gateway machine with Windows 98 on a 12 GB disk
> > > which works fine. She wants to move on up to Linux, and purchased
> > > a second HD, a Maxtor 40 GB disk. She knows even less about
> > > hardware than I do, and together we proceeded to just put the
> > > disk in the machine and cable it up, without even looking at its
> > > jumpers.
> > > 
> > > The machine now still boots fine into Windows, and Windows can
> > > see the second drive okay. However, Linux cannot see either the
> > > old drive or the new one. She is going to install Slackware 8.0
> > > on her second disk, but when the installation boot disk and root
> > > disk are run, and we have the login invitation as root, neither
> > > fdisk nor cfdisk can 'open' any of the four HD devices, not even
> > > /dev/hda.
> > > 
> > > Reviewing the boot messages for the ramdisk installation system,
> > > there is no mention of any HD either. It does find her CD drive
> > > on /dev/hdc, but no other /dev/hdx devices are found.
> > > 
> > > Anybody have any idea where to look for this problem?
> > > 
> > > Thanks - Chuck
> > > 
> > > *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
> > > Visit me at http://www.mhonline.net/~chuckh
> > > The Moon is Waxing Crescent (24% of Full)
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > 
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

Re: HD not detected

[Amanda Lee]

Yeah, by today's standards, they'd call tis a "bootstrap" hahahah! but it's
obviously not that primative.

Amanda Lee

----- Original Message -----
From: "Richard Villa" <rvilla1@swbell.net>
To: <speakup@braille.uwo.ca>
Sent: Friday, January 18, 2002 9:09 PM
Subject: Re: HD not detected


> Well,
>
> If anyone looks at the origin of the PC and how it boots, they will find
> that the DOS boot is still used to get the beast going no matter what OS
> you are going to load.
>
> Richard
> On Fri, 18 Jan 2002, Gregory Nowak wrote:
>
> > Why would you expect a DOS floppy to see the drives if Linux does not?
> > Greg
> >
> >
> > On Fri, Jan 18, 2002 at 03:59:04PM -0600, Richard Villa wrote:
> > > Well,
> > >
> > > First off, you need to make sure that the drives are set up correctly.
> > > The jumpers need to be configured so that the first drive is the
master,
> > > and the second drive is the slave.
> > > Next I would boot the machine with a dos floppy to make sure that the
> > > system sees both drives.
> > > TThen you need to partition the new drive, and if you are going to
want
> > > any dos partitions one the drive allocate and format them.
> > >
> > > Now you should be able to do your install.
> > >
> > > Richard
> > >
> > > On Fri, 18 Jan 2002, Charles Hallenbeck
> > > wrote:
> > >
> > > > I hope someone may have an explanation or a suggestion for this
> > > > one:
> > > >
> > > > My friend has a Gateway machine with Windows 98 on a 12 GB disk
> > > > which works fine. She wants to move on up to Linux, and purchased
> > > > a second HD, a Maxtor 40 GB disk. She knows even less about
> > > > hardware than I do, and together we proceeded to just put the
> > > > disk in the machine and cable it up, without even looking at its
> > > > jumpers.
> > > >
> > > > The machine now still boots fine into Windows, and Windows can
> > > > see the second drive okay. However, Linux cannot see either the
> > > > old drive or the new one. She is going to install Slackware 8.0
> > > > on her second disk, but when the installation boot disk and root
> > > > disk are run, and we have the login invitation as root, neither
> > > > fdisk nor cfdisk can 'open' any of the four HD devices, not even
> > > > /dev/hda.
> > > >
> > > > Reviewing the boot messages for the ramdisk installation system,
> > > > there is no mention of any HD either. It does find her CD drive
> > > > on /dev/hdc, but no other /dev/hdx devices are found.
> > > >
> > > > Anybody have any idea where to look for this problem?
> > > >
> > > > Thanks - Chuck
> > > >
> > > > *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
> > > > Visit me at http://www.mhonline.net/~chuckh
> > > > The Moon is Waxing Crescent (24% of Full)
> > > >
> > > >
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > >
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>

Re: HD not detected

[Shaun Oliver]

ok chuck first and foremost you must once you've put a new drive in the
machine, always check the bios to ensure that all drives are being
detected.
a good way to ensure that your drives are always seen is to set them all
to auto detect and possibly move the jumper to cable sellect.
the bios if it's recent enough should just pick up the fact that there's
a drive there and assign it according to it's ide channel.
hth
On Fri, 18
Jan 2002, Charles Hallenbeck wrote:

> I hope someone may have an explanation or a suggestion for this
> one:
>
> My friend has a Gateway machine with Windows 98 on a 12 GB disk
> which works fine. She wants to move on up to Linux, and purchased
> a second HD, a Maxtor 40 GB disk. She knows even less about
> hardware than I do, and together we proceeded to just put the
> disk in the machine and cable it up, without even looking at its
> jumpers.
>
> The machine now still boots fine into Windows, and Windows can
> see the second drive okay. However, Linux cannot see either the
> old drive or the new one. She is going to install Slackware 8.0
> on her second disk, but when the installation boot disk and root
> disk are run, and we have the login invitation as root, neither
> fdisk nor cfdisk can 'open' any of the four HD devices, not even
> /dev/hda.
>
> Reviewing the boot messages for the ramdisk installation system,
> there is no mention of any HD either. It does find her CD drive
> on /dev/hdc, but no other /dev/hdx devices are found.
>
> Anybody have any idea where to look for this problem?
>
> Thanks - Chuck
>
> *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
> Visit me at http://www.mhonline.net/~chuckh
> The Moon is Waxing Crescent (24% of Full)
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

-- 
Shaun Oliver

Marriage is a three ring circus:
engagement ring, wedding ring, and suffering.
                -- Roger Price

Email: shauno@goanna.net.au
Icq: 76958435

Re: Will DecTalk work with with Speak Up?

[Shaun Oliver]

Hi Sean,
You'd do better to run the doubletalk pc
as the dectalk pc I don't think is supported yet.
I will stand to be corrected on this.
On Sat, 19 Jan 2002, Sean
murphy
wrote:

> Hi All.
>
> Will DecTalk PC work with SpeakUp?  If so, what are the steps to install?
>
> The other option I had is DoubleTalk Pc instead of the Dectalk.
>
> My knowledge with Linux is not that high, at this point of time.
>
> Linux redhat 7.1 running earlier version of the kernal.
>
> Sean.
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

-- 
Shaun Oliver

Marriage is a three ring circus:
engagement ring, wedding ring, and suffering.
                -- Roger Price

Email: shauno@goanna.net.au
Icq: 76958435

Re: Will DecTalk work with with Speak Up?

[Gregory Nowak]

Are you installing a distribution other then redhat? If so, then which one?
Greg


On Sat, Jan 19, 2002 at 01:39:12AM +0000, Georgina wrote:
> Hi
> 
> Either of your cards will work but if you want some help you'll have to provide 
> much more information and people here will be glad to help.  Here's some 
> of the questions I have that will help us to help you:
> 
> Is it Redhat you wish to Install?  Or do you have a Redhat installation 
> on which you wish to install a speakup enabled kernel?
> 
> Do you already have a set of disks from which you wish to install?
> 
> Do you have a cable connection, or know someone who is willing to download 
> large files for you?
> 
> Do you still have linux partitions?  Do you have enough disk space?  Do you 
> wish to maintain Windows partitions? 
> Gena
> 
> 
> 
> >Hi All.
> >
> >Will DecTalk PC work with SpeakUp?  If so, what are the steps to install?
> >
> >The other option I had is DoubleTalk Pc instead of the Dectalk.  
> >
> >My knowledge with Linux is not that high, at this point of time.
> >
> >Linux redhat 7.1 running earlier version of the kernal.
> >
> >Sean.
> >
> >
> >_______________________________________________
> >Speakup mailing list
> >Speakup@braille.uwo.ca
> >http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: HD not detected

[Gregory Nowak]

Since I've discovered linux, not for me.
I mean this for pcs that have been worked on internally, as well as a brand new machine.
I switch to a DOS floppy only when I have some reason to doubt dmesg output.
Greg


On Fri, Jan 18, 2002 at 08:09:05PM -0600, Richard Villa wrote:
> Well,
> 
> If anyone looks at the origin of the PC and how it boots, they will find 
> that the DOS boot is still used to get the beast going no matter what OS 
> you are going to load.
> 
> Richard
> On Fri, 18 Jan 2002, Gregory Nowak wrote:
> 
> > Why would you expect a DOS floppy to see the drives if Linux does not?
> > Greg
> > 
> > 
> > On Fri, Jan 18, 2002 at 03:59:04PM -0600, Richard Villa wrote:
> > > Well,
> > > 
> > > First off, you need to make sure that the drives are set up correctly.  
> > > The jumpers need to be configured so that the first drive is the master, 
> > > and the second drive is the slave.
> > > Next I would boot the machine with a dos floppy to make sure that the 
> > > system sees both drives.
> > > TThen you need to partition the new drive, and if you are going to want 
> > > any dos partitions one the drive allocate and format them.
> > > 
> > > Now you should be able to do your install.
> > > 
> > > Richard
> > > 
> > > On Fri, 18 Jan 2002, Charles Hallenbeck 
> > > wrote:
> > > 
> > > > I hope someone may have an explanation or a suggestion for this
> > > > one:
> > > > 
> > > > My friend has a Gateway machine with Windows 98 on a 12 GB disk
> > > > which works fine. She wants to move on up to Linux, and purchased
> > > > a second HD, a Maxtor 40 GB disk. She knows even less about
> > > > hardware than I do, and together we proceeded to just put the
> > > > disk in the machine and cable it up, without even looking at its
> > > > jumpers.
> > > > 
> > > > The machine now still boots fine into Windows, and Windows can
> > > > see the second drive okay. However, Linux cannot see either the
> > > > old drive or the new one. She is going to install Slackware 8.0
> > > > on her second disk, but when the installation boot disk and root
> > > > disk are run, and we have the login invitation as root, neither
> > > > fdisk nor cfdisk can 'open' any of the four HD devices, not even
> > > > /dev/hda.
> > > > 
> > > > Reviewing the boot messages for the ramdisk installation system,
> > > > there is no mention of any HD either. It does find her CD drive
> > > > on /dev/hdc, but no other /dev/hdx devices are found.
> > > > 
> > > > Anybody have any idea where to look for this problem?
> > > > 
> > > > Thanks - Chuck
> > > > 
> > > > *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
> > > > Visit me at http://www.mhonline.net/~chuckh
> > > > The Moon is Waxing Crescent (24% of Full)
> > > > 
> > > > 
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > 
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: HD not detected

[Gregory Nowak]

I think someone already mentioned this. Cable select will work only if you have the right ribon for it, and if your controller/drive support it.
Greg


On Sat, Jan 19, 2002 at 02:33:47PM +1100, Shaun Oliver wrote:
> ok chuck first and foremost you must once you've put a new drive in the
> machine, always check the bios to ensure that all drives are being
> detected.
> a good way to ensure that your drives are always seen is to set them all
> to auto detect and possibly move the jumper to cable sellect.
> the bios if it's recent enough should just pick up the fact that there's
> a drive there and assign it according to it's ide channel.
> hth
> On Fri, 18
> Jan 2002, Charles Hallenbeck wrote:
> 
> > I hope someone may have an explanation or a suggestion for this
> > one:
> >
> > My friend has a Gateway machine with Windows 98 on a 12 GB disk
> > which works fine. She wants to move on up to Linux, and purchased
> > a second HD, a Maxtor 40 GB disk. She knows even less about
> > hardware than I do, and together we proceeded to just put the
> > disk in the machine and cable it up, without even looking at its
> > jumpers.
> >
> > The machine now still boots fine into Windows, and Windows can
> > see the second drive okay. However, Linux cannot see either the
> > old drive or the new one. She is going to install Slackware 8.0
> > on her second disk, but when the installation boot disk and root
> > disk are run, and we have the login invitation as root, neither
> > fdisk nor cfdisk can 'open' any of the four HD devices, not even
> > /dev/hda.
> >
> > Reviewing the boot messages for the ramdisk installation system,
> > there is no mention of any HD either. It does find her CD drive
> > on /dev/hdc, but no other /dev/hdx devices are found.
> >
> > Anybody have any idea where to look for this problem?
> >
> > Thanks - Chuck
> >
> > *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
> > Visit me at http://www.mhonline.net/~chuckh
> > The Moon is Waxing Crescent (24% of Full)
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> 
> -- 
> Shaun Oliver
> 
> Marriage is a three ring circus:
> engagement ring, wedding ring, and suffering.
>                 -- Roger Price
> 
> Email: shauno@goanna.net.au
> Icq: 76958435
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: HD not detected

[Kerry Hoath]

Cabel select requires special cables
and you just can't set everything to cable select and expect everything to work all the time.
Many a dodgey techniton has done this and learnt the error of their ways.
Cable select uses a signal on the cable and it depends which port the drive is pougged into as to whether it is
master or slave.

Regards, Kerry.
On Sat, Jan 19, 2002 at 02:33:47PM +1100, Shaun Oliver wrote:
> ok chuck first and foremost you must once you've put a new drive in the
> machine, always check the bios to ensure that all drives are being
> detected.
> a good way to ensure that your drives are always seen is to set them all
> to auto detect and possibly move the jumper to cable sellect.
> the bios if it's recent enough should just pick up the fact that there's
> a drive there and assign it according to it's ide channel.
> hth
> On Fri, 18
> Jan 2002, Charles Hallenbeck wrote:
> 
> > I hope someone may have an explanation or a suggestion for this
> > one:
> >
> > My friend has a Gateway machine with Windows 98 on a 12 GB disk
> > which works fine. She wants to move on up to Linux, and purchased
> > a second HD, a Maxtor 40 GB disk. She knows even less about
> > hardware than I do, and together we proceeded to just put the
> > disk in the machine and cable it up, without even looking at its
> > jumpers.
> >
> > The machine now still boots fine into Windows, and Windows can
> > see the second drive okay. However, Linux cannot see either the
> > old drive or the new one. She is going to install Slackware 8.0
> > on her second disk, but when the installation boot disk and root
> > disk are run, and we have the login invitation as root, neither
> > fdisk nor cfdisk can 'open' any of the four HD devices, not even
> > /dev/hda.
> >
> > Reviewing the boot messages for the ramdisk installation system,
> > there is no mention of any HD either. It does find her CD drive
> > on /dev/hdc, but no other /dev/hdx devices are found.
> >
> > Anybody have any idea where to look for this problem?
> >
> > Thanks - Chuck
> >
> > *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
> > Visit me at http://www.mhonline.net/~chuckh
> > The Moon is Waxing Crescent (24% of Full)
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> 
> -- 
> Shaun Oliver
> 
> Marriage is a three ring circus:
> engagement ring, wedding ring, and suffering.
>                 -- Roger Price
> 
> Email: shauno@goanna.net.au
> Icq: 76958435
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
Kerry Hoath:  kerry@gotss.net kerry@gotss.eu.org or  kerry@gotss.spice.net.au

Re: HD not detected

[Shaun Oliver]

ah ok I didn't realize you needed special cables for cable sellect.
oh well, we live and learn.
On Sat,
19 Jan 2002, Kerry Hoath wrote:

> Cabel select requires special cables
> and you just can't set everything to cable select and expect everything to work all the time.
> Many a dodgey techniton has done this and learnt the error of their ways.
> Cable select uses a signal on the cable and it depends which port the drive is pougged into as to whether it is
> master or slave.
>
> Regards, Kerry.
> On Sat, Jan 19, 2002 at 02:33:47PM +1100, Shaun Oliver wrote:
> > ok chuck first and foremost you must once you've put a new drive in the
> > machine, always check the bios to ensure that all drives are being
> > detected.
> > a good way to ensure that your drives are always seen is to set them all
> > to auto detect and possibly move the jumper to cable sellect.
> > the bios if it's recent enough should just pick up the fact that there's
> > a drive there and assign it according to it's ide channel.
> > hth
> > On Fri, 18
> > Jan 2002, Charles Hallenbeck wrote:
> >
> > > I hope someone may have an explanation or a suggestion for this
> > > one:
> > >
> > > My friend has a Gateway machine with Windows 98 on a 12 GB disk
> > > which works fine. She wants to move on up to Linux, and purchased
> > > a second HD, a Maxtor 40 GB disk. She knows even less about
> > > hardware than I do, and together we proceeded to just put the
> > > disk in the machine and cable it up, without even looking at its
> > > jumpers.
> > >
> > > The machine now still boots fine into Windows, and Windows can
> > > see the second drive okay. However, Linux cannot see either the
> > > old drive or the new one. She is going to install Slackware 8.0
> > > on her second disk, but when the installation boot disk and root
> > > disk are run, and we have the login invitation as root, neither
> > > fdisk nor cfdisk can 'open' any of the four HD devices, not even
> > > /dev/hda.
> > >
> > > Reviewing the boot messages for the ramdisk installation system,
> > > there is no mention of any HD either. It does find her CD drive
> > > on /dev/hdc, but no other /dev/hdx devices are found.
> > >
> > > Anybody have any idea where to look for this problem?
> > >
> > > Thanks - Chuck
> > >
> > > *<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*<<<=-=>>>*
> > > Visit me at http://www.mhonline.net/~chuckh
> > > The Moon is Waxing Crescent (24% of Full)
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> > --
> > Shaun Oliver
> >
> > Marriage is a three ring circus:
> > engagement ring, wedding ring, and suffering.
> >                 -- Roger Price
> >
> > Email: shauno@goanna.net.au
> > Icq: 76958435
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>

-- 
Shaun Oliver

Marriage is a three ring circus:
engagement ring, wedding ring, and suffering.
                -- Roger Price

Email: shauno@goanna.net.au
Icq: 76958435

Re: Will DecTalk work with with Speak Up?

[Georgina]

Hi

Whoops, sorry my mistake, don't know what I was thinking.  Sorry for any 
inconvience this may have caused.
Gena



>On Sat, 19 Jan 2002, Georgina wrote:
>
>> Either of your cards will work
>
>This is WRONG!
>
>The dectalk PC card is *NOT* supported at this time.  This is a common
>question so I'll repeat it - the  dectalk PC is NOT supported.  The reason
>for this is that the dec PC needs to have its software loaded into it by
>the screenreader before it will work.  As it is right now, speakup
>synthesiser drivers must be initialised at boot time and of course, there
>are no filesystems mounted from which to load the dec PC's internal
>software in order to send it to the synth.  I presume that the size of this
>software makes putting it in speakup itself prohibitive.  It's situations
>like this that provide strong insentive for modularisation of speakup
>drivers, as people have been wanting dec PC support for as long as I can
>remember, at least since the external dectalks became supported.
>
>I should add that the doubletalk PC is well and truly supported, it being
>the first synth to work with speakup.
>
>Geoff.
>
>
>
>_______________________________________________
>Speakup mailing list
>Speakup@braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup