Not sure if this fits here but ... I installed Suse 10.0 on a 32 bit PC and could use the CLI perfectly. I have a new 64 bit PC now and I am unable to CD further than one part of the path eg CD /home works ok but cd /home/bin does not. Also I cannot CD to any new folders I create. I have tried to give myself full permissions but still not working. I am mnot doing this with root login but then I wasn't on my old 32 bit PC.

I'm not sure if this also may be a way my new PC has SATA drives and has Dell hidden partition at end of drive?

I'm on the verge of giving up Linux as I use Dreamweaver on Windows so using Dual Boot PC.

Any help is welcome. Until I find answers I cannot even begin to attempt to install the driver for Ethernet Controller to get a network connection with Linux. I'm afraid Linux still has a long way to go before convincing users like myself (not beginner but no way expert) who just does not have much time to spend on these problems. I even put in another ethernet card which Linux found and used yesterday but unable to do so today because it wants to use the onboard one. (I'm using Windows to send this message !)

All in all I'm just about ready to give up because of the time constraints.

moonhawk

Further findings: Also unable to use CD command with root login properly. I can also not change permissions to folders to Read/Write/Execute in Root Login. It does not find or open an external Lacie Hard Disk I have - Nautilus brings up error (whereas in my home login I can open the external hard drive .....

This is all on fresh brand new install of Suse 10.0 64 bit version on a new PC.

Is it Suse (64 bit version) causing problem?
Is it the way the SATA Hard Drive's formatted/partitioned? PC make is Dell Dimension 9150.

I did everything similar to my old PC which dual booted with Windows/Linux with no serious problems as described above.

With the network card situation I've spent the evening trying to get a connection back with Linux and done numerous configuration of network settings/Intel Pro/100 - nothing. So I'm left with Windows which has the onboard Internet connection.

Am at the end of my tether so any help now appreciated!!!

Apologies for posting twice - it was unintentional when I was registering simultaneously I think and windows popping up here and there.

After a fresh install of Suse, its behaving exactly the same way and at this point I have to resign myself to unfortunately only using WindowsXP on this machine.

I am now beginning to think it may be the partitioning. Dell have two hidden partitions on their new PC's - a Utility (next to C: Windows) and a Restore (which replaces the WindowsXP CD). The Restore is located at the end of the HD. Linux places itself in between. So could this affect the functioning of the terminal?

In the future I may just have to wipe HD completely and reformat it my way.