Expired HP cartridge - OfficeJet K5400

Trying to print few more pages on HP OfficeJet K5400, but not able to print everything at once. It would print 3 pages, then stuck after printing about 70% of the 4th one and LEDs blinking: the Power light and the Resume light blink, and all Print Cartridge lights are on, as described on HP Support document for K5400 series HP printers and HP's Ink Expiration page (another link).

I searched on the internet and I found solutions that worked for others but not for me.

The solution that worked for me is described on hardwarefetish.com using HP Ink Cartridge Expiration Patch (got this link via comment on http://constitutionalcode.blogspot.com/2005/02/cartridge-expiration-date-workarounds.html). Great staff, thank you!

FTP on Windows 2008 Server R2

FTP on Windows Firewall and non-secure FTP traffic

To easily set up an FTP server, Filezilla can be used (test locally, make sure it works). Additionally, a quick step is necessary: add a rule in Windows Firewall to allow necessary ports.

Windows firewall can be configured from command line using netsh command. 2 simple steps are required to setup Windows Firewall to allow non-secure FTP traffic:

1) Open port 21 on the firewall
netsh advfirewall firewall add rule name="FTP (no SSL)" action=allow protocol=TCP dir=in localport=21

2) Activate firewall application filter for FTP (aka Stateful FTP) that will dynamically open ports for data connections
netsh advfirewall set global StatefulFtp enable

Taken from http://social.msdn.microsoft.com/Forums/en-US/winserver2008appcompatabilityandcertification/thread/72ea0c7d-1071-4637-a38f-e77195e8a738/

Some more info
Configuring FTP Firewall Settings in IIS 7
http://learn.iis.net/page.aspx/309/configuring-ftp-firewall-settings-in-iis-7/

FTP7 for Windows Server 2008 RTM is released!
http://blogs.msdn.com/b/robert_mcmurray/archive/2008/02/27/ftp7-for-windows-server-2008-rtm-is-released.aspx

Installing FTP 7.5 on Windows Server 2008
http://technet.microsoft.com/en-us/library/dd722761(WS.10).aspx

Configure Total Commander as a client to use SSL/TSL feature

1. Get the OpenSSL package from
- official page - http://gnuwin32.sourceforge.net/packages/openssl.htm
- the LibCurl library - http://curl.haxx.se/download.html *
* Please scroll down to the section named "Win32 - Generic" and download the following package (or a newer one): Win32 2000/XP 7.19.0 libcurl SSL enabled Günter Knauf 1.54 MB

2. Copy the two dlls libssl32.dll and libeay32.dll from the "bin" subdir of the archive to the Total Commander directory.

3. Now you can make connections with prefix ftps:// and https://

Note: There will appear a red open locker for connections because the root certificates are missing. To get the root certificates of Verisign, Thawte etc, do the following:
1. Start Internet Explorer and open its configuration dialog
2. Go to the page "Content"
3. Click on "Certificates"
4. Go to the last page "Trusted root certificate authorities"
5. Select all certificates
6. Click on"Export"
7. As name, enter: rootcerts
8. Confirm with Next/OK. This creates a file rootcerts.p7b
9.a. Copy rootcerts.p7b to the installation folder of OpenSSL C:\Program Files\OpenSSL\bin\
9.b. Issue the following two commands to convert to openssl format:
openssl pkcs7 -inform DER -in rootcerts.p7b -print_certs -out unfiltered.pem
openssl x509 -in unfiltered.pem -out rootcert.pem

10. Put the file rootcert.pem in the Total Commander directory

Dual-boot Windows XP and Windows 7 (or Vista)

"Earlier versions of the Windows operating system (XP and bellow) are incompatible with the new Windows Vista startup method. Windows Vista uses a new Boot Configuration Database (BCD) store. This store contains a boot menu and all the information about operating systems that are installed on the computer. Therefore, a Boot.ini file that is from an earlier version of the Windows operating system cannot be used to start Windows Vista.

In earlier versions of the Windows operating system that run on a basic input/output system (BIOS)-based computer, such as Windows XP, the boot process starts with the system BIOS. The BIOS determines the boot device, and then loads the first physical sector. This physical sector is named the master boot record (MBR). The MBR contains the partition table and the necessary boot execution code. This code searches the partition table to find the active partition and passes control to the boot sector on the active partition. Then, the boot sector on the active partition loads the Ntldr program. The Ntldr program parses the Boot.ini file. This file is used to enumerate the operating systems that are installed.

When Windows Vista or Windows 7 starts on a BIOS-based computer, the BIOS loads the MBR and then loads the boot sector. However, boot code loads the new Windows Boot Manager program (Bootmgr). The Windows Boot Manager program parses the Boot Configuration Data file, enumerates the installed operating systems, and then displays the boot menu. If an earlier version of the Windows operating system is installed in a dual-boot configuration with Windows Vista or Windows 7, the Windows Boot Manager program transfers control to the Ntldr program for the earlier version of the Windows operating system. The Windows Boot Manager program does this when you select Windows Vista from the boot menu.

When you install an earlier version of the Windows operating system on a Windows Vista-based or Windows 7-based computer, Setup overwrites everything from the MBR, the boot sector, and the boot files. Therefore, the earlier version the Windows operating system loses forward compatibility with Windows Vista.

To start versions of the Windows operating systems that are based on Microsoft Windows NT, you need the following files:

• Ntldr
• Boot.ini
• Bootfont.bin

Note You need to use this file when you install the Windows versions of the East Asian languages.

• NTDetect.com

In Windows XP, these files reside on the system partition that is marked "active." By default, these files are hidden system files in Windows XP. Users can replace these files by using the Recovery Console, or users can start the operating system by using a Windows NT boot disk. Windows Vista does not use these three files. Windows Vista starts by using the hidden system file Bootmgr and other required files that are located in the \Boot directory."

Taken from Microsoft KB.

Quick tasks:

Windows 7 won't boot:

Start the Windows 7 install DVD, and choose "Repair" and "Command Prompt". At the prompt, do a "bootrec /RebuildBCD" to write down a new bootloader.

Credits goes to answer #31954 on serverfault.com

Links:

- Windows 7 on C: partition, Windows XP on D: partition and the PC booting into XP automatically

- How to Do a Dual Boot Installation with Windows 7 and XP + How to Stop System Restore Points from being Deleted in Vista when Dual Booting with XP

- How to install Windows XP over Windows 7 in a dual boot ?

- Install Windows XP in Dual Boot with Pre-Installed Windows 7

- Installing Windows XP after Windows Vista

- Switching my Windows 7 Boot Disk from D to C with BCDBoot rather than BCDEdit

- How to Use the BCDEDIT Command Line Tool

- Hack the Windows NT/2000/XP Boot Loader

- quad-booted XP, Vista, Leopard and Ubuntu on the same HDD

- “How to” Dual boot Ubuntu and Windows 7 (Ubuntu installed first)

Despre acest blog
Disclaimer and privacy statement
Actualizat: 2010-04-08.
___

TCP/IP troubleshooting in Windows

Some useful links from Microsoft:
http://support.microsoft.com/kb/314067/
http://support.microsoft.com/kb/299357




Utils:
- to reset TCP/IP stack do this at the command prompt:

netsh int ip reset c:\resetlog.txt

C:\windows\system32\config\system missing or corrupt

Problem: When starting computer (Windows XP Home), the following error message is displayed:

Windows could not start because the following file is missing or corrupt
C:\windows\system32\config\system

You can attempt to repair this file by starting windows setup using the original setup CD-Rom. Select "r" at the first screen to start repair. Do NOT use an OEM "Recovery Disc". Only a valid Windows XP media will work or a disc from the OEM that says "Operating System" may sometimes work depending on how the manufacturer labeled the CD.

Searching the internet, I found several places describing the problem which didn't work for me - in my case, the culprit was bad memory installed.

Links: Windows XP Crashed? Here's Help, Microsoft article Q307545, DriverGuide forum.

Windows Media Player Plugin for Mozilla Firefox, in Windows 2003 Server R2

MichaelF's Windows Media Player plugin is a great one, only that it won't work on server platforms. I used the method below to have this functionality on Windows 2003 Server R2 Enterprise Edition. It might work on any Windows 2003 server editioin, but I didn't test. Follow the steps below if you wish to try on your Windows 2003 Server:

1. Install Windows Media Player 11 (not necessarily needed, but that's what I did), using Zack Whittaker's method. It worked like charm. Comment 67 on its page helped me go further - this is what is says:

March 24th, 2009 at 4:25 pm - LinHongJun Says:
Use Microsoft’s Orca to edit extracted ffplugin.msi and remove the lines under LaunchCondition. Save and exit Orca, now you can run ffplugin.msi to install WMP Firefox plugin.
http://port25.technet.com/pages/windows-media-player-firefox-plugin-download.aspx

2. Download WMP Firefox Plugin from the link above. Extract the archive to a folder, let's say C:/wmpfirefoxplugin_winxp/.

3. Download and install Windows installer 4.5 Development Kit. Go to the installation folder (C:\Program Files\Windows Installer 4.5 SDK\Tools\) where you will find orca.msi.

4. Install orca.msi then open it. In Orca, open the file C:/wmpfirefoxplugin_winxp/ffplugin.msi. Go to LaunchCondition Table and change condition MsiNTProductType from value 1 to 3 (I also changed description to reflect condition change).

5. Run C:/wmpfirefoxplugin_winxp/ffplugin.msi and voila! The plugin is installing without error. If Mozilla Firefox is open, close it and open it again. From now on, websites which require WMP plugin will work as expected. Here is one to test.



If you need WMP plugin modified as explained above, you can get it from this location. Open the archive and run ffplugin.msi. Feedback is greatly appreciated and highly moderated. Please do not ask for other versions, I don't have time for tests. Take the information as it is and let me know if it works or if you like.


Links related to this subject:
- How to install Windows Media Player 11 with Media Sharing on Windows Server 2003 / R2 by C:Amie

About
Disclaimer and privacy statement
Updated / Actualizat: 2009-03-30.
___

Copy / Paste Files Between A Terminal Server And A Client

As simple as that... :)


Despre acest blog
Disclaimer and privacy statement
Actualizat: 2007-06-22.
___

Terminal Services on Windows XP

[later edit] To use more than one remote desktop sessions, there's XP Unlimited for Windows XP, which allows use of up to 3 concurrent connections in trial version, and no time limits. Nicely done.


Warning: The following tutorial is available in full length at Jason Golod's blog and Riccardo Raneri's blog thou' it didn't work for me. Haven't read all comments, maybe that can help.


1. Go to Safe Mode

2. Disable Remote Desktop (right-click on My Computer)

3. Disable "Terminal Services" service (Administrative Tools)

4. Backup C:\Windows\system32\dllcache\termsrv.dll

5. Copy this modified termsrv.dll to C:\Windows\system32\dllcache\

6. Add [EnableConcurrentSessions.reg] to registry

7. Start >> Run >> gpedit.msc >> browse to Computer Configuration -> Administrative Templates -> Windows Components -> Terminal Services and double click Limit number of connections >> select Enable (2 or more connections, recommended 5)

8. Restart Windows in Normal Mode

9. Enable Remote Desktop (right-click on My Computer)

10.Enable "Terminal Services" service (Administrative Tools)


Despre acest blog
Disclaimer and privacy statement
Actualizat: 2007-03-07.
___