Jump to content

chris z

OTW
  • Posts

    951
  • Joined

  • Last visited

Everything posted by chris z

  1. chris z

    kde 3.1.4

    hmmmm........ if nobody figures it out by the time i get home from work tonight, i'll give it a looksee & post back with what i came up with. (damn Windows at work....) Chris
  2. chris z

    kde 3.1.4

    i'm not at the Linux box right now (work..... ) but, to edit/manipulate the KDE right click menu, i'ts something like this........... KCC->look & feel->behaviour....... or KCC->desktop->behaviour......... i know it's one of those , or in KCC->look & feel somewhere. once you find the right click options in there, you need to disable the predefined KDE right click options & then you'll be able to create your own in the same area. Chris
  3. silverpenguin.......... as dragonmage noted, you are using a beta of Moz, so it's bound to be buggy. if you scroll down a bit in the software forum here, you'll see several Mozilla/Java problem related threads. read through them & you may get a solution. a couple of quick thoughts though........ it's not wise to install a newer version of Moz over an older version. did you first uninstall your Moz1.4 & delete the Moz profile in your home directory before installing Moz1.6? Moz is notorious for having Java incompatability issues. you need to make sure you have the correct GCC libraries & the correct verison of Sun Java for certain builds of Moz. here's a link to the Moz1.6b issues/bugs page....... Moz1.6 beta issues here's a link to Moz1.6b Java installation instructions........ Moz1.6 beta read me scroll down to where it says "java, plug-ins, & other extras" for Java specific info. Chris
  4. chris z

    SCSI Emulation

    you don't want to edit that line! you want to edit the append line 2 lines below that, using the syntax i stated above........ the line you are refering to with hda9 is one of your linux partitons, not a cdrom drive. hda would be your hard drive (like c:\ in Windows) the 9 is refering to one of your linux partitions (like /usr /home /root etc.) splash=silent is refering to your boot splash screen (i think???). so, what you need to do is not touch the hda9 line, and make the append line below that read as i stated above. gotta get back to work now........ Chris
  5. chris z

    SCSI Emulation

    yorneb.......... you need to have the info all on one line like this........(this is my lilo.conf) look for the bold letters....... you have your scsi info on 2 separate lines. put it all on one line like my example above, substituting your own drive letters (hdc & hdd). EDIT: ok, i was just looking at your lilo.conf again, now that i'm not in a hurry to get to work. here's where your mistake is in your lil.conf........ you have hdc listed twice & also you have 2 lines instead of one. yours should read like this, all on one line...... append="devfs=mount hdc=ide-scsi hdd=ide-scsi acpi=off" if indeed your cdrom & burner are hdc & hdd respectively. and remember, BACK UP a copy of your untouched lilo.conf if you haven't already. better safe then sorry later. ;) Chris
  6. chris z

    Mouse is really odd

    what DE are you using? if you're using KDE, go to KCC->peripherals->mouse. there's a bunch of mouse settings you can tweak there. Chris
  7. Akai........ have you looked into this..... Epson Stylus Color 680 drivers for Linux or, if that doesn't work, try this....... Google search for Epson 680 printer drivers for Linux Chris
  8. 2 things......... what command are you using when you try to run Moz from terminal? if memory serves me, the command isn't just mozilla, it's something like ./mozilla or ./mozilla.bin. if you check the Moz website, it tells you the exact command in the install guide for Moz. also, you didn't answer my question about installing over a previous version of Moz. since you did uprmi.update --auto-select, i'm assuming you did. if that is the case, it could be conflicts between different versions of Moz causing your problems. along that line of thought, have you tried uninsatlling Moz completely, every last bit of it, then reinstalling, & finally tackling the plugins? if you haven't, i'd suggest giving that a go, because as bvc said, the Java rpm is pretty much fool proof & should work without any intervention on your part. Chris
  9. Gowator....... isn't there any way that you can enable winpermissions for yourself & try installing from the executables? i have no experience with Lindows or how that works, but it may be as i said before........there may be other files involved that are embedded in other directories other than the one's that i could find & sent you. if ya need anymore, i still have the 2 programs on my computer here, so let me know. good luck...... Chris
  10. chris z

    SCSI Emulation

    smartjak......... i'll break it down as best i can....... lilo is your bootloader. lilo.conf is simply a text file for lilo, listing the choices you have to boot your computer (ie: boot into windows, linux, failsafe mode, etc) & that also contains some info as to what to load when booting into one of those choices (ie: where the kernel is, which kernel, where your drives are, etc.). the problem you (& other people, including myself at one time) are having with burners, is that most burning programs don't recognize an IDE (integrated drive electronics) drive. i won't bore you with the technical details of what IDE is & does & how it works. you can Google for that info if ya like. SCSI stands for small computer system interface. again, you can Google for the info. in a nut shell, it's 2 different technologies used for running drives & making them recognizable to the computer & various programs that use them. back to lilo......... one of the things that lilo tells your computer is what type of drives (hard drive, floppy, cd, dvd, etc) your computer has. more than likely it's gonna have ide drives amongst them. so, when a program (such as k3b or other cd burning apps) don't recognize ide drives, you have to tell your computer to emulate the ide drives as scsi drives. which leads us back to editing a line in the lilo.conf to tell your computer to do just that. so........ being that lilo.conf is simply a text file, you need a text editor to edit it. you can choose one of the multitudes of text editors out there. kwrite, kedit, kate in KDE, for instance. you can use any of the gnome editors, or even VI in terminal mode. you just need something to use to edit that line in your lilo.conf file. IMHO, the easiest way to do this is thusly.... i'm gonna show you how to do this the easiest way using KDE as your DE. if you use Gnome, or something else, then just substitute the appropriate apps with what you use. open terminal-> su to root-> type kdesu konqueror-> hit enter-> **** note: you need to have root privileges to edit the lilo.conf file. hence logging into KDE super user mode to access it. if you're using Gnome, et al, you'll need to acces the lilo.conf file with whatever root method you use in those DE's. **** this will open the KDE Konqueror file manager in Super User (hence the kdeSU part) mode. in this mode, you are essentially root & have all the powers of root, so pay attention as to what you're editing & such. now, with KDEsu opened, navigate to your /etc directory-> find the file called lilo.conf-> since it's just a text file, you can just click on it & the program associated with text files will automatically open it, or you can right click on it & open it with the program (text editor) of your choice. okay.......you have the puppy opened. now, scroll down until you see the in the first section where it says image=boot/vmlinuz. that's your default linux installation that you boot into. below that, look for a line that says something like the following.... **** note: you can apply this same method to other kernels listed in your lilo.conf that you may use to boot into, if you indeed have more than one kernel version on your computer, as many people do. just look for the same line listed below under the kernel version of your choice in the lilo.conf file. **** append="devfs=mount hdX=ide-scsi acpi=off" that's the line that tells your computer what type of cdrom drive(s) you have. the line above would be for one drive (hdX) saying that the drive is an IDE drive (=ide) with scsi emulation enabled (-scsi). NOTE: the X in hdx will be the letter of your particular drive. it may be A, B, C, or any other letter of the alphabet. it depends on how your system boots, what's slave versus what's master, & the amount of drives on your system. now, to make your second drive (cdburner) emulate scsi, you need to add the following info in BOLD to that line........ append="devfs=mount hdX=ide-scsi hdX=ide-scsi acpi=off" again, with the letter X corresponding to the letter of YOUR drive. spaces (i know) & cap sensitive (i think) counts here, so make sure you get that correct. after you do that, save the file as is. do not rename it or your system won't boot. close kdesu. now, to make that change take effect, to need to tell your computer that you updated your lilo bootloader. so, to do that, go back to terminal. if you're still root, stay there. if not, su to root. then type the following lilo -v hit enter that is telling lilo to add the changes you made in verbose (-v) mode. you could also just type lilo & hit enter, but you wouldn't see any output. after you type that, a few lines will scroll by showing that lilo is being updated. if it finds anything wrong, in verbose mode, you will see an error message which will let you know things are not correct & give you the chance to go back & fix it. if you don't use the -v switch, you won't see anything so you won't know if it's good or not. now, after that, if you didn't see any error messages, you need to reboot your computer for the scsi emulation to be enabled. so, simply reboot your comp with whatever method you are comfortable with. it doesn't matter if you do it via terminal, or via right click desktop. once you've booted back up, you will need to rerun the setup program for k3b (or what ever burning app you're using) so it can now detect your newly scsi emulated drive. A HELPFUL HINT THAT MAY SAVE YOUR PANTS...... BEFORE EDITING ANY IMPORTANT CONFIG FILE, IT IS ALWAYS A GOOD IDEA TO BACK UP THE KNOWN GOOD WORKING VERSION OF THAT FILE TO ANOTHER DIRECTORY OR EVEN A FLOPPY. THIS WAY, IF YOU REALLY BUGGER SOMETHING UP, YOU CAN ALWAYS REPLACE THE GOOD WITH THE BAD! hope this helped explain things more clearly....... Chris
  11. chris z

    SCSI Emulation

    if you're using LILO, then do the following. open lilo.conf with a text editor of your choice. it's in /etc/lilo.conf. edit or add the following line under the "append" section append="devfs=mount hdX=ide-scsi hdX=ide-scsi acpi=off" (where the hdX should be the letter of YOUR corresponding cd drives.) save the file. after you edit lilo.conf, go to terminal, su to root, then type: lilo -v hit enter, then reboot for the changes to take effect. if you're using GRUB, then i'm not sure about the exact editing info & somebody else could probably help ya with that. Chris
  12. the files you requested have been sent to you via e-mail to the address you provided. hope it works. let me know....... Chris
  13. allrighty then........ give me a few minutes. e-mails will be forth coming....... Chris
  14. tag, you're it! :lol: ok, i think we're getting there. now, i need you to tell me exactly what you need....... i ran the wg511 executable. it created a directory in my /program files. contained there in are 3 more directories. here's what they are & what's in them, with files sizes in () rounded up.. let me know which things you need/want. driver->contains: netwg511.cat(0b), netwg511.inf(21k), wg511dcb.arm(91k), wg511icb.sys(57k) install->contains: install.ini(415b), install2k.exe(45k), install9x.exe(46k), mainctrl.exe(284k), pcarmdrv.exe(44k) utility->contains: wg511wlu.exe(216k) keep in mind, i'm not sure if the executable i ran placed files unknown to me in other locations. it does come with an uninstaller, so if you don't need these or don't want them, i can uninstall easily enough. (thank god for work computers.......the perfect testing grounds!) also, the wg511wlu.exe file is a configuration utility, so i'd think you'd definitely need that. i'll be here at work with access to this stuff until 3:30PM US EST time. if i don't hear back from ya by then, i'm just gonna uninstall this stuff 'cause i'm not sure if it will interfere in anyway with my network here. Chris
  15. yeah, i just got the mail i sent back marked undeliverable. onto wg511......... before i send it, i'm still confused. there are no drivers in that .zip file. there's a 1.5meg executable file & a word doc with info about it. there are no other files in that package. let me know if that's what you want, then i'll e-mail them to you. (at the proper address :P ) if that's not what you need, then i'm back to being stumped again. Chris
  16. Gowator, i just e-mailed you the wg311 driver files. hope that's what you needed. also, the e-mail address you provided seems to be wrong; it wouldn't send that way, so i ammended it to: sl-at-lepeanuts@homelinux.com EDIT although i didn't make note of it in my e-mail, those drivers are for winxp, just in case you were wondrin'. Chris
  17. ummm........ Gowator........ not sure what you're wanting here. i just went to your links for the files. they are simply .zip files. there's no CAB files inside of them. i downloaded them & simply extracted the contents (unzipped them) using WinZip. i'm in Win2K at work right now. all you should need to do is get a copy of WinZip to extract the contents. it's a free program located at winzip.com. if you really want me to, i can e-mail you the contents, but it's over 7 megs worth of stuff & if you're on dial up or your e-mail server has storage limitations, it may be troublesome for you. let me know....... EDIT ps: also, the wg311 contains seperate drivers for win9x, win2k, & winxp. which version do you need? Chris
  18. not sure about your other issues, but with the icon problem, if you're using KDE, see this thread, it might apply to your situation. scroll down a bit in the thread to read my solution........... KDE icon problems Chris
  19. smartjak........... open Konqueror->setting->configure Konqueror scroll down to "java & javascript" make sure the path to java points to where your java is installed. IE: mine looks like this: (your path may differ depending on your java installation. from what you wrote above, yours will probably loo like /usr/bin/java/your current version of java/bin/java) /usr/local/j2re1.4.2/bin/java then scroll down to where it says "plugins" make sure "scan for plugins globally" is checked & then click the "scan for new plugins" button. set the scan to the directory to where you java is installed, or choose one or more of the choices in the selection box. click "apply" "ok" open Mozilla->edit->preferences->advanced->scripts & plugins & make sure all boxes are checked EXCEPT FOR "create or change cookies" make sure you have java enabled. "apply" "ok" still in Moz, click "help" "about plugins" it will show you all plugins installed. it should show Java now. try a Java enhaced web site to test it out. (also, one more note. when installing Java or searching for the plugins in Konq, make sure you are not running Moz at the same time!) gotta get to work now........... Chris
  20. Darkelve........... AFAIK, Opera skins are Opera specific, & vice versa with Moz & Firebird. so, no, you couldn't use a Firebird skin on Opera. Chris
  21. Darkelve........... if you want some cool Opera skins, go here........ http://my.opera.com/customize/skins/ actually, i don't know if it's the same skin you have for Firebird, but Opera has 6 skins in the Breeze theme. check 'em out below.......... Breeze skins for Opera i'm currently using Breeze Simplified. very minimalistic, no clutter, & it leaves lot's of screen space for your viewing pleasure. Chris
  22. chris z

    Java problems

    see this thread for a similar discussion & solutions....... Java & Flash problems in a nut shell, to get Java to work properly in Moz you need to make sure you have the correct version of Java because there are conflicts with certain versions of GCC libraries. to get it to work properly, you need to sym link the Java to the Moz plugin folder & tell Konq the correct path to your Java plugin via settings->configure konqueror->java & java script. here's another link to Moz's faq section concerning proper Java installation. Java plugin faq Chris
  23. you might wanna check if your gcc libs are correct & check into Java issues. i know there are gcc conflicts with certain builds of Moz & Java. any time i've ever had a problem with random Moz crashes or have helped somebody with a problem like this, it always seems to be traced back to one or both of those issues. and since Galeon is built on Moz's Gecko engine, that would only make sense that Galeon crashes too. also, did you try this Moz upgrade over an existing version? that's not recommended according to the Moz faq's & my own first hand experience. if that's the case, it could be a conflict with an older version of Moz or remnants there of. go to the following link for Moz's support pages if you haven't done so already. all of the above things i mentioned are discussed there & various fixes are given. http://www.mozilla.org/support/ Chris
  24. purple illusion!.......SWEEEEEET!!!!!!! :lol: (i feel like a chameleon........changing colours all of the time!) think i'll be keeping this one for a while! thanks! Chris
  25. i'm likin' the cali skin, myself! go mysti, go Mysti.... think you can work something out in a purple & black scheme? B) Chris
×
×
  • Create New...