pmpatrick

You do get a little more than a warm feeling in your heart knowing your supporting Mandrake. They also have a large download section of rpms specifically packaged for Mandrake. Sure you can get most of the stuff somewhere else but it is convenient. You can also vote on what future packages you would like to have them put together for inclusion in the download section.

You may be right. Try running the command "df" without quotes from a console with a zip disk in the drive. That should list all your block devices. From what you describe, I don't think you will see your zip drive but that will rule out any problem with mcc. Also, check kde Control Center>Information>SCSI and see if your zip drive is listed under scsi devices(hdd=ide-scsi means your zip drive is running under scsi emulation). I take it from the hdd designation that your zip drive is configured as slave on your second ide channel. You can try reconfiguring it as master and your cd writer as slave to see if that has any effect. Did you try booting with a zip disk in the drive? I saw a post either on this board or the old board where having a disk inserted at boot up fixed somebody's zip drive problem. It may be that kernel support was not enabled for the device. Here's a link on how to enable kernel support: http://www.linuxhelp.net/guides/zipdrive/ Before going through the above, I think you can check to see if kernel support is enabled for your zip drive in the kde Control Center. It's under System>Linux Kernel Configurator. From the above link you should check in the Block devices section for "Include IDE/ATAPI FLOPPY support". I think you can activate from within this program if it's not already activated. However, the above link does not show the zip drive running under scsi emulation so I'm not sure this approach is appropriate.

Not likely. I have win98, Mandrake 9.0 and Red Hat 8.0 on my box with no such problems. Many people dual boot without having their windows partitions corrupted. I suspect a windows problem but without knowing more it's hard to tell. Can your friend access /mnt/win_d in linux? If he can, you can copy the data on /mnt/win_d to the linux partition or C(/mnt/win_C) or both, reformat D and copy the data back. You may be able to access the data on the corrupted partition in linux even though windows can't. Also, why do you beleive the FAT is corrupted on D? What error messages does he get when he tries to boot into windows? Can he even get windows to boot? Have you tried running the windows utility scandisk to correct the problem and if so, what result? Post back with a little more info and I might be able to come up with more suggestions.

Glad I could be of help and thanks for the links. Exactly what I was looking for. I'm ready to give updating the kernel another go.

Agree with all of the above. Look at your error messages. They're telling you your hardware can't read the CD and the timeout set in your hardware has been exceeded. It tries again only to get the same result. You've got some older hardware(relatively) that may not be able to handle some of the newer CDR media currently on the market(at least with the drivers available during the install); either that or it's a marginal burn that the drive is having trouble reading. Try reburning at a slower rate; try reburning with a different media type(i.e. brand). If that doesn't help, post back. There are ways to install by copying the CDs to a FAT32 partition on your hard drive and installing directly of the hard drive. One way or another we can get you going.

What desktop GUI are you using? It's really not clear from your post exactly what you are trying to do. As far as getting rid of the what to do menu, DOlson was kind enough to publish a tutorial on that very subject on his website: http://mdkxp.by-a.com/ Check it out. There's a lot of great stuff there. If your trying to get rid of that top bar in Gnome and transfer the menu to the bottom bar, this is your link: http://www.club-nihil.net/mub/viewtopic.ph...5767&highlight= Post back and give more details if the above don't help.

I can suggest a few things that might help: 1. Try booting with a zip disk in the drive and see if you still have the same problem; 2.Try configuring your zip drive in Mandrake Control Center (mcc>Mount Points>Zip Drive). How is the device listed. Mine is listed as a scsi device (sda4) but it's a usb , not ide like yours. Check to see that mount points are defined and if so, what they are. Tick the Option button then OK which will bring up the Options window. Disable supermount and tick "user" and "noauto".

If it exists, I haven't found it and beleive me, I've looked. Anyway, even if the patch does exist, it's for kernel 2.4.18 and Mandrake 9.0 uses 2.4.19. However, I beleive 2.4.20 does correct the dma problem even though you still get the resource collision message. The message is apparently caused by Intel's BIOS but the situation is taken care of later in the boot process. This is based on my research of the issue. Also, I recently downloaded Yoper on a boot disk(similar to Knoppix) which uses kernel 2.4.20. Got the resource collision message but hdparm revealed that dma was enabled and I was getting 38MB/sec as opposed to 5MB/sec in Md 9.0. After scouring the message boards and seeing a lot of people complain that the situation is caused by Intel's "lazy" or "incomplete" BIOS, I emailed Intel support and asked if they had any plans to correct the problem with an updated BIOS. Got a nonresponse back, the gist of which was "No, we've got better things to do with our time. It's a kernel problem." Would recommend that anyone with 845E or 845G chipsets also bug Intel to let them know we're out here and are not happy with the situation. It's the only way things will change. Also tried updating the kernel some time ago to 2.4.19-something but really made a mess of it. Got dma enabled with this kernel(38MB/sec) but the system was dog sloooow, much worse than the original kernel. Sure I did something wrong; wound up going back to the original kernel. If you have a link to the Cooker 2.4.20 kernel, I'd appreciate that. Also, any advice on what you need to do to update the kernel so I don't repeat my prior errors would be welcome.

Please post your /etc/fstab file and your hardware(drives).

Just got home and ran PM from the flopies on my system. One other thing you might also want to try before resizing the windows partition is the "check partition" option in PM. Right click on the windows partition and select this option from the drop down menu. It might be able to fix things or give some helpful info. Good luck.

At he end of the day, I think a reinstall will be necessary as suggested above. Here's some things you might want to try if your feeling adventuterous. Before doing anything, back up your data on an external medium first since you could loose it all. Everything seems to point to your partition table having been altered in a way which makes the windows partition inaccessible to either windows or DOS. I don't think it was PM that caused the problem since you were able to reboot into windows after the operation was completed. I also don't think it's a matter of file corruption caused by PM, since that probably would not render the windows partition inaccessible in DOS(i.e. from the windows boot disk). After backing up your data, make a linux boot floppy as I suggested in my previous post. Do the fdisk /mbr thing to remove lilo. The following suggestions are designed to force a rewrite of the partition table by a windows friendly utility, hopefully in a form that will allow windows or DOS to see the windows partition. That's the idea anyway, maybe you can think of other ways to accomplish the same thing: 1. Run PM off the flopies and see if any errors are reported. If errors are reported and PM offers to correct them, answer yes. Reboot and see if you can get windows going. 2.If no errors are reported, look and see how PM sees your windows partition. That may be a good indication of how windows sees it. Note anything unusual(e.g. incorrect file system designated) and compare how PM sees the partitions with how linux sees them. If PM can see the windows partition and nothing seems out of sorts, try enlarging or shrinking the windows partition with PM which will cause a rewrite of the partition table. Reboot and see if it worked. If these don't work, go the reinstall route

I don't see anything unusual in your /etc/fstab file. Your windows partition entry is exactly like mine. Now more questions: 1. As I recall, when using PM to resize the windows partition that contains window's root directory, PM reboots into DOS, performs the operation and then reboots back to windows. Did this occur? 2. If you have the PM boot floppies, did you try booting with them and,if so, were any errors reported when you did? 3.When you did the fdisk /mbr thing and tried to reboot into windows, did you get any error messages or just blinking cursor? Inquiring minds want to know. :lol:

Let's try to get you back to square one. If you haven't already done so, make a boot floppy for linux by going into Mandrake Control Center (Start menu>Configuration >Mandrake Control Center). Type your root password at the prompt then tick Boot>Boot Disk. Put a floppy in the drive and tick build the disk. Test the floppy to make sure you can boot off the floppy into linux. Assuming you were able to successfully create a linux boot disk following the above(if not, don't go any further), next, rewrite your MBR by booting off a Win 98 boot disk and run the following command: fdisk /mbr This takes lilo off the MBR and rewrites it with window's MBR. You will still be able to access linux by using your boot floppy made above. Reboot and see if you can boot into windows. If you can , run Partition Magic and see if it reports any errors in your partition table. If it reports errors and asks if you want to correct them respond yes. I've noticed in the past that when I've used linux partitioning utilities and booted back into windows and ran Partition Magic, the program reports two errors for every partition created using the linux partitioning utility. I usually respond yes when the program offers to correct the errors and have had no further problems in either linux or windows. If you get this far and are able to boot into windows, post back and we can try to figure out how to reinstall lilo so you can boot into either windows or linux. Next, a few questions: 1. After you resized your windows partition with PM, did you test to see if you could boot back into windows(i.e. reboot into windows after the operation and before installing Mandrake)? 2. I notice you have a laptop. Many laptops come with a hidden partition from which you can restore windows. This is given in lieu of a CD restoration disk. Does your laptop have this kind of hidden partition?

I don't know how many times I've reposted this but it keeps coming up. You can move the start menu to the bottom bar in a few clicks and trash the top menu bar in Gnome 2.0 forever: http://www.club-nihil.net/mub/viewtopic.ph...5767&highlight= It's just that easy.

Your not alone. We all feel your pain. Check this thread: http://www.mandrakeusers.org/viewtopic.php...=639&highlight= It's not just a Mandrake problem; it's a kernel problem with 2.4.19. People with the current versions of Knoppix and Suse based on the same kernel are having the same problem. The install will go, but you cannot enable dma. The new kernel, 2.4.20 will fix the problem and it works fine under 2.4.18(Redhat 8.0). They just blew it with 2.4.19.

Since no one else is helping I guess I have to try again. Found something that might be the answer. Check out this post: http://www.club-nihil.net/mub/viewtopic.ph...er=asc&start=15 According to these guys, when you uninstall shorewall it also toasts your iptables. If they're missing and some script is looking for them it could be causing your problem. Check in rpmdrake and see if iptables is installed. If they're not, reinstall them. If they're there, uninstall them because they've been altered by shorewall and reinstall the iptables.

Glad you finally got to a GUI. Now that you're there you can use some of Mandrake's graphical configuraton utilities to reconfigure X. When you get to the screen with large icons go to the start menu>Terminals>Konsole which will open a console. Type su then Enter and type your root password at the prompt. Then type "mcc" without quotes and hit Enter. This should bring up Mandrake Control Center. Hit the "Hardware" button then "Graphical server configuration" . From here you can reconfigure your graphics card, monitor and resolution and test any changes you make. Check to see what's designated for your graphics card, and monitor and make any changes you think are appropriate. Hit the Test button to see if the changes you made are helping or making matters worse. Also see if you can increase your resolution which will make the icons smaller. When you get it the way you want hit the Options button and click "yes" in the popup window then quit and close mcc. Reboot and see if you can get to a graphical login screen. It sounds like your running in SVGA mode which is a very rudimentary graphics mode that all grapics cards support. The install program will select this mode when it doesn't recognize your grahics card. That's the first place I would look. Also be careful with your monitor settings. If you select a monitor with higher frequencies than your monitor supports, you can burn your monitor out if you run it for an extended period of time.

Try this: Right click on the bar where you want the menu, go up to "Add to Panel", then go down to "Gnome Menu" and click on it. A little black foot should appear on the bar and when you click on it you should see the Gnome start menu.

That was my idea on the other board. Given the age of your computer(two years), I don't think your battery is going. When the system battery starts to go, the bios setup has a tendency to reset itself to default values if the computer is removed from power and later restarted. By removed from power, I mean pulling the plug out of the wall or killing the power on the power strip. When you do that the battery has to deliver power to the bios setup memory. If it fails, you lose that info and the next time you power up, the bios will reset itself to its default values. If you made changes in your bios setup you can check to see that they are still there rather than the default values. I agree with mtweidmann that it certainly sounds like a hardware problem and apparently one that is only bothering Mandrake and not your other OSes. That could point to a hard drive problem with only the area of the hard drive where Mandrake is located being affected. If you know the make and model of the drive, you can download a diagnostic utility from the manufacturerer's website. Basically, you just download the proper utility, click on the downloaded file and you are prompted to insert a floppy. The diagnostic utlity is then copied to the floppy which you can boot off of and run diagnostics to thoroughly check out the drive and repair bad sectors if necessary. One thing that might help narrow things down is if you could identify where in the boot process the system freezes while booting Mandrake and any error messages you get.

You may want to repost this on Networking. You'll probably get more help from people that know what they are talking about. As I am unfamiliar with DSL configuration in general and your hardware in particular, I can only state the obvious, most of which you appear to have done. One thing though you might want to take a look at. You are getting an error message referring to line 150 of /usr/share/speedtouch/speedtouch.sh. Try opening up this file with gedit or kedit and see what's at line 150. It might give you some idea what's going on. Also, if changes were made to this script, there may be a backup, probably in the same directory. They usually appear with the same filename with a .bak extension. If it's there you can compare the two files to see if anything has changed. You can also try renaming your current file with a .new extension and dropping the .bak extension on the backup and see if you can get running with the backup file.

If you have Partition Magic on floppies, you can delete and reformat with that. If not, you can download the hard drive utility from the manufacturer's website and do a low level format on the drive which will zero fill every sector of the drive. This wipes the disk completely clean and you will then be able to partition the disk with windows fdisk.

I have no clue as to what the error messages mean. The only thing I can suggest is to completely recyclye power i.e. shut down everything, pull the plug out of the wall, wait a few minutes and then try again. I've found that sometimes it's the only way to get cranky USB devices working. Also try setting security settings to the lowest possible settings. Did you have internet access after your install of CUPS and shorewall and only lose it after you booted to windows and back? It's not clear from your post.

i don't know what you've tried already, but the first thing I would do is check it out in Mandrake Control Center>Network & Internet>Connection. Under the State field in LAN configuration, see if it says "up". If not tick the Expert Mode button>Configure Local Area Network and try to activate it. Also see if it's configured to start on boot. If you want to start from scratch, you can reconfigure the LAN and internet connection by clicking on the Wizzard button and you will go through the same screens that you did during the install when you configured your internet connection.

I personally wouldn't bother increasing swap unless there is a need. You currently have 128Mb of RAM plus 250Mb of swap for a total of physical memory plus swap of 378 Mb. You are going to increase to 384Mb of RAM which will give you a total of 734Mb. That should be more than enough for most purposes. Try it out and see how much swap you are using under heavy load. I doubt that you will see swap being used that much with that much RAM.

Here's a simple way to do it: http://www.club-nihil.net/mub/viewtopic.ph...5582&highlight= I've been down this road many times and this is a pretty straightforward way to deal with the problem of booting multiple linux distros. It is certainly possible to have multiple linux distros on your bootloader. What you have to remember is that at boot time only the partition from which the bootloader was installed will be mounted and recognized so you have to copy the info for booting the other linux distros to that partition. The above link describes how to do this by copying the boot floppy info to the partition mounted at boot time. Create a boot floppy for redhat and reinstall the mandrake bootloader by using the install disk CD1 in rescue mode. Then follow my procedure per the above link for creating a redhat entry in your mandrake bootloader.