Recently in Linux Category

Happy Programmer's Day, or what's left of it!

Well we finally got it working, otherwise you wouldn't be reading this! As we struggled to locate what the actual problem was, all we found was other people with similar problems but no one had answers. Finally the problem is solved. Here's what we found to be the correct installation order (obviously D/L & install applies to each step):

1. Ruby

2. Ruby Gems

3. Rails

4. MySQL-Ruby C Bindings

5. FastCGI Developers Kit (Muy Importante!!!!)

6. Ruby-fastcgi bindings (0.8.6 or higher due to mem leak issue in older versions)

7. Install DSO for mod_fastcgi (Apache 1.3)

NOTE: For Apache 2 & lighttpd step 7 is different but since we're using Apache 1.3 I'll digress.

This is just a quick reference so if you don't know how to use curl, wget or how to run make, I suggest some more reading before attempting this. Hope this helps everyone out there having setup issues similar to ours.

The HP PSC 1410 all-in-one printer is not really supported in the linux community, and very little information is available; practically none on HP’s website.

Here’s how I got it working in Suse 10.0 RC1:

By default the HPLIP drivers were installed with Suse.
If you need the drivers they can be downloaded from the sourceforge HP project: http://hpinkjet.sourceforge.net/

Download the HP 1400 series PPD from here:
http://www.linuxprinting.org/

Now you need to copy the PPD file into the right directory. In my case (as root):
From the terminal, su to root and type the following.

cp HP-PSC_1400-hpijs.ppd /usr/share/cups/model/HP

Go into YAST, Hardware, and printers. From there you can select the HP 1400 ppd for the printer, and you should be up and printing pretty pictures.

I received the error on Windows XP startup that my hal.dll file (hardware abstraction layer) was missing and Windows would not boot. Here’s how I fixed it.

Boot from your Windows CD and follow the directions to start the Recovery Console. When asked for your Administrator password, enter that in. In my case I didn’t have one so I left it blank.

I then navigate to the system32 folder by typing “cd windows/system32? to get into the system32 directory and type “dir” to get a list of directory files to confirm that the hal.dll file was there. In which case it was. This tells me that there is a problem with my boot.ini file.

I then typed the following:

cd C:/
Attrib -H -R -S C:\Boot.ini

DEL C:\Boot.ini

BootCfg /Rebuild

Fixboot

exit

The Attrib command I entered made the file editable. The DEL command deleted the Boot.ini file and the BootCfg /Rebuild created a new Boot.ini file based on my partition tables. The exit command reboots the PC.

If you ever run into this and the hal.dll file is truely missing, you can extract a copy from your Windows CD by typing the following from the recovery console.

expand d:\i386\hal.dll_c:\windows\system32\hal.dll

This will copy the file from the CD to your system32 directory and reboot. You should be up and running again.

I hope this helps someone that has the same problems I encountered with Windows and hal.