danleff

Yikes! Before you try a win 98 boot disk, what version of windows do you have on the system? If you have Windows XP. where is the FC2 partition relative to the windows partition. In other words, what is the partition structure on the hard disk for the distro installs that you currently have? You were using lilo as the botloader? Which distro is using lilo to boot your system? You may still be able to recover lilo as the bootloader. I assume that you did not make a boot floppy disk for FC2?

4.2. How do I run GUI (X11) programs as root? Gentoo has a security limit on XFree that only allows the same user (from the same machine) use the X server. To run X11 programs as root you must first use the command xhost (xhost localhost) to give other users on the same box permission to use the X server. $ xhost localhost $ su - # kcontrol & # reference

Take a look here, which may give you some ideas.

Don't have a an Athlon 64 bit CPU, wish I did. But, note the other threads under the "related threads" below. This will give you some ideas on what to watch for. I suggest that you make a small fat32 partition on the drive keeping the NTFS partition away from the Linux partition on the hard drive. There have been issues with the Fedora partitioning utility and NTFS partitions. Or, set up your partition(s) for Fedora ahead of time and install to the previously formatted partition(s) that you made for Fedora. Especially if you have a system that came pre-loaded with Windows, and you do not have the XP install cd. Also make sure that you defrag the XP partition before installing Fedora, to assure that there is no data on the end of the NTFS partition.

I think that you are on the right track, depending on the distro. I have found various results, depending on the kernel that I am using. For the 2.4 series, the drive is detected as a scsi device, which has nothing to do with the fact that it is a ide or actual scsi device. Yes, the new versions of cdrecord are supposed to work, but, as I noted, not always. I still had to pass the ide-scsi option to the kernel on boot. It also depends on the burning software that you use. what burning software and version do you use? If K3b, take a cruise over to the forums there and you will see some posts on this subject.

OldSpiceAp, you have the sb0200 model? Many have problems with it, as it is a legacy card. There are many variations of the SB Live card, dozens in fact. Not all of them are stock SB compatible with the older alsa emk10k1 driver, or for that matter the OSS driver.

This may very well be the issue, needing to install from source. The support for this card is only in Alsa 1.06.

After a quick google search, folks have been able to use this drive in linux. What burning software have you tried? I can think of a couple of issues. What linux kernel is in your distros? The 2.4 or 2.6 kernel versions? Try this also, at root terminal user, type in; cdrecord -scanbus (hit the enter key) and what output do you get? Something like; Cdrecord 1.9 (i686-pc-linux-gnu) Copyright © 1995-2000 Jörg Schilling Linux sg driver version: 3.1.22 Using libscg version 'schily-0.1' scsibus0: 0,0,0 0) name of burner Or something like that? If using a 2.4 series kernel you may need to pass the scsi argument to the kernel at boot. Let us also know what distro that you tried this on, as well as the kernel series.

Just to clarify, I am running Mandrake Community 10.1. You can install the new Wine version on your current Mandrake install from Sourceforge Your current version should have done the same thing, if it is a post May 2004 version. If you choose the new version, I suggest un-installing the old version of wine and then install the newer one. Mandrake will use the libwine files from your current version that came with Mandrake. You may want to try the latest version on your system to see how it works. There should be no difference between wine running in 10 vs. 10.1. Again, I modified my install with dcom and the windows scripting files which may explain some of the reasons why it is working better on my system. This app. allows the install to proceed and may have dll files that GSAK needed. Just my take on it.

Understood, but my comments were about your boot order in the bios. If the boot order is not set correctly, or set at all in the bios, then the usb-cdrom will not be probed to boot. The model or make of cdrom device should not matter (unless it does not comply with standards), but if the laptop's bios is set to boot from usb-cdrom. Disregard this if you already checked the bios boot order.

I just installed the latest version of Wine on Mandrake 10.1 (version 20041019)from Sourceforge (rpm). When I ran wine without any arguments, it created the folders in my .wine directory. It looks like Wine now does this for you automagically. I'm used to needing to run the old winesetuptk to do this (obviously from older versions pre May 2004). The folders that you should see in the .wine directory would be; dosdevices drive_c If you do this from root user, then the directories are created in /root/.wine. If you run it as regular user, then you will see the directory structure in /home/user/.wine. The drive_c directory contains all the regular windows folders that you would expect to see, which is your fake wine drive. I just installed the GSAK program and it works fine from what I can tell, however, it does not like the file structure totally and does not link to the browser correctly. Of course, I installed dcom98 and the windows scripting programs, which may explain some of this. These are required for some other win apps, such as Dreamweaver MX and Nero. The upshoot of this is that while it works fine for me (possibly due to recent changes made in Wine), it still will not probably do all that it should. I get no freezing on closing and such. I use Crossover Office, which costs, but runs Office 2000 and other apps quite well. Acrobat Reader 5.1 runs well and even put an icon on the desktop for me. Interesting, some changes seem to have been made, but clearly not enough to install and run most win apps easily.

If you already have a usb cdrom drive, do you have the bios set to boot from usb-cdrom as the first boot choice? While it is possible that it may be an issue with the usb cdrom, often folks fail to set the bios correctly to boot from usb-cdrom as your first choice. If you have it set this way, make sure that the usb-floppy is not attached when you try to boot from the cdrom. Also, what are you trying to boot from the usb cdrom? Is it a bootable cdrom disk, such as an iso image that has been burned as an image to the cd?

Try disabling the onboard nic in the bios, boot up Mandrake and see if it gets picked up. If not, when in Mandrake, go to start-->system-->configuration--> configure your computer. Click on the Network & Internet, then Manage Connections. See if the Realtek is listed. If you need to get this far, let us know what you see. Also look under the Options tab and see if start at boot is selected. If not check it and save the changes. If you still have no luck, let us know.

Yes, true, this works well, I think if the kernel image is all that is installed. I agree with Dapper Dan, Synaptic is the way to go. He can give you specifics on fedora and synaptic installation and use. But, I would keep it around, just in case something goes amis with the new kernel, as a backup to get into the system. You can change the order that the most recent kernel comes up easily with either Grub or Lilo, which ever boot manager that you are using, if this is a concern or preference.

zero0w, as soon as I clicked on your link, the bell went off on your post! Let's see if we can get blackhawk3d some directions on how best to do this in fedora.

Is this a Dell system, or a Dell Legacy SB card on a generic system? Do you know the model number (it is on the card itself). This seems to be the root of the problem. Alsa does not like some of these Legacy cards. I had one of these and never got it to work correctly. You should have alsa already installed in Core 2. If you type alsamixer in a terminal window as root, do you get the mixer window? See if the volumes are set all the way up, or nearly so. If not, try increasing the volumes. Another post also noted that a fix was to run alsa_init in a terminal window and the sound came up. If you could post what web resources that you used to address the issue, this may also help us see what suggestions were made.

Were you trying to run sax2 from the command line, or from the icon on the desktop. That was what I was trying to get at. I don't have Yoper on my system now, so I can't remember if sax2 pops up a terminal window or not. If it did, apparently the message was helpful. What I do remember is that Yoper was finicky about running as root user (yoper) vs. an added user. Perhaps you can post what the fix was, so that others could benefit fromwhat worked for you. But I'm glad that you figured it out on your own! You may want to post Yoper based questions on their forum, which is where my link guided you to. The forums are pretty active and have a lot of solutions and bugs/fixes posted.

As the directions note; Quote: Go to Yoperconf select sax2 display setup go to input devices select mouse, and go the third tab and click enable mouse wheel So, go to the control panel (Yoperconf) and try the directions from there.

I just installed Mandrake 10.1 on my test system using the hard drive install method and the cdrom boot image. It worked very well. The issue is that you need to keep track of what the order of the partitions that you created, so yu know where to point the installer to. I bet the mistake that you makde was to point the installer to the correct drive, but failed to tell it the directory that the iso's were in. Say, if they were in a directory named "isos", then you would have to point to /isos. If the isos were just in the root directory (not in a sub-directory) then you should have typed /, which designated the root of the partition. Just for clarifcation, did you give the exact order of you partitions above? in other words, was Windows installed as the first os on the system? If so, than it should have been on the first partition of the drive. Or, did you resize partitions, or move the Windows partitions to make the swap partition...? In terms of burning cd's, the common error is to burn them at too fast a speed. Do not burn them at the top rate of the cdrw drive. Use 4X or 8X speed. I also noticed that you spoke of dvd? Did you burn the previously failed iso's on cd or dvd? The other issue, is did you just burn the iso to a cd, or did you burn the image? if you burned just the iso file, then you would see just the iso file on the cd after the burn. This would, of course, be incorrect. but I doubt that you did this, because you burned a boot sio to try the current install, correct? I use Nero all the time, which is a fine program. However, another good choice for Windows XP is CdBurner XP Pro It does a very good job and is free to the user. BTW, I noticed that you accidently started another thread, Do you want that deleted?

Take a look at the Yoper forum article on this subject here.

I agree with Dapper Dan. Wht not use cdr media to do the install? By the way, there is no disk geometry issue if Windows is on a fat 32 partition, only ntfs. You should also have the iso images instaled on a different partition than what you are installing to, not the same one. Are you using a floppy image to start the install? Also, are you designating the partition, as well as the directory that contains the images? To give an example, I will post a screenshot, or better yet look here at figure 3-3

Quote: It is supposed to work under Linux, using WINE. Well the website states that it is reported to work under Wine, but it is not supported by the maker of the application. What this means is that some have gotten it to work, probably with some trial and error. What is missing is what version of Wine that it is reported to work with and the method of getting it to work. A quick google search did not reveal too much, but I can look further. I assume that the version of Wine you installed, was the Mandrake version that came on the install cd? There are no quick and simple guides that I have found on Wine. It takes a little getting used to. I have messed with it for some time and getting many Windows based apps. to work on it is difficult. A good site to get an idea of the complexity of Wine is Frank's Corner. Are there any other Windows based apps. that you are looking to run under Wine?

Most recent distros have no problem with these mice, I have a Logtech optical and it works fine. What distro and version are you using?

What Linux distro are you using and what version? Scanners are usually configured and run by the packages sane and xsane, which are usually included in most distros. There was a previous on this scanner by shadowmatrix here, which did not look too promising. Is yours a usb or parallel model?

If you want to just use the fat32 (vfat) partition for storage of files, you can leave it as is. Linux will be able to read and write to it. If you really want to change it to a linux filesystem, say to expand your home partition, you can do so, as long as Linux is on a logical partition. I agree with Dan, Qtparted will do the job for you either way. It will, however, not touch ntfs partitions. Is your distro on one large partition, or does Ubuntu install on multiple partitions? I'll look at the Ubuntu page later and see what i can find.