Recently I replaced my tired old Inline 6 cylinder in my 1963 C10 with a used 350 crate motor. The previous owner has put a fairly ‘large’ cam in it, and it has that aggresive ‘lopy’ idle that we all want. While it sounds great, cams like this create very low vacuum at idle, which introduce other problems.
Chances are that if you are reading this post, it is because you are having a hard time finding a PCV valve that will operate correctly with low manifold vacuum. Try using a standard PCV valve with low vacuum, and you can hear an annoying clicking or ticking noise. This is caused by the valve not fully opening as there is not enough vacuum to do so. This may create other problems as you may not be extracting all the crank case gasses building up in the engine, which the PCV was designed to do. While there are a few options out there to solve this problem, I was surprised I was never able to find a specific ‘high performance’ or aftermarket PCV valve for low manifold vacuum motors. Most people recommend getting a PCV valve from an early to mid 60’s high performance car, such as the corvette which came from the factory with low manifold vacuum.
Upon further research, I discovered that not many years ago, GM released a PCV valve … which isn’t really really a valve at all. It’s just the PCV housing, with all the guts removed and is hollow in side. The bottom side has a pin hole, much smaller than standard PCV valves. The GM part number for this PCV is 12572717, and you’ve probably seen this referenced all over the internet while doing your search. I went to my local Advanced Auto Parts store, and while they didn’t have the GM brand, they did have the exact same part made by a company called BWD, and it is part number PCV484. It cost me just under $8, and made a huge difference in my motor. Because the inlet hole is so small, it actually helped bump up my manifold vacuum, and now I feel safe that the crank case gas build up is being removed safely with out me having to worry about. It fits right into my Chevy Small Block 350 as any PCV would do.
Here are a couple more photos of this PCV valve
The turn signals and hazard lights quit working on my 1998 Dodge Viper recently. Following the directions in the service manual to diagnose the problem, I discovered it was the Turn Signal / Hazard Flasher module located where the fuse box is under the steering wheel. Unfortunately, you have to pull the whole dash panel off under the steering wheel to get to this module as it is not accessible from just removing the fuse box panel cover. Thankfully it’s only about 5 or 6 screws you have to remove and the whole dash panel comes off.
I looked around for a replacement Turn Signal / Hazard Flasher module, and all I could find were very expensive MOPAR / Chrysler replacements. The part number of the Chrysler Flasher Module is 56007098 and they range anywhere from $30 – $45 on eBay and other online sites. I figured there had to be a cheaper module available that was a reproduction brand from another company, after all I was certain this Flasher module would be used in other Chrysler & Dodge cars as well.
Sure enough after some searching by a determined employee at Advanced Auto Parts, we found a replacement module made by Novita (Part number EP27), and cost only $15.99. It is a 5 terminal, 11-15v DC flasher module. I just installed it an my turn signals are working once again on my Dodge Viper.
It’s been 1 week since my nose surgery. I went to the doctor today for the 1 week checkup, and get the packing out of my nose, and stitching cut. There is a big improvment, and I feel 95% better, though things are still a little sore. Anyway, it was totally worth the 1 week of pain.Watch movie online The Transporter Refueled (2015)
Thats all for now.
phpCrypt version 0.4 was released late last night. It includes support for the 3-Way cipher. Another big addition is support for secure random number generation on Windows using the Microsoft’s CAPICOM SDK. This will create Initialization Vectors which are more secure than in previous releases on the Windows platform. Prior to version 0.4 Windows users had to rely on PHP’s mt_rand() function for random numbers. View the README file included with phpCrypt for more information.
In addition, several bug fixes and minor speed improvements were made to the library. This version is still considered ‘experimental’ and is not ready for production.
I’m considering freezing this version for a while, and let feedback roll in so I can address issues and implement feature requests.
Chances are that you stumbled onto this page because Linux is freezing, crashing, and randomly rebooting on you, and you can’t figure out why. There is a strong chance that the reason this is happening is because the ACPI (Advanced Configuration and Power Interface) and APIC (Advanced Programmable Interrupt Controller) implementation on your motherboard is buggy, and Linux can not properly communicate with them. On any modern PC, ACPI and APIC are standard, and most have no way to shut them off in the BIOS. To make matters worse, many implementations of these by BIOS manufacturers are buggy and do not meet the specifications properly.
What is ACPI and APIC?
Most of my readers who have found this page already know what these are and what they do, they just want a solution to fixing the problem. I won’t write a detailed explanation about what ACPI and APIC do, rather I will point you to some resources for you to get a better explanation:
http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface – An explanation of ACPI
http://en.wikipedia.org/wiki/Advanced_Programmable_Interrupt_Controller – An Explanation of APIC
http://support.novell.com/techcenter/sdb/en/2002/10/81_acpi.html – Linux Kernel boot parameters for ACPI and APIC
If your Linux box is freezing, crashing, or rebooting because of ACPI or APIC, this isn’t the fault of Linux. As far as I can tell from my research Linux properly implements ACPI and APIC, and the implementation on your BIOS is buggy. Of course, in Windows these buggy implementations are often accounted for, leaving the BIOS manufacturers with little reason to correct their errors. This is where we run into problem in Linux
So how can you fix the problem?
The first thing you should do to correct the problem is to check the maker of your PC or Laptop and see if there is a BIOS update. If there is an updated BIOS try this first and see if it fixes your problem. I have read where this helped some people. Personally though I have never been this lucky
A BIOS update did not work, now what?
If you have the latest BIOS, or the BIOS update did not fix the problem, your only other option is to disable ACPI and APIC from loading during the Linux boot. This is not the ideal as APIC and APIC, when working, are very beneficial to your computer. However using a computer that freezes, reboots, and crashes is even worse.
What you have to do to turn off ACPI and APIC in Linux is pass kernel boot parameters to the Kernel at boot time. This is done by modifing your boot loader GRUB or LILO. This article will not get into detail on how to modify your GRUB or LILO configuration, however I will explain which parameters to pass to your Linux kernel.
The four Kernel parameter options you will be concerned with are:
- noapic – Turn of the System APIC
- lapic – Turn on Local APIC
- nolapic – Turn off Local APIC
- acpi=[off | ht ] – Turn off ACPI completely by using acpi=off, or partially shut off ACPI leaving on your processors Hyperthreading on by using acpi=ht
On single processor machines you can fully disable ACPI and APIC by passing kernel boot parameters:
- noapic nolapic acpi=ht
The above parameters tell Linux to not load the APIC and Local APIC kernel modules, and only load ACPI so that it enables the Hyperthreading on your processor
On a dual core, quad core, or multiprocessor machine, you want to make sure you enable Local APIC. Local APIC has some kind of control over your Multiprocessor machine. If you shut off Local APIC on an multi-core or multiprocessor machine, you will only see one processor available. Use the following Kernel parameters:
- noapic lapic acpi=ht
Well that’s about the best I can explain it. Hopefully this helps you, or at the very least gets you some starting point to fixing your Linux problems.
After many months (technically years) of working on phpCrypt, I am finally happy to announce a Beta version of phpCrypt is finally ready for the public. phpCrypt is an Open Source PHP Encryption library that does not require or use any external PHP modules. phpCrypt does not use mCrypt or OpenSSL PHP modules. phpCrypt was written from scratch using freely available resources online and in books, to help me better understand and learn encryption. It’s not as fast as the mCrypt module because phpCrypt is written in PHP, however if you are in a situation where you can not use the mCrypt library phpCrypt should be a suitable alternative.
phpCrypt aims to support every major encryption cipher, as well as major encryption modes. Also included are some older, historic encryption ciphers, which I implemented when I was bored.
Please note that this release is a beta release. I have not had the chance to test it thoroughly, so I am hoping others will give phpCrypt a shot, and report back what you think. The project is under active development, and I will respond to bug fixes as soon as possible.
Chances are if you found this page, it’s because you locked yourself out of Windows 7 and forgot the password to log back into your account. There are many ways to reset your password including several software applications that can do the job. However, I have found the easiest way (and free!) is as follows:
- Get your Windows 7 installation disk. If you don’t have one, you can download a free copy of the Windows Install disk here and burn it to DVD:
Windows 7 32-Bit (x86) Direct Download Links
Windows 7 64-Bit (x64) Direct Download Links
- Insert your Windows 7 Install disk in your CD/DVD drive, reboot your computer, and boot off the DVD.
- When the Windows 7 install screen comes up, click the link that says ‘Repair Windows‘ near the bottom left hand side.
- A new screen appears with several repair options, select the one that says ‘Command Prompt’
- When the command prompt opens, you will be in the X:\ drive. This is the Install DVD and not your Windows System. You need to find where your Windows 7 is installed. It may be C:\, however it is not uncommon for the Repair Disk to place it as drive letter D:\ or another drive letter. Search drive letters until you find one that has the Windows directory. For demonstration purpose I will use D:\ in this article. So if D:\ is your Windows installation drive, then you will have the following directory D:\Windows
- Now you are going to make a copy of the Sticky Keys application, because we are going to copy over it later. To make a copy of Sticky Keys run the following comand:
X:\> copy D:\Windows\System32\sethc.exe D:\
- Now we are going to copy the Command Prompt cmd.exe over the Sticky Keys appliction. To do this run the following command:
C:\> copy D:\Windows\System32\cmd.exe D:\Windows\System32\sethc.exe
- You’re now done with the Command Prompt and Repair Mode. Reboot your computer and remove the Windows 7 DVD.
- When the computer reboots, it will boot back up as normal into your login screen. Now press your shift key 5 times. The Command Prompt will open up.
- Run the following command in the Command Prompt:
C:\> net user [your_login_name] [your_new_password]
*Please Note that [your_login_name] is the login name you are resetting the passworld for, and [your_new_password] is the password you want to set for the login name.
- Close the command prompt, and now login with your new password! Once you are logged into your account, don’t forget to copy the sethc.exe back to it’s original location.
C:\> copy C:\sethc.exe C:\Windows\System32\sethc.exe
That’s it. You are done! You can now begin logging in with your new password.