Jump to content

fuzzylizard

Members
  • Posts

    803
  • Joined

  • Last visited

Posts posted by fuzzylizard

  1. Easy solution, remove all partitions, reformat the drive, reinstall everything.

     

    But I don't that is what you are wanting to do. When you say that you can't boot up anymore, what exactly do you mean? What boot loader are you using, LILO? Do you get the boot loader? Can you boot into Mandrake? Do you have a boot floppy for Mandrake that you can use to boot into it?

     

    Depending on the answers to the above, there is a way that you can boot from the Mandrake install cd and enter rescue mode. this will allow you to mount your Mandrake filesystem and rerun LILO to try and solve the booting problem.

     

    What does it do when you try to boot into XP? Are you sure XP is still there?

  2. There are three places that you need to enter username/password, and they all need to match.

     

    1. Each user needs to be entered as a user in Linux

    2. Each user needs to be manually entered as a user in Samba

    3. Each user needs to use the same username/password to log into windows

     

     

    A few things first:

    1. How is your samba network setup? Is is a workgroup or a windows domain network?

    2. If the network is setup to work with workgroups, are all the computers on the same workgroup?

    3. Have you entered each user manually into Samba? Each user needs to appear in the smbpasswd file.

    4. what kind of authentication are you using for samba?

    5. what does you smb.conf file look like?

     

     

    Here is the biggest thing: Do you have encrypted password set to yes in Samaba? (The fact that you have the win2k boxes logging on indicates that this is yes.)

  3. The best way to ensure that any computer can access your samba network is to ensure that the usernames/passwords that people use to log into the windows computers are the same as the usernames/passwords they are going to use to log into samba. There needs to be a direct one-to-one correlation in terms of username/password.

     

    In addition, each person who is going to log into samba needs to be set up as a user on your linux machine. Once samba authenticates the user based on its password file, it hands the user over to linux which uses its own security model to handle the user from that point on. As a result, this means that each user must be entered into both Samba and Linux as users.

     

    Third, the way that win98, win2k and winXPHome handle things like logging onto a samba share are completely different. This accounts for the differences you are experiencing between the different OS's. The easiest way around this is to ensure that the username/password that the user uses to log onto the windows computer is the same that they use to log onto the samba share.

     

    Whenever you try to access a smb share (samba or windows) the username/password that the user logged with is first sent to try and authenticate that user, only when this fails, does the samba server than try another method of authentication. However, the way that this second method is handled is very different between 98, 2000, and XP Home. (XP pro is the same as 2000).

  4. I don't think there is a way to correct this. There are actually two thing going on here. One is the tab completion, but the second is that you have not entered enough information to make a unique completion. Therefore, bash is giving you a list of all files that match the pattern that you have listed and then refilling in what you already typed.

     

    If you do tab completion on a filename that is unique, and type enough that bash can make a unique match, then you should see the backslashes remain in what you typed.

     

    My guess is that, in your case, another program is stepping in to help the tab complete and it does not reprint the backslashes on screen after it has listed all files that match what you typed.

  5. From the sounds of it, you have more than one computer on the LAN that is called localhost. This tends to be the default name that Linux distros give to computers when you do an install. You will need to go through the entire network and ensure that each computer had a unique name.

     

    As for how to change the name of a computer, if you do a search of this forum you will find numerous threads on that subject. Hint: just go through the network wizard in advanced mode.

  6. another question............

     

    can you/should you leave your /home/.kde directory in place? and, if so, does KDE3.2 retain & use your old personalized KDE settings? for inquiring minds that want to know..........

     

    Chris

    Not sure. I removed my old .kde directory just to make sure that there were no conflicts. Actually, I simply backed it up and changed the name to something like .kde-old. That way, I have access to what was in it. However, I really have not needed it.

  7. First step: Make sure that you are not in KDE 3.1.3. So, logout and login back into gnome, shell (init 3), or some other desktop environment.

     

    Second: attempt to install kde 3.2, this will raise a lot of errors. Open up the Remove Software part of the software packages thingy and remove whatever package is at the end of all those this-package-conflicts with this-package lines

     

    Third: attempt to reinstall kde 3.2

     

    I had to do this about 3 times before I was able to get it to install cleanly.

     

    The trick is that you need to be in some other desktop other than kde.

  8. Wow, was that ever fun!!! :P :angry: :P

     

    Basically had to remove KDE 3.1.3 in order to get it to work. However, I DID get it to work.

     

    In terms of all the dependencies, I simply went into the file manager and removed all the conflicting packages. This seemed to clear everything up. The only package that I have lost is K3B. Other than that, everything went nice and smooth once I ripped out the offending packages.

     

    Now to try and install a newer copy of K3B.

  9. I decided to go with the Kingmax ram. More because the price was right and also because I could walk into a store and buy it. Both important points to consider. I did not go with Crucial because I live in Canada and that would add extra shipping, and other, costs to the total price.

  10. Whatever you do, do not buy a Dell notebook that uses integrated video. Due to a bug in the BIOS, they are a pain in the neck to try and install Linux onto. Supposedly this has been fixed in XFree 4.4, but then no one is shipping distros with the new release, so you can't win either way.

     

    Any Dell that uses a 'real' video card I would highly recommend. I have been very happy with my Inspiron 1100. Only two complaints are the video bios thing and I only got the laptop with 256megs of ram, which is way to little.

     

    Hint: Make sure you get at least 512 megs of RAM with your notebook.

  11. That's kinda funny. It does introduce an interesting question though. Does running Office XP using Crossover Office on Linux introduce any security risks? Just seems to be that you are installing the buggiest, most insecure programs that Microsoft produces into Linux. Does this introduce any security vulnerabilities?

     

     

    I wonder what would happen if you tried to run the install?

  12. I have installed Mandrake 9.2 onto my system, again, and am wondering how I would go about setting it up so that I can connect to more than one wireless network. I have one network at home and one network at school. I have my wireless card setup and running on my wireless network at home. However, I have not been able to get it to work at school.

     

    I have tried to setup different profiles for both home and school. All this resulted in was crashing the network tools. I have heard that there is some kind of wireless toolkit that you can install that includes something called iwconfig? However, I am not sure where to get it. I have tried running iwconfig on my notebook and it does not exist.

     

    Any ideas?

  13. Post here in a few days and a few weeks how it is running. I am interested to see exactly how stable Dreamweaver MX is when running via Crossover office.

     

    Also, what was the install like?

  14. For Photoshop, there is The Gimp. Although, as you say, the learning curve is steep.

     

    As for Dreamweaver MX 2004 - No, you will never find anything on LInux that comes close to matching it. There are a few text based editors that are nice - Quanta, bluefish - but they lack any form of wysiwyg layout ability or any form of project management.

     

    Out of interest, how can you be looking to replace Dreamweaver on your computer if you are looking for a place to download it from?

×
×
  • Create New...