Compaq armada 1700 upgrade advice

MMXP · Sun Sep 30, 2007 9:49 pm

Hey I'm back after a good while

I have some questions that maybe some of you can help out with.

I just now acquired a brand new compaq armada 1700 from a good friend of mine. He said he's only used it twice and never laid eyes on it again after he got a dell desktop....

I need to know if this laptop will take anywhere from 300mhz to 700mhz with speed step 3 enabled on the mobo ? I heard some idiot on another forum pushed his armada 1700 to 750mhz without killling it... is that possible even though I have a p2 233 running at 100fsb ?

Also I will put in a 40gig HDD in this laptop as well as increasing the ram to 160mb... The reason why I am doing this because I will be leaving behing windows 98SE and moving on to windows 2000 also I will be taking this labtop on small trips or for business usage and maybe play some games on it.

I need to know if this will be possible at all.

1.Week 1 CPU upgrade.
2.HDD upgrade
3.week 3 final memory upgrade.

will I need a bios update to do the required upgrading tasks ?

Sharedoc · Fri Oct 05, 2007 4:49 pm

Propably P2 233 processor needs to be changed to a faster P2 or possible P3 CPU. Propably you can upgrade up to 400MHz P2 quite easily.

MMXP · Sun Oct 07, 2007 12:41 am

Would this help out any I know the FSB on this CPU is at 100FSB my mums has one in her dell laptop.

I also know that if I install this on my compaq armada 1700 the laptop would slap the speed down from 500mhz to 400mhz and thats quite fine with me as long as I can go on to use XP home or Pro sp1

My main number question is will the compaq accept it without needing a bios hijacking ?

http://cgi.ebay.com/ws/eBayISAPI.dll?Vi ... =p3907.m29

Wed Oct 10, 2007 11:50 am

your P2 233MHz is running a 66MHz FSB because there are no 2.33 fractions on intel processors. the compaq armada 1700 features an intel BX/DX/ZX chipset and supports 100MHz FSB, so you can go for a 100MHz FSB CPU like a 500MHz P2. maybe even a P3 will work but be sure to check if the L2 cache is initialized correctly. A bios update or an additional software driver on the operating system may fix this issue.