I can answer portions of your post:
biosci3c:I am currently running Blink 4.4.1 on Windows 7 RC 32-bit. It works great (seems better than on XP SP3). However, there are a couple of issues. I have had a few BSODS, which I have traced back to blink (several occured in a row, but they seem to be fine now, had something to do with a file called tcpip.sys).
Windows 7 should be similar to Vista (in how it handles BSOD memory dumps) so if you can complete the following for eEye (if your problem occurs again).
1. Right click on My Computer >> Properties >> Advanced Tab. Look for a Startup and Recovery section (like Vista has at the bottom of this window) and select the Settings button.
In this section, there should be something about writing debugging information and then a field that you can select what size of "memory dumps" you want the system to complete when it encounters a BSOD. If you can, select "Complete Memory" dump and then make note of where on your system it is creating the dump files at. The default location in Vista is: %SystemRoot%\MEMORY.DMP. Now, if your BSOD occurs again, let the system create an entire memory dump before it restarts itself (so don't stop it by turning off your system when you see the BSOD). After your system restarts, go and retrieve the dump file it created, zip it in a zip file, and send it to Nicula at lnicula@eeye.com and if you want to include Brian also at bpatten@eeye.com . These dump files help eEye a lot with finding out what is causing the conflict with your system.
On a final note, you have to have a big enough pagefile also set to allow the system to create a dump file too. If it gives you a warning about not enough memory being set (after you make a change to the size of dump being done) that means your pagefile must be larger to allow it to complete successfully. Depending on the size of the memory dump, you may also have to email eEye and ask how you can transfer larger files to them (since email will not work when they are too big). eEye has ways of you sending them large files privately.
biosci3c: Printing with the firewall on is extremely slow (like one line every two seconds). When I turn off blink, it runs quickly
Since you know it is the firewall, can you run a debugging session with ONLY the firewall module in Blink turned on while you attempt to print? Information on how to do this can be found here:
http://www.eeye.com/html/support/kb/view.html?id=KB000802
Once again, send the logs to the same two individuals that I stated above. When you send any logs to eEye, please be sure to reference the post(s) you have made and any relevant information about your system that could be of use to eEye.