danleff

Quote: At first I am able to see the window where it ask preference of boot in What are the choices of logging in that you get and which are you choosing? This is a very old version of SuSE and I need to search my memory banks. I'll take a wild guess and say that you are attempting to login at disagnostic mode or console mode. Try choosing the first menu option. If you get the same response, try typing in startx (hit the enter key) at the command prompt.

This virus dates back to 2002. I'm no expert on this, but it looks to me that the virus affects older versions of Apache and OpenSSL. I doubt that this is a problem for most users, given it attacks older Apache Web Servers and obsolete OpenSSL.

OK, here is a quick draft of my article. Page 2 should be of interest to you. dual boot with sata and ide drives.

To make a USB bootable DSL pendrive, you need to make the pen drive bootable, not just copy the files off the cd. See the wiki page here. Note the instructions; Quote: From within the DSL main menu, it is possible to create either a USBZIP or a USBHDD formatted pendrive with DSL installed. Just choose the appropriate install method and follow the prompts. Most USB pendrives are located at device name "sda" after they are plugged into the USB port. You also need to be able to boot from usb. See your bios manual for the options available for your system. Again read the wiki instructions. But, you want to boot off a floppy, so see the wiki page located here for directions about making a bootable floppy to boot off of USB. What I was referring to about directions for the secure option in Linux, was related to your statement; Quote: If I click on that, I get two folders...one for Windows and one for Linux. Clicking on either one of them, I get a README file explaining about how to set up a Secure Drive. . The reference to the Lexar site was for information about how the secure drive is set up and why only the public folder is seen by Linux. The drive is apparently only set up for write access from Windows in admin mode.

Look at this article. For more information, see this article as well.

Ahhh...a JumpDrive Secure drive. Go to the web page for your stick here and you will get the answers to all your questions. Your drive is set up as secure for Windows XP or 2000 as admin. You can read the "Public" folder and no others. Read the readme files to set it up as a secure device in Linux. Otherwise, you should copy these files to a safe place and you can format the drive for general use if you don't need the secure features. Again, read the JumpDrive faq page.

Is SuSE trying to see the drive as a fat32 or fat16 partition? Most jump drives are formatted as fat16. I just tried it in SuSE 10 beta. It shows in fdisk as fat16. I wonder if it is mounted incorrectly, hence the "disk full" message. Look at dmesg and see if you get some output such as mine; Code: USB Mass Storage support registered. Vendor: USB Card Model: IntelligentStick Rev: 2.02 Type: Direct-Access ANSI SCSI revision: 02SCSI device sdb: 522432 512-byte hdwr sectors (267 MB)sdb: Write Protect is offsdb: Mode Sense: 0b 00 00 08sdb: assuming drive cache: write throughSCSI device sdb: 522432 512-byte hdwr sectors (267 MB)sdb: Write Protect is offsdb: Mode Sense: 0b 00 00 08sdb: assuming drive cache: write through sdb: sdb1Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0 So you would mount it as such; make a mount point, say /mnt/flash (as root user) mkdir /mnt/flash Then; mount /dev/sdb1 /mnt/flash Where in my case the device is sdb1 and my mount point is /mnt/flash.

Take a look at the sound faq on the Debian wiki. This may help. Remember, if you updated the kernel, you must reinstall alsa, which I assume you are using. Which version of Debian are you using? Sarge...?

Did you check or ask this question at the ClarkConnect forums? You are more likely to get a direct answer. It looks like Promise had Linux source drivers for RedHat 8 and 9 and SuSE, but it looks like somethng for an experienced Linux user to try. They had the usual disclaimer "we do not provide support...". I can only guess that support is built into the kernel (2.6.9) or as a module, but they might be the best folks to check with.

Puppy Linux does this with a floppy boot disk. Apparently, DSL can do this as well. I suggest that you ask on the DSL forums, so someone can directly give you a valid answer. But I did find this post about this same issue. Look at the last post from cbagger01.

I think you will like the new SuSE release. I am using the beta 2 version. No problems yet. Until October 6th...

Is there a problem with your current samba? You need a newer version than this?

Nice work guys! Or...you can try SuSE 10 beta 2 or RC1 now and see if it works. 8)

I just looked at your motherboard manual. Very interesting and completely different from my Asus board. I also did a windows installation on my sata drive. I will post my results with a link to my web site and web page on the subject. Your motherboard manual states the following on booting; Code: Hard Disk Boot Priority: This item selects the hard disks booting priority. By pressing <Enter> key, you can enter its submenu where the hard disks detected can be selected for the booting sequence to boot up system. This item functions only when there is the option of [Hard Disk] in any one of the First/Second/Third Boot Device items. Bootable Add-in Device: (For IS7-G and IS7 only) This item allows you to select the add-in device among the [PCI Slot Device], [OnChip SATA], and [Onboard SATA] channel to serve as the bootable device listed in the item “Hard Disk Boot Priority”. If you don't mind booting from the ide drive (which windows is on right now), I probably have a solution. Give me a little while to settle this out. But, probably the following; 1. Is the current hard drive with Windows on it set as the primary master IDE hard drive? 2. If so, you can run the rescue mode of Fedora, chroot to the sata drive installation and run; Code: grub-install /dev/hda Assuming that grub had the drive originally chainloaded as +1, windows will be a viable option, or you can add it to grub, once you are up and running with Fedora. But let me re-read your posts more carefully, as this is getting a little complicated.

The boot order is controlled by the bios, not the designation of the drives per se. By removing drives, the boot order does not change. You must change what drive to boot from in the bios, whether it be from sata or an ide drive. What motherboard is in this system? Or, if this is a Dell or Gateway system, post the brand and model system. I would avoid unplugging and plugging in drives, as this will confuse the issue, as well as each install that you do, which teels either grub or the Windows boot.ini what drive to boot the OS from. Consult your motherboard's manual for bios settings. By default, most bios' are set to boot on the Primary Master drive, or hd0. You can change this in the bios itself. With the bios set up this way, all ide drives are detected first, then the bios looks for any sata drives on the system. The sata drive is not moved up in the detection tree, but rather you tell the bios what drive to use to boot your system. However, the point is that you want all the drives that you want to use connected, so Linux can detect all the drives and make the grub device.lst to offer you what drives to boot each OS from. If all the drives are not attached, then grub will not add these drives to the list as options to boot any given OS from. You can always change grub to boot all you OS installations, once you decide what you want on each drive. there are various methods to do this. Make a decision what configuration that you want, booting from an ide drive, or sata. Then you can move to install Windows and your Linux distro(s) on your system. Generally, Windows should be the first boot device and installed as such. This makes things a bit easier. I have not done a pure sata install of Windows yet, but may do so this weekend for the experience.

You will get a lot of opinions on this, but basically Windows wants to be the first OS on the system. Unless you know what you are doing, it is best to install it on the primary master drive on the system. Remember, sata is not designated as Primary master......like ide drives. My system is as such; Primary master ide drive - Windows Primary slave - data drive and/or Linux installations Sata drive - Many Linux distros If the sata drive is the only one on the system, Windows should have no problem. Any drive that you use for windows needs to have a filesystem (NTFS or fat32) on it. Writing zeros clears all formatting and windows can't see the drive effectively to do an installation. You need to have at least one active partition on the drive, say fat32 or NTFS. So, you also need to put a filesystem on the drive that you want Windows to see and install to. Since Windows will not be your main OS try the above and... 1. Install Windows on the Primary Master ide drive 2. Install Fedora on the sata drive, or if you have room, the Primary master, telling Fedora to use free space from the NTFS of fat32 system. Otherwise, if you want, preformat the drive with space at the end for Linux on the ide drive, using some utility like PartitionMagic, to resize the NTFS volume or make an ext3 filesystem. Then tell Fedora to use this for root. 3. Install Grub during the Fedora installation to the MBR, or hda, your Primary Master drive. You should get a dual boot environment that will boot both Windows and Fedora. Again, each drive that you use to install an OS needs some sort of filesystem on it, at least one, for the OS to see the drive and use it. Windows or Linux will not recognize a blank, zeroed drive without at least one filesystem on it. Say you only pre-formatted the primary master with NTFS and left some empty non-formatted space for Linux. This is fine. When you go to install Fedora (if you choose) on this drive, fedora will give you the option to install on the free space that it sees afyer the NTFS filesystem that Windows is installed on. Do not re-format the data drive, as this will erase your data on the data drive. Leave this drive alone and your data will be intact.

I have two very reliable boards, the Asus A7n8x-E Deluxe and the Soyo Dragon Platinum Plus. Both support AMD Athlon XP processors very well. Make sure that you know what type of processsor that you have and that it is supported, either the Thoroughbred or Palomino, or if both are supported. They can be had at a number of vendors, such as Tigerdirect. You should have no trouble finding a motherboard to meet your needs.

Once you zero write the drive, set it up again with the Maxblast utility as a data drive only. Then install Fedora and write grub to the MBR, which should be hda, your primary master drive.

I also found the Linux compatibility tests for this model here, which states that there is no compatibility with RedHat, SuSE and Mandrake. Of course, these results may not be totally up-to-date.

Just to clarify, are you using PINNACLE Studio 9 EASY CD CREATOR under Linux or Windows? ...and are the errors occuring under Linux and not Windows? What distro of Linux are you using?

Floyd; Before you get an answer from Maxtor, did you check the bios settings to make sure the drives are primary master and slave? Without confusing things any more, realize that you still have an MBR on the Windows drive (primary master) and there is no need to reset this. If this is part of the confusion, realize that when you changed the cables, the boot.ini may be looking for the Windows files on the wrong drive designation. This was the source of the NTLR not found error. This can be fixed. Is the bios set up to boot from the primary drive or secondary drive? And you are booting fine into Windows now? Are you using the Maxblast diskettes or CDROM version? You can use Maxbast to "zero write" the slave drive to wipe it and start over, if necessary, using the Maxblast maintenance option. But what I want to prevent is making a mistake and overwriting or wiping your MBR on the Primary drive. Especially if you do not have a full version of XP to repair the MBR. Do you have a full version of the Windows XP installation CDROM? Here is a link to the Maxblast tutorial for reference; Maxblast tutorial. We can also probably fix the Fedora Grub installation with a little work.

A little more information would be helpful. What distro of Linux are you looking to use and what hardware other than the mothertboard do you have that you would be looking to use with Linux? It is rare that someone might have the same motherboard right now, given the hundreds of boards out there. However this article seems to indicate that you should be OK.

Quote: 1) Not a Gateway of Dell system, I built this one myself: Abit KV7-V Motherboard, AMD Sempron 3000+ CPU etc (see above) OK, good. I just wanted to make sure. Some folks actually post the motherboard model of their Dell systems. On your point #2, the Windows boot.ini file, just like the grub file points to the Windows system files to start the system. Switching the drives confused the boot.ini file, which was still pointing to the secondary master (if that was the drive designation when you installed windows originally). I am actually surprised that clearing the bios solved the problem. This is why you got the stop errors. You switched the hard drive cables and the boot.ini was still looking for the Windows files where Windows was originally installed. Your last post reminded me of a possible problem with the Maxblast software. You usually get two choices on how to format the new drive. The first choice is if you are adding an operationg system to the drive. This choice should only be picked if this is the only drive on the system, or you are replacing the master primary drive to prepare it for a windows installation. You should pick the second choice, use it as a data drive. This prevents the drive from being set up as a boot/master drive, where the MBR is. I bet grub got set up on the slave drive, if you picked the first choice using the Maxblast software, which set the drive as active boot. Quote: Did I solve that problem by clearing the BIOS after re arranging the Hard Drives to Primary Master and Primary Slave and reinstalling FC4? Yes, for this most current installation. The drive and it's partition should have been detected at their current locations. Let me think on this one a little more. But, make sure that the drives are also jumpered properly. There is no jumper on the slave drive, correct? Look in the bios to make sure that the drives are detected, as you expect. I would correct the problem with the slave drive, if you picked the option in the Maxblast software to format the drive to use with installing an OS. Make sure that Windows continues to boot correctly after this with no adjustments to the bios. Finally, currently, the boot order in the bios is pointing to master hard drive or to the secondary? Of course, the proper thing to do, would be to set the ide cables just the way you had them from the start, making sure the jumpers is correct for master and no jumper for slave. Especially if Windoes boot is still causing a problem. Then we can go from there.

Quote: Actually, I am posting this from MEPIS. I am impressed with this one. However, it looks like I have to pay to get a harddisk installation done with root access. No, you don't have to buy it to install it on the hard drive. If you are signed on as demo user and pick the "install me" icon, the install will prompt you for a password. The password is root. The installation should then continue without incident So, Fedora does not like the system configuration of the Dell. At this point, I don'r know what else to suggest. The only other remote possibility is that the iso files did not completely burn properly and the hardware is not the issue, rather the disks, which caued some files not to be written correclty to the hard drive and gave you the fits during the install. Telling Frdora to ignore the hardware bypassed the problem. At least for the installation. What speed did you burn your iso disks at? ISO images need to be burned at 4X or 8X, no fater.

Just as a note, fedora Core 4, Mandrake 10.2 and SuSE 10 (beta) support the Gigabit Ethernet onboard cards well. In terms of wireless, I found this thread.