Today I tried to print a file in the office, and couldn’t. I was able to search and find the print server and the right printer, but I couldn’t get it to connect. Windows 7 just said “Connecting to…” for several minutes. Trying another printer eventually got past that screen, but then Windows 7 immediately demanded that I provide an .INF file. Which I didn’t have, of course.
I’d already printed to a network printer at home, so why didn’t it work at the office? I don’t know, but I’ll spend some time fiddling with it next week. I can’t see any reason for Windows 7 to have trouble with this.
On the good news front I now have a working VPN client. NCP sent me a download link for the their beta Windows 7 VPN client, which is good for 30 days before I’ll have to purchase it. I had a little trouble configuring it because there are a nearly infinite number of configuration options and it wasn’t clear to me which ones I should choose. But then I remembered reading that it could import a saved Cisco VPN configuration file. I imported the one I’d used in Windows XP, and it immediately connected and worked perfectly. So I guess I’ll be buying a copy soon.
I’m annoyed with Cisco, though. They sold us VPN concentrators and I feel they’re responsible for providing client software to connect to them. It’s irresponsible for them to not support 64-bit versions of Windows.
Charles Engelke's Blog 
First of all sorry for commenting at wrong place.
I have a question about your old post https://blog.engelke.com/2005/08/27/codewright-and-ugly-fonts/
I tried that but it didn’t worked for me. Can you please describe in detail if you remember that?
Comment by Brijesh — February 25, 2009 @ 1:01 pm
See my new post about this.
Comment by Charles Engelke — February 25, 2009 @ 3:19 pm
Hello!
Very Interesting post! Thank you for such interesting resource!
PS: Sorry for my bad english, I’v just started to learn this language 😉
See you!
Your, Raiul Baztepo
Comment by RaiulBaztepo — March 28, 2009 @ 9:09 pm