qa1433

That just it. I do not get errors. paul

Hi all, Not sure what I have done. All was well until I installed wine-config-sidenet and configured it. Then one user could not log into KDE. All users (root, z100 & guest) can log into KDE. However, qa1433 cannot log into KDE. However, qa1433 can log into Fluxbox. When qa1433 tries to long in to KDE it acts like it is going to bring up KDE but then returns to the initial log-in prompt. I tried renaming the .kde to .kdeold so I would not lose anything. I re-login to see if that fixed it. It did not. I checked that all permissions are correct for the qa1433 home folder. They are correct. I am sure there is some file(s) that got modified for qa1433 as qa1433 was the user that installed wine-config-sidenet. Is there a profile file that is used for each user. If so what the name. I can vi it to fix the problem. Does anybody know what file I need to look at and change to get qa1433 able to log into KDE again? Hope the above makes sense. Any help you can provide is greatly appreciated. Thank you, Paul (qa1433) [moved from Tips & Tricks by spinynorman]

Thanks Folks, I will give it a try later when I get home from the office. paul 8)

Ixthusdan, Thanks for the reply. Here is my drive partition brakedown. hda1 = Win 98 (Windows C) hda5 = Win 2K (Windows D) hda6 = JAMD Linux hda7 = Mandy 9.1 If I remember correctly, during the Mandrake install, I had the opportunity to state where I wanted the bootloader to be placed (MBR, /root partition, or a floppy). I inserted my floppy and chose floppy. It did not make the boot floppy. It just went directly to Summary. In the 8.0 version the installer actually had an option of making a boot floppy. It worked flawlessly. It was not clear to me that I would have to separately, invoke an option (possibly only in Expert mode) to make a boot floppy, for emergencies. As Kool as the installer is this may be a weakness. Or maybe better yet, I didn't understand the option. :o If you have a functioning linux bootloader, then boot to your favorite distribution and edit lilo/grub. That said if I understand your above statement that even without the bootloader floppy I should be able to Boot Mandy from GRUB once I modify the GRUB file to include the hda7 (Mandy 9.1 partition)? Is that correct. Please forgive me for trying to be so exact, but the box that I am fussing with is my wife's. If I blow it up, I will never hear the end of it. You know how wives can be? :?: :shock: and Um Valpo Indiana awy! I was born in Muncie, IN. Been in Dallas since 81. Thank you in advance for your help! :!: paul 8)

So I want to make sure I understand this correctly. if I use the CD1 install disk as rescue disk, I can: 1.) install lilo 2,) make a boot disk 3.) un-install lilo 4.) Boot Mandy 9.1 from floppy My original grub boot-loader is left intact so I can boot win 2K & JAMD Linux? :?: I just do not want to loose my grub boot-loader as it work perfectly. Later, I will want to add Mandy 9.1 to my JAMD grub boot-loader. Thnaks for th help, paul 8)

Well on my install it never really made a boot floppy. So hda7 has mandy on it but I have no way to boot it. Any ideas? Thanks, paul 8)