Cardinal

Another way is just edit your bash profile and set the buffer to 1000 lines for example, then tell it to load your profile by default

Hi gents. After using Kde for a while I decided to jump back in to Gnome only to be greeted by these two errors; Clicking restart or close results in an endless cycle of error prompts, they don't go away. I have not done any serious system editing, the last thing I remember doing in gnome was running yum. Any ideas guys?

Thank you for that It works fine. I'll send you some nice Karma for helping me

Thanks for the reply Dan Here is my menu.lst entries. # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd1,0) # kernel /vmlinuz-version ro root=/dev/hdb2 # initrd /initrd-version.img #boot=/dev/hda default=3 timeout=10 splashimage=(hd1,0)/grub/splash.xpm.gz title Fedora Core (2.6.9-1.3_FC2) root (hd1,0) kernel /vmlinuz-2.6.9-1.3_FC2 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.9-1.3_FC2.img title Fedora Core (2.6.8-1.521) root (hd1,0) kernel /vmlinuz-2.6.8-1.521 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.8-1.521.img title Fedora Core (2.6.5-1.358) root (hd1,0) kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.5-1.358.img title Windows rootnoverify (hd0,0) chainloader +1 I'm pretty sure I know which entries to remove, do you think it's worth it? Your suggestion about leaving an entry as a 'fallback' seemed like a good idea. I'm really only doing it improve the appearance of the boot menu. I've been booting with the new kernel for a while now and it seems fine. Anyway, thanks again.

I've not tried IceWM for years, it looked dated and was not very accessible when I used it last. I've not tried fluxbox, can I install it on Fed 2? KDE works well but the themes available are woeful. I think Gnome works well enough and looks quite nice and functional with bluecurve for example. Egorgry, keep the tips coming. Some useful advice there. Is there any way of forcing Gnome to remember window placement settings and or icon views? Sorry to go off topic

Hello everyone. I'm using Fedora Core 2 and updated the kernel with yum. When I reboot I notice an older version of the kernel is still showing in the boot screen. I would like to edit the boot options so only the updated build of Fedora is shown and also XP, that is set up to dual boot. At the moment, I have three options to boot, I would like to change that to only show two. Thanks in advance guys. - Cardinal

Alec. There is no time limit. It behaves like a normal service pack in that regard. It adds the Windows XP security center, which includes a few updates to the firewall and automatic update. It also adds rather useless AV support that try's to detect the AV software you have installed. Speed wise, most reports I have read claim if anything, a general increase in OS speed and more noticeably, IE speed. I think the RC2 is worth the install. I doubt very much the final will be changed much if at all. No problems here. I have tried a few builds of the service pack and finally this one fixes the problem with viewing DIVX files. No app problems yet, and Symantec AV corporate 9.0 finally works correctly. Good luck, though you won't need it. - Card

I agree with Alec's general answer. Times are tough, but mostly this is a boring time to be online. Xp is stale, Linux is going nowhere interesting and relief is far off. By the way Alec, don't be such a defensive moron, you brought this thread way off topic.

Originally posted by ShoGinn: Quote: If You have: "auto-protect failed to load" - try this way >>> Start regedit.exe. Find: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SAVRT Change: C:\Program Files\Symantec AntiVirus\savrt.sys to \??\C:\Program Files\Symantec AntiVirus\savrt.sys Find: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SAVRTPEL Change: C:\Program Files\Symantec AntiVirus\Savrtpel.sys to \??\C:\Program Files\Symantec AntiVirus\Savrtpel.sys That did squat. Any further information on this problem available?

I am going to try a different NIC or two as I have a few spare. I am guessing the cable could be trashed though, which is possible (a slammed door perhaps hehe) So I'll use the hub when I try the different NIC's. Anyway, thanks guys. I've made myself a coffee and am off to play networking. P.S. Crazykillerman, thanks for setting me straight with the crossover/standard cable difference. I was a little confused with what I had written also. But, I got it right in practice, I just made the error in my post

Again, thanks for all the help so far guys The answers: Yes, Both the network cards are working correctly, and are shown to be working correctly in the device manager. (When I say they are working correctly, I mean they show up in the network connections, The lights are working and Windows show's no conflicts or errors) The cable is the only thing linking the PC's. I do have a hub (10/100 switch), But I could not get the network working with that at all. In the gateway PC (the box with the dial up connection) There are two Network connections shown. The dial up, and the adapter. On the other PC, Only the adapter connection is shown. So to answer Alecstaar, Yes this seems to be normal. The cable is a crossover cable. There are no firewalls enabled on either pc. (Including the Xp one) I'll enable Netbios to see if it does anything but as Alecstaar pointed out, pinging just the IP of each computer should still work on a pure tcp/ip right? Damn. So it could be hardware is that what you guys are saying? Oh, Crazykillerman, Is there anyway to setup one of the PC's to act as a DHCP server? Or is that a no no? And why the hell does Windows specify that one of the PC's should have their IP address assigned automatically then? (It did this by running the network connection wizard) Thanks again guys. I do appreciate it. - Cardinal.

Thanks for the reply Alecstaar. To answer your questions. Yes, the subnet mask is set to 255.255.255.0 on Both PC's. Both of the NIC's are showing no problems at all in the device manager. As far as the cable goes, I can't be 100% sure, but it was working fine the other day. Any other ideas? - Cardinal

Hi there. I need help with a simple Home LAN. I am sure this topic has been covered so many times before. However, it has been discussed in bits and pieces with different problems in different posts. I need help from start to finish. Now that I have stated that, please refrain from any unhelpful 'do a search responses'. Now, on to my questions.. I am running a small peer to peer LAN at home. Both PC's are using XP with simple file sharing enabled on both. At the moment, I am using a single Untwisted Cat-5 cable with a direct connection. I do however, have two (or more) standard Crossover Cat-5 Cables and a 5 Port Switch that I tried to use unsuccessfully. I have some minor networking experience with Windows PC's in the past and have tried a few things. I have also tried to use the XP networking wizard ;( that seems to be so useless, and it also seems to fail. Both computers have only the single NIC Installed. 1 Computer runs a simple dial up connection that is not shared. I have set both PC's with an IP address of 192.168.0.1 and 192.168.0.2 respesctively. I have not added anything in to the gateway, or DNS sections of the network properties. Running Ipconfig shows me the following information on the Gateway PC (I'll use the term gateway in this case only to describe the PC with the Internet connection, realising that it isn't actually a gateway in this case) Windows IP Configuration Host Name . . . . . . . . . . . . : mother Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter D-Link Adapter : Connection-specific DNS Suffix . : Description . . . . . . . . . . . : D-Link DFE-550TX 10/100 Adapter Physical Address. . . . . . . . . : 00-50-BA-F8-E7-25 Dhcp Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.0.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : What happens is neither of the computers can see eachother. The ping command replies with a ' request time out ' when trying to ping the other PC. Pinging Locally, (127.0.0.1) on both PC's works fine. So does a ping command to their own IP address. Now this setup has worked once or twice. That is, almost randomly it will work. But not very often. I have also tried to setup the workstation PC to have it's IP assigned automatically. This also fails. I am not running any firewall type on either PC. Both's PC's have their C drive shared. Both PC's are in the same workgroup. Netbios Is not installed on either PC. Neither of the computers are using any type of Network Access Control, i.e Smart Card. I think that is all the information I can give. So I ask you people, What am I doing wrong? Why won't it work? And as I mentioned above, why does it work intermittently? Thanks in advance. - Cardinal. [/i]

This might be like beating a dead horse but there is Norton Utilities 2002.

Thanks both of you.