Whenever I get a hard drive mucked up, I usually just zero fill the drive and start with a clean slate. Especially if it doesn't contain anything I need to save.
If you are still interested in this particular ThinkPad, I would contact the seller asking for the seven character type number. Then look that number up on the Lenovo Support website using "Quick Path". If it has the Intel graphics, you should get a cool running and reliable machine. If you find it does indeed have the NVS 140 chip, I would pass on it. BTW, I own two T61 ThinkPadss, both of which have the Intel graphics, and they are fine machines.
The ThinkPad R61 can be an excellent machine, but I don't see the full type number or type of GPU mentioned anywhere in the eBay ad. That may, or may not, be a bad sign. This series has either onboard Intel graphics, or discrete nVIDIA Quadro NVS 140M graphics chip which has been widely documented as having a manufacturing defect that affected every brand of laptop they were installed in. This doesn't mean they have, or will all fail, but all of them manufactured before 08/08 were defective, and IMHO are like a ticking time bomb. Often, when eBay sellers fail to mention this chip, it's because they are covering up the problem.
I run 32-bit #! with 1.5GB RAM, and it's plenty for me, but I seldom have more than five or six Iceweasel tabs open at a time. RAM usage for me usually stays under 400MB. But, at this moment I'm on my Xubuntu box running Chrome with three tabs open and RAM usage is still under 600MB. This machine is also 32-bit, with 2GB RAM.
We've recently been discussing this topic in this thread: http://crunchbang.org/forums/viewtopic.php?id=25463
There are some tips and links to additional info in there that should be enough to get you started, if not all the way to networking those three machines.
The system-config-samba package I *think* added a very easy way to set up samba shares using a small GUI, instead of these cryptic changes to smb.conf. Maybe that works on crunchbang as well?
Nice find! Somehow, in my searching around, I had missed that one. So, I too installed "system-config-samba" on my Xubuntu laptop, and in seconds had the chosen directories available on the network, accessible to other Linux and Windows machines alike. No more difficult than doing the same in Windows. I'm thinking this is one of the reasons Ubuntu, and it's derivatives, are so popular with those of us who are simply "users", and not system admins. Sadly, the package doesn't seem to be in the Debian repos, but I suppose one could install it from source. When I get some time, I'm going to look through the Xubuntu smb.conf file to see what changes have been made there, and then apply those to my #! box to see if I can make it's files available to the network.
Thanks for all the suggestions. Feels like we are making some progress!
I appreciate the help guys. I'm sure my problems are not because the system doesn't work, it's my lack of knowledge about setting things up, and the way folks who are trying to be helpful always forget to include a few details about how they got it working. For example:
@neil a bit confusing now you guys have different issues - but you need to make sure ssh is enabled/running on your linux box.
sudo service ssh start
I suspect you're right, and ssh should work, but with only the instructions lilince wrote, it doesn't for me. If I enter "sudo service ssh start" in terminal, I get the error "ssh: unrecognized service". So I tried openssh, and get "openssh: unrecognized service". So, I'm still lost as to why it doesn't work for me, since I know openssh is installed. If I run apt-get install openssh-server again, apt shows it as already installed.
@phillipe1 - thats a really good stripped down essential howto for smb.conf - thanks!
Phillipel's guide didn't add any functionallity that I don't already have, and he didn't include the one most important edit needed to browse Windows shares in Thunar, i.e. add "name resolve order = bcast host" right under the WORKGROUP entry. But, even with Phillipel's edits, I can't browse #! from Windows.
and @neil you can browse winXX machines from #! because its built in to Thunar
Yes, for the most part, but even as delivered with Waldorf it doesn't just work OTB, smb.conf still needs at least the one edit above to make it work.
This is not of great importantence to me, as it's just a hobby and something I'm trying to learn. So, I will keep reading, and trying things until I stumble onto something, amid all the incomplete suggestions, that makes it work for me. At this point, I'm thinking that setting Samba up as a server is what we are trying to do, but as of yet, I have only seen it work with a Puppy Linux distro that was pre-configured as a server (PupServer). Since Linux is so often used as a server OS, one would think this would not be so hard, but so far, it has been for me, and apparently so for matroska, and many others a well.
I think people are over complicating things. On the windows machine, install WinSCP. On the #! machine, install openssh-server:
Sound simple and easy. OK, installed as directed on both machines.
On the windows machine, install then fire up WinSCP, enter the hostname of your #! machine, select SFTP, choose port 22 and enter your password. You can then transfer files between them.
Nope...doesn't work. WinSCP replies, "host does not exist".
You only need to mess on with Samba if you want to access Windows files from the #! machine.
Now this works splendidly! I have no trouble setting up Samba to access Windows files from #!, but have yet to get it working the other way around. Just tried Philippe1's suggestions, but that didn't seem to help the situation any. Still can't browse #! from the Windows box.