danleff

I guess you didn't like Dapper Dan's response? Are you still speaking of the USB modem, analog modem, or router?? Which exact model? The 600 series can mean any of the above. If you are still speaking of the modem, then a search on Google shows that there is no support for this series (as Dan's link revealed) and I could find no reference to any drivers that have been written. It seems that the company has no interest in this and probably has not released the specs. for the modem. Some users have requested this and the request has fallen on deaf ears. Hopefully bumping this thread will find anyone who has this modem and can possibly shed more light on the issue.

Also, just to clarity, don't burn the iso itself to the cd as a data file. You need to choose the "burn image" feature of the burning software. See my draft on burning iso's at this link.

Well, the first question is, do you have any sound at all? Let's start with music. When you pop in a music cd, does the media player come up and seem to play, but there is no sound? Or, does no media player seem to be present when you pop the music cd in (no media player comes up)? Giving us a little more information will help isolate the problem.

I just started an iso burning how-to located here. Take a look at that. We get so many of these questions, I thought I should do one. It still is in draft, but, Blackpage is right. See if you burned it as data (you see only one iso file on the cd), or as an image (you see directories and files on the cd). Also, the onboard cd writer in XP does not handle iso files.

One point of clarification. make sure that you are running an exe file that is an executable vs. the installer exe file. Running the installer file will "uncompress" the needed files into the wine directory structure, but you need to know where the executable exe file is once this is done to actually try the program out. Also, may Windows based apps have specific dll files that need to be imported into the Wine environment. This is a reason why some of the apps. crash. Once we know what you would like to try out, we can give you some leads. Petergavin makes good points about setting up wine. If you are confised about this, just ask!

Fedora, unlike Mandrake, has not really compiled a list of known working hardware. The hardware requirements can be found here. This is a good starting point to make sure that your system has enough ram and speed to run the "heavy duty" distros. Also, depending on what you are looking to do with a distro, helps to choose which one that you might want to consider. Gaming, productivity, ease of use, experimenting, or a combination of all of these? If you are new to Linux, you may want to consider an easier distro to learn. A nice introduction to using Linux can be found by using one of the Live cdrom based distros that run of a cdrom without installing from a hard drive. This way you can test out Linux and see what you like. Most major distros have a live cd version available. Mepis and Knoppix are two fine cd based distros to give such a test drive from. Any reason why you are looking at Fedora only? If you let us know what hardware that you have, we can try to point you in the right direction. Finally, look at this thread to get some opinions.

The first thing to consider, is what Windows programs that you are looking to run. Wine does not run all programs made for Windows well, or even at all. If this is the case, there are usually good Linux based packages that will do what you will like sans the hassle of getting Windows apps. to work via Wine. Give us some idea what apps. that you are looking to run.

Which distro are you using? If you are "up[censored]" then most likely the source is the internet. If you are adding packages (programs) then the issue could be a bad cdrom disk, or you burned the disk at too high a speed, so it is not being read properly. Iso files like slow burn speeds, say 4X or 8X. The other issue sometimes is making sure that you inserted the proper cdrom disk in the series...disk 1 vs. disk 2 and so on. Finally what media are you using? older cdrom drives don't generally like cdrw disks and can have trouble reading them properly.

Well first, what symptoms are you having with the cdrom in the old system? Is it that you are unable to boot the Linux install disk? Once we know this, and look at this issue, then we can get to installing it on the new system, if you must, then using it as the primary OS on the old system? This is a bit more involved.

A somewhat dated but good guide is at the USB Scanners under Linux guide. Also, look at the Sane website to get some ideas. I have an old, but good Agfa 1212U that works fine for me.

Good question. I did a search on computone intelliport and did not come up with much, except for older kernels. I will assume that tey are either there, or were discontinued by default in base kernels, based on the age of the card and popularity, or lack thereof. There is one article that you may want to look at the following how-to which may send you in the right direction. It seems that the company made drivers for the 2.2 kernel series, so you may try e-mailing them or looking on their web site, if it is still up. P.S. I found this link that is still up. I see what you mean. Take a look at the linux.txt file.

Great! that's the ticket. 1. If the file(s) were present at all where XP thought that they should be...and 2. Grub looking in the right place. So, the problem is solved with some basic infomation and nudging with your ability to troubleshoot the problem. Nice job!

emccornack, what make/model system or motherboard do you have? The power down feature is a function of the bios and the distros inclusion of APM or ACPI features in the core kernel. There is a setting to enable or diable acpi on boot, which may solve the issue, but the function depends on the above mentioned features and whether you need to enable or disable the feature at boot time.

adamgdwn, let's try this fix first. Are you comfortable with editing files using a text editor? If not, we will try to walk you though it. You will need to edit the /boot/grub/menu.lst file. Change the entry for Windows from; title windows root (hd1,0) makeactive chainloader +1 To the following; title windows root (hd1,0) makeactive chainloader +1 map (hd0) (hd1) map (hd1) (hd0) Save the file and try rebooting into Windows via Grub. If this does not work, we will make one more adjustment.

Originally posted by Hipphead: Quote: I know that it is mounted caz of this Filesystem Size Used Avail Use% Mounted on /dev/hda5 5.6G 2.5G 2.9G 47% / /dev/hda7 3.5G 121M 3.4G 4% /home /dev/hdb1 39G 32K 39G 1% /mnt/secound /dev/hda1 28G 14G 14G 51% /mnt/win_c Both Harddrives are fat 32 formatted Can anyone suggest anything? Mandrake should have added the drive during the install. The entry should have been the next logical drive/partition such as; /dev/hdb1............./mnt/win_d If you added the drive after the install, then you have to edit /etc/fstab to add the entry with the proper permissions. mandrake is set up to automatically add the drive on install, if it is there. It uses the /etc/mtab file to set the drive up. Try the following. Look at /etc/fstab and check whether the drive is set up correctly. Match it to the code for the "C" drive, except change the values for hdb1. So, it should look like; Quote: /dev/hdb1 /mnt/second vfat umask=0,iocharset=iso8859-1,codepage=850 0 0 Reboot to allow mtab and fstab to be modified. You should then be able to go to the Home icon on the desktop and navigate to /mnt/second and access the drive with no problem. This way the drive will be automounted and accessible. You can check the permissions by right clicking on the second folder, select properties-->permissions-->advanced and make sure that permissions are there for show and write entries , as well as enter.

In Mandrake, to change the screen resolution,go to the Mandrake Control Center by clicking; start-->system-->configure-->configure your computer--> You will be prompted for your root password. Type it in and hit "OK" Click on the hardware menu on the left...then "screen resolution. You can also get there by clicking the icon on the panel on the bottom. Run your mouse pointer over the icon monitor with the wrench next to it. you will see "configure your computer" pop up. So you can click on this to get to the control panel as well. Just be a little careful and make sure that your monitor and video card can support what resolution and bits that you want to choose. It sounds like Mandrake is shutting down properly, but just not powering off the computer, correct? This is a function of Mandrake interfacing with the computer's bios correctly. Depending on your system and what you enabled (or disabled) for power management during the installation (and the bootloader) this can happen. You can just push the power button to turn off the system completely, or try to make a change or two to the bootloader to enable or disable power management. What computer system do you have (model and make)?

This is onboard Gigabyte with jacksense? If so, It would be important to use a new distro, like Mandrake 10.1 or Fedora 3. If you post the motherboard make and model, as well as the distro and version that you are using, this would help a lot.

OK, this tells us a lot. So, the MBR for Windows is not on the second hard drive. I believe that your assumption is correct. I bet you told Windows to install to the second hard drive, but it only installed Windows proper there, not the start-up files. It created boot on the MBR of the first drive. You installed Mandrake on the first drive, telling it to use the entire drive for Mandrake? You then allowed Mandrake to write the MBR to drive 1 (hda)? This is what I meant. Grub is a fine bootloader, but when you attempt to boot Windows, Windows can't find the startup files, where it expects to find them, on the first hard drive. This is why the usual senario would be to install XP first on the primary, then Linux on the secondary. I've never done it your way and would have to search around for a fix. Perhaps someone has and has a quick answer. I do know that one user did post his solution a while back, but I don't remember when, or who it was.

The older the floppy, the more issues you will have, regardless of the amount of usage. Fedora does some funky things with permissions, so I bet this is the problem. Exactly how are you trying to mount the floppy in Fedora? From the command line, or from a desktop icon? Are you getting any error messages, like only root can mount the floppy? Most distros will also complain about floppy disks that have been formatted over and over. The floppy formatting utility is also funky in Fedora. I really don't know what the cause is. But if you try to format a floppy in Fedora, make sure that it is not already mounted.

Don't get the term bootloader and startup files confused. By design, XP expects to be the first OS on the primary drive on any system. You should always install XP first on the primary, then Linux second. This solves a lot of issues. But, let's clarify first. Was your currently "second" hard drive originally the primary? In other words, did you change the jumpers on the drives to make the Windows drive the second hard drive in the system, before installing Mandrake? Did you install Grub on the Master Boot Record, or a /boot partition? Try something first. Get into the bios and change the boot sequence setting of the hard drive from HDD0 to HDD1. Save the changes and reboot. Does XP boot without Grub? Let us know and we can proceed.

I got to hand it to you, you come up with some good ones! I'll have to use this article to show my Windows colleagues, who don't believe me that Linux is more secure.

I believe that the modem is a PCTEL modem, which is designed to run in Windows, a so called "winmodem." These are a bear to get going. There is a slm driver for it, but I emember another post on this. Folks had varied results with it, especially on the 2.6 series kernel, such as the one that Fedora uses. Intel is the controller type/interface, not the modem. I would enlist the help of you Linux colleagues to help with this, especially if you are not adept at installing such packages (drivers). It is not an easy task for those not used to tackling this problem. The other option is to get an external serial modem, most of which work fairly well with Linux in general. These modems do have the hardware chip onboard, rather than relying on the motherboard/cpu to do the work of the hardware chip. This is a common problem in many laptops that have these inexpensive modems. A real hassle for Linux users.

Either a bad download, or bad burn. Did you burn the images at a slow speed, say 4X or 8X? They need to be burned at a slow rate. Also, did you verify the disks during the install?

I am reaching into my remote memory on this, but if it is an asci WEP key, you may need to modify the passkey phrase with an s:prefix. At the appropriate key line try; ...key=s:1234... Where 1234...is replaced with the actual WEP key.

Also, look at your WEP settings for the router. Is the password/WEP key in HEX or ASCI?