Well, you know .... computer science IS NOT an exact (accurate ?) science.
If it was, everybody would know it ! <img src="/images/graemlins/grin.gif" alt="" />

I wanted, for already a long time, to install some Linux on an unused Compaq 1850R server I have.
Your post about Suse induced me to try it.
I downloaded a CD image from the german Suse web site, burnt a CD and launch an installation : after a few hours, I got a list of 50 or 100 packages in error and the loader installation refused to end correctly !
Result : I still don't have any Linux installed ... <img src="/images/graemlins/confused.gif" alt="" />
(just for fun : I gave that CD to a co-worker who launched the same instal procedure on a Sun server : no problemo, everything worked fine !!) <img src="/images/graemlins/blush.gif" alt="" />

I can't help with the Windoze side, haven't used windows in years.

Is it a PCI modem? If so, try using the command "lspci" to see what PCI devices where found. You should see several lines that look like this:
<pre><font class="small">code:</font><hr>
00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
00:1f.6 Modem: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Modem Controller (rev 02)
01:00.0 VGA compatible controller: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10]
</pre><hr>
Your modem should be one of them. You can also try using the "dmesg" command to see if your modem was found when linux booted.

Have you tried the standard voodoo? Move the card to a different slot, pull it out and reseat it, power off for 30 seconds, then try again?

I've seen those old server cd-rom drives go dead just from sitting for so long. Server runs for 3 years blowing a the bit of dust in the air on the drive electronics and when you try to use it it will run a bit then die. Suse does have an ftp option, you could boot from the suse cd and start the rest of the install from network.

If it´s a softmodem Suse 8.2 most probably doesn´t have the driver on the CD / DVD. When I did the installation Linux failed to detect the modem but it identified the chipset properly. I found a driver here . The installation warned about the version of the default kernel and reboot tended to freeze afterwards (a complete shutdown did work). An update solved this problem.

Groo:

It is a PCI modem with its own onboard processor.

Did all the standard voodoo including modifying port settings.

This modem is almost 2 years old and has been very reliable and was working before hard drive meltdown.

At what point do you issue the commands you mention. This is my first loading of Linux and I want all the hardware working in Windows before I start experimenting with Linux unless you think Linux may push some button to bring the modem in line.

Thanks!

Bountyhunter

Understood. I don't think linux will fix the modem, but I've had success using linux to diagnose problems like this. I suppose a windows expert could get the same stuff, but linux makes it relatively easy to get detailed hardware information. Linux is transparent, predictable. I'm never sure what windows is doing behind all those GUIs (graphical user interfaces).

Anyway, the two commands (lspci and dmesg) can be issued any time after the system has come all the way up. Log in, open a command window (it'll be called something like "command shell", "xterm", "console", etc.), and type "lspci" (no quotes). Then type "dmesg" (no quotes). Neither one will do anything to the hardware. Both just print some information that may or may not be helpful. I'm hoping lspci at least shows your modem even if it's not being assigned to a device. If your modem doesn't show up, it might be dead. :-(

Edit: As you know, there are several different linux distributions. They're all slightly different. If you get "command not found" for either of the above commands, you probably still have the command but it's not in your default PATH.

Groo:

After more voodoo and trying the 2 different methods detailed in the installation sheet that did not work for me, I found a third method listed and the modem came on line.

As soon as I find (I forget which pile of documentation on which desk, drawer, table, box, file cabinet, etc., I "organized" the info in. <img src="/images/graemlins/crazy.gif" alt="" /> <img src="/images/graemlins/tongue.gif" alt="" /> <img src="/images/graemlins/blush.gif" alt="" />), the settings for my ISP provider, I should be able to log on with my Primary AMD 1700+, 1.47 Gigahertz computer. I know I can get most of the info off of this secondary unit, but I prefer original instructions in order to get it right.

To all, thanks for the help, and buy Linux. As long as you are not using Windows XP with its different disk formatting protocol, you should be able to have a dual operating system platform and more of us can learn Linux together.

Bountyhunter <img src="/images/graemlins/smile.gif" alt="" />

Excellent!

I don't use Suse, so I don't know how to turn it on, but most linux distros include firewall software. I'd use it, even for a dialup connection. After that, be sure to disable any services you don't need (sendmail, portmapper, nfs, telnet, ftp, etc.) It's possible to make a linux machine very secure with a little effort.

There is a really cool new version of Damn Small Linux called the Metropipe portable virtual machine which is a virtual linux machine that runs from a USB key - it uses emulation technology to actually run DSL from the USB drive with all of your settings, data etc on the drive. You plug it in, double click on the machine and it starts up, giving you the same environment whether you run it from windows or linux. I keep one on my USB key for when I need to use other people's machines.

That is extremely cool