Yup. Looks like that may be the saving path here. And I sure will not migrate to anything past Windows 7. By that time I am hoping to be largely retired and then I don't have to care anymore. I have lately met a surprising number of people who have signed off for good, no more PC, no more Internet.
One thing I found is that Thunderbird versions past 24 really failed in Windows 7. V31 does really weird stuff. And V24 just crashed. Again ...
Whether open source or not, overall the quality of software deteriorates with higher version numbers. To me that has pretty much become an inevitable fact of life. So I cling to older versions because they typically are more reliable. Unless there is a really compelling reason to upgrade like there was with Cadsoft Eagle I will stick with "last known good".
With Windows 7 I have to keep the task manager open at all times to be able to force-terminate a program. With XP I don't have to do that.
I'm (not) running V31. Whenever I try to get my messages, it hangs. The log shows some sort of memory allocation error. Unfortunately, I have three years of email history on there that may be lost. :-(
Though more prone to hacking.
I certainly don't keep it open but it is often useful. ;-) I didn't find XP to be any different. Software sucks and always has.
Exactly the same here, even with V24.5.0. Right now it hangs. Again. But in Windows 7 I don't dare to kill it via CTRL-ALT-DEL because then it may never wake up again. This even happens when deleting a message, hangs for 5-10 seconds at a time. So I now must avoid deleting and do that summarily in the evening before dinner. What a joke.
Under Windows 7 such things are ssslllooooowww. Mostly I have to wait about two minutes, even after receiving "big" emails such as "test_1". Then it finally wakes back up. XP is clearly the better OS.
V31 crashes hard, never woke up again and always needed to be de-installed and re-installed. Too cumbersome to "receive" emails that way so I ditched it.
Oh, and I just managed a black-screen crash of Windows 7. On XP it was blue-screen but I only ever got that once, when the hard drive on my wife's computer went phseeee.. rat-tat-tat .. *CLANCK*
Important: Make your own file structure such as Keith_data/mail and back it up regularly. Never use the default.
True. However, the whole time I had XP there were no virus issues on my PCs. Same before. The only hardcore issue I encountered was actually in the DOS days. A client had a file on a 3-1/2" disk and when I inserted that into my laptop the computer locked up. Scanned it with a (back then rather elementary) virus scanner and sure enough that disk was infected. Didn't get into my computer but afterwards a major clean-up started at the client. Turned out it was everywhere there.
XP behaves like a rock here. After this rather unpleasant experience with Windows 7 I will keep XP on the other PCs. Malwarebytes has vowed to keep supporting XP with their virus scanner and now I know the reason.
Comparison:
When my wife's computer had a HD crash it took me around 2h on a Saturday moring to re-install XP, update drivers (afterwards it could play movies which it couldn't before) and re-install all the apps she needs.
On my new Windows 7 machine I had to install about 2x the number of apps but no OS because that came with it. I've now got over 30h of frustrating IT work in it and a few things still do not run right. Time during which I could not work for revenue. Windows 7 was a serious productivity killer for me.
This also means I will cling to my remaining old hardware, meaning no sales for PC makers on my part unless something literally goes up in smoke.
i kind of like W7-64, it has worked great for me.. of course I am using
12G or mem and no swap file.,. I don't load the system up when using it, just a couple of apps here and there.
As for viruses, I remember my first one back in the days of the IBM clone XT's etc It came on a 5.25 floppy from a game I got at a computer show, when shows where just getting started.. Name of the virus was the "Dark Avenger", ID it had in the file "Eddy Lives"
That virus would attached itself to the end of each file each time you ran a program(EXE), at some point your disk would run out of space!
Back when Peter Norton owned the business, his Norton Virus detection and removal worked a treat
The SMC Barricade 7008ABR is 15 years old. In computer years, that's an antique.
The setup instructions mention XP, so I'll assume XP was supported.
Insanity is doing the same thing repeatedly and expecting different results.
I thought you were troublshooting an antique router/print_server and not a network problem. If you can't ping the router, the print server is not going to work. You might want to do a 'system restor' on your Windoze 7 machine to a previous registry which should undo whatever you did to create the problem.
Windows: What do you want to reinstall today? OS/X: Making easy things easier and difficult things impossible. Unix: You can do anything you want, if you can figure out how. Linux: Ten ways to do everything, some of which might work.
--
Jeff Liebermann jeffl@cruzio.com
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
The real problem is that features and functions get added faster than bugs get fixed. Adding features means glory for the developer, while fixing bugs does not. If left to free run for any length of time, the inevitable result is a bloated useless feature infested monster that's full of unfixed bugs. The usual solution is to just start over from scratch, following the identical methodology, which produces the identical results.
--
Jeff Liebermann jeffl@cruzio.com
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
That's if you use their little software. But you don't have to, you can simply go through a TCP/IP port, key in the IP address and so on, works. Well, except in Windows 7.
And whoops, here it happened again: Email window whited out, TB says not responding, twice. Came back after two minutes. Whenever it doesn't it's CTRL-ALT-DEL. Never happens on any XP machine. Meaning XP is better, plain and simple.
That's why I don't want to start throwing printer names like "YUCK" at it :-)
(it's LPT1 on the Barricade)
Of course I can ping the router. Else I could not even respond here.
And XP always worked, for over a decade. Like clockwork. Man, do I miss XP already. And no ten horses will get me to switch any of the other computers. After this Windows 7 install I am cured of that.
Yep. I just noticed that it's stuck at LPT1 and unchangeable on the Barricade router. Are you sure you don't want a different print server?
I'm still using XP for most of my machines. XP isn't perfect, but good enough. Oddly, since MS stopped issuing updates, XP has been VERY stable and crash free. Hmmmm...
The problem with XP is that many software vendors are no longer supporting it. For my stuff, I don't care, but I have customers that buy expensive software packages that want support. Also, I can't get XP to run reliably on some of the latest greatest hardware. Eventually, I'm going to run out of old machines for XP.
--
Jeff Liebermann jeffl@cruzio.com
150 Felker St #D http://www.LearnByDestroying.com
Santa Cruz CA 95060 http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558
Did you try enabling the LPR / LPD features under:
"Add or Remove Programs" -> "Turn Windows Features on or off"
According to Microsoft Technet:
"The Line Printer Remote (LPR) Port Monitor allows a computer running Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2 to print to the Line Printer Daemon (LPD) service on a UNIX print server."
I can buy another one, sure. But isn't it sad that one has to ditch a pefectly good product just because the designers of another new product weren't competent enough?
Time to stock up on the old a.k.a. last known good stuff then. Seriously. There are people who did that even with cars. There you have the same bloat problem, more and more unreliable electronics are added.
I don't understand this. Or maybe I misunderstand. If I use any other name or alias the Barricad printer port will not understand. But it won't make a difference anyhow because Windows 7 doesn't even send anything there. XP does.
On the print server, you give the device a share name, right? If that is the case, then the entire remainder of the network does not need to know what type of port the printer is attached by.
If you have an application which requires printing specifically to say "LPT1", then you alias "LPT1" on the machine with the legacy app or whatever requires it with a pipe to the actual share name.
So, it would be like:
NET USE LPT1: \\SHARENAMEHERE
On the machine with the picky application. add /PERSISTENT: YES to make it stick in future boots.
That share name can be aliased locally on your machine by another name, if you are unable to call the share directly.
To get help on the NET function (command), type "NET HELP"
To get help on this USE alias function, type "NET HELP USE"
The "line printer daemon service" has to be up and running on said "Unix" machine.
Note that "the line printer daemon" service is a very old animal as are line printers themselves, so unless it still simply functions as a print server cue, it likely is not even ran on a modern system. Could also be a dormant kernel module that never gets initialized when modern kernels get compiled.
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.