Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

old win98 compaq laptop help

- - - - -

  • Please log in to reply
17 replies to this topic

#1
togermano

togermano

    Member

  • Member
  • PipPip
  • 105 posts
  • Joined 07-July 08
I have an old windows 98 compaq laptop I lost the restore cd so i installed windows 98 using the cd I had of it and unfort the compaq drivers check to see if its a windows 98 that came from compaq off their restore cd I guess. THere must be some kind of reg hack to make the drivers think I am using the windows 98 version from compaq... Does anyone know of such a hack?


How to remove advertisement from MSFN

#2
CharlotteTheHarlot

CharlotteTheHarlot

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,054 posts
  • Joined 24-September 07
  • OS:none specified
  • Country: Country Flag

I have an old windows 98 compaq laptop I lost the restore cd so i installed windows 98 using the cd I had of it and unfort the compaq drivers check to see if its a windows 98 that came from compaq off their restore cd I guess. THere must be some kind of reg hack to make the drivers think I am using the windows 98 version from compaq... Does anyone know of such a hack?

I believe you are talking about two different CDROMS. You said you "installed" from a ( official Windows ? ) disc but then you say the "drivers" then "check" something. Did this "check" happen during the install? And by "install" do you mean Windows setup or the Compaq recovery which are two different things? It would help if you describe exactly what you did in detail including describing the discs you used, and Windows version.

The "Recovery" or "Restore" discs are different from "Windows discs", and were a completely different animal in those days. Some that I remember for that Win9x era contained OEM created images or similar packed files with the OS and OEM branding and crapware all in one. This is roughly comparable to the way it is done today in the Windows 6.x era with recovery partitions holding the same type of stuff ( Dell, HP, etc ). Others had only the applications on the "Recovery" or "Restore" discs and required setup from the OEM Windows CDROM first. It can be very confusing!

( Although this doesn't apply to you with Win98 gold, I have the Microsoft Win98se and the similar Compaq branded version, they are the "Windows discs" and only differ slightly with OEM branding stuff and some INFs in two CABs ( one is Precopy2 iirc ). This Compaq Windows CD is not tied to any Compaq model however, unlike the "Recovery" or "Restore discs" which are very specific to the exact model of computer. )

In theory, a complete reformat and install from any non-OEM branded official Microsoft "Windows" disc usually works, only resulting in some missing logos in the owner page and other minor things. However, at least Compaqs had a radically different BIOS arrangement that used some local files in addition to the CMOS chip. So, while 95% of computers can be tamed by re-formatting and full installing Windows, you might very well have one of the very few that are actually locked to custom install files. What I am saying is that you might have the type of computer that cannot be wiped and installed normally and will have to track down the correct discs.

Also, the Compaq model is very important for another reason. If I am not mistaken, they had these very specific Driver PAQs ( update and support files ) that might be necessary, but this info should be able to be researched today in Google ( unlike in those days in the early to mid-1990's ).

So you have to really be specific on what discs you have, what you did, and what was the result. What is the exact Compaq Model? What exactly do the discs look like? Is one of them the correct "Recovery" or "Restore" disc for that model? I despise those recovery-restore discs personally but you may be stuck and have to rely on it unfortunately. There is some chance an image of it can be downloaded from a Compaq user group website, but failing that, there may be one on eBay.

... Let him who hath understanding reckon the Number Of The Beast ...


#3
togermano

togermano

    Member

  • Member
  • PipPip
  • 105 posts
  • Joined 07-July 08
The model is 1600-XL145 and what I mean is I used a windows 98 se I bought years ago. Unfort the driver setup files you download from compaq website checks to see if a valid compaq mobile platform and the setup says no it is not because I did not install windows 98 se from the compaq branded windows 98 cds...

#4
CharlotteTheHarlot

CharlotteTheHarlot

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,054 posts
  • Joined 24-September 07
  • OS:none specified
  • Country: Country Flag
So this is a laptop and you are talking about Win98se, correct? What is actually installed now? Is this how it was originally delivered?

Do you know what the partitioning is? In other words, is it just C: or maybe several partitions, perhaps a hidden partition with recovery/restore files?

What are the specific discs you have? Are they distribution or CDR? We need to know what you are missing!

What are the files you say you downloaded and are they the exact ones for that laptop?

... Let him who hath understanding reckon the Number Of The Beast ...


#5
togermano

togermano

    Member

  • Member
  • PipPip
  • 105 posts
  • Joined 07-July 08

So this is a laptop and you are talking about Win98se, correct? What is actually installed now? Is this how it was originally delivered?

Do you know what the partitioning is? In other words, is it just C: or maybe several partitions, perhaps a hidden partition with recovery/restore files?

What are the specific discs you have? Are they distribution or CDR? We need to know what you are missing!

What are the files you say you downloaded and are they the exact ones for that laptop?

The original harddrive has been changed because it was broken. Its just the regular windows 98 se cd and I use the windows 98 key that is on the back of the laptop. I downloaded the drivers from the compaq website and yes they are exact drivers....

#6
togermano

togermano

    Member

  • Member
  • PipPip
  • 105 posts
  • Joined 07-July 08
the modified inf and cab files must satisfy the drivers setup file system check to see wither its compaq or not :(

#7
CharlotteTheHarlot

CharlotteTheHarlot

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,054 posts
  • Joined 24-September 07
  • OS:none specified
  • Country: Country Flag
The Compaq Win98se CDROM I have seems to be an "update" disc rather than "full install". It is an original blue and silver distribution disc and has this in small print: "This program will search your system to confirm your eligibility for this special update edition".

I did an audit between the Microsoft Windows 98se and Compaq CDROMs and found three main files of difference in the \Win98 folder, (Compaq shown ) ...
1999-04-23 ... 17:22 ..... 168,096 ... Dossetup.bin
1999-04-23 ... 17:22 ... 1,351,645 ... Precopy2.cab
1999-04-23 ... 17:22 ...... 37,299 ... Setup.txt


The CDROM structure is largely identical, however 2 subfolders are removed from the Compaq disc that appear on the Microsoft disc ...
\Tools\Admin
\Tools\Nettools


Additionally there is one extra file on the Compaq disc not on the Microsoft disc ( and probably not of consequence ) ...
\Drivers\Printers\Hp\Djet690c\Disk2\Hpf69r08.gid

Within the \Win98 folder, there are three files on the Microsoft disc missing from the Compaq ...
\Win98\Format.com
\Win98\Oemsetup.bin
\Win98\Oemsetup.exe


Full stop here. I believe this means that the Compaq CDROM is considered an "Update" disc rather than full install, because of the lack of format. I thought they were essentially the same in those days, but I may have mis-remembered. Anyway, continuing ...

Many of the CABs are binary different but it is because of 7 files that appear in almost all of the Microsoft CABs that are missing from the corresponding Compaq CABs. So when you WinDiff the two CDROMs there is a large list of differences until you compare the CAB contents. These are the 7 files that repeat in almost every CAB on the Microsoft disc but removed from the Compaq disc ...
Dibeng.dll
Gdi32.dll
Iosclass.dll
Krnl386.exe
Ntdll.dll
Systhunk.dll
Vfd.vxd


Additionally Compaq removed these files from their version of Win98_74.cab which exist on the Microsoft CDROM ...
Under~10.wav
Under~11.wav
Under~12.wav
Under~13.wav
Under~14.wav
Under~15.wav
Under~16.wav
Under~17.wav
Under~18.wav
Underw~6.wav
Underw~7.wav
Underw~8.wav
Underw~9.wav


The differences that matter all occur in PRECOPY2.CAB where most of the INFs have the references to those 7 extra Microsoft files edited out. Whatever driver update files that the OP ran which require Compaq branding, the references will most likely be found within these 22 files that differ between the two CDROMs (Compaq shown ) ...
1999-04-23 ... 17:21 ...... 54,959 ... copy.inf
1999-04-23 ... 17:21 ...... 56,353 ... copy1.inf
1999-04-23 ... 17:21 ...... 50,498 ... copy2.inf
1999-04-23 ... 17:24 ...... 76,410 ... default.sfc
1999-04-23 ... 17:21 ...... 45,747 ... del.inf
1999-04-23 ... 17:21 ...... 35,342 ... del1.inf
1999-04-23 ... 22:22 ...... 40,816 ... ieeula.chm
1999-04-23 ... 22:22 ...... 23,355 ... iesupp.chm
1999-04-23 ... 17:31 ...... 56,006 ... layout.inf
1999-04-23 ... 17:31 ...... 57,187 ... layout1.inf
1999-04-23 ... 17:31 ...... 55,036 ... layout2.inf
1999-04-23 ... 22:22 ...... 26,204 ... lic_help.txt
1999-04-23 ... 22:22 ...... 40,816 ... license.chm
1999-04-23 ... 22:22 ...... 26,204 ... license.txt
1999-04-23 ... 22:22 ...... 23,355 ... mtshelp.chm
1999-04-23 ... 22:22 ...... 23,361 ... setupc.inf
1999-04-23 ... 22:22 ...... 17,997 ... setuppp.inf
1999-04-23 ... 22:22 ..... 745,168 ... setupx.dll
1999-04-23 ... 16:35 ...... 61,528 ... subase.inf
1999-04-23 ... 22:22 ....... 8,116 ... support.txt
1999-04-23 ... 22:22 ...... 57,292 ... webhelp.chm
1999-04-23 ... 16:35 ...... 28,028 ... winver1.inf


The most likely solution for OP will be to obtain a proper full install Compaq version of the Win98se disc and re-install. An alternative method might be somehow converting his official Microsoft full install disc to Compaq branded by obtaining those three files: DOSSETUP.BIN and PRECOPY2.CAB and SETUP.TXT and dropping them into the \Win98 folder and overwriting the originals and then burning the disc again. This would keep FORMAT and the other files in place. Whether this would work I am not sure. Due to the relative lack of information given, I am not sure if his Hard Drive actually has Windows physically in place, which is a requirement for the "update" to work ( it probably on requires one file really ). So this is up in the air. Since this is Win9x you could even skip the burning of the disc and just copy the entire contents to the harddrive in the laptop and running the SETUP from a dos prompt if you can boot to clean DOS.

Personally, here is how I would do this. Pull the HDD out, slave it in another computer ( rigged for 2.5" drives ). If there is any Windows installation still on that HDD I would back it up temporarily, and then format it FAT32 with system ( so it boots ), copy the Win98se Compaq CDROM to the HDD, ( and copy the backed up Windows installation if it existed ). Put it back in the laptop, boot to DOS and then run SETUP from the copied folder. If the transplant of those Compaq files onto a full install CDROM does not work, I would have to Google to find the trick to make it full install.

I believe this is do-able, but might take a few tries. Still better to just find a Compaq full install Win98se on eBay I think. The OP has not given nearly enough information though. Depending on specs there is some chance you might be able to get Win2k working.

P.S. Here are all the disc comparison details ...
Spoiler

... Let him who hath understanding reckon the Number Of The Beast ...


#8
CharlotteTheHarlot

CharlotteTheHarlot

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,054 posts
  • Joined 24-September 07
  • OS:none specified
  • Country: Country Flag
Details about that computer are at the HP website ...

Compaq Presario 1600-XL145 Notebook PC ( at HP website )

- Product Specifications

- Software & Driver Downloads

The Downloads are all still alive and direct ...

Spoiler


Are any of those listed downloads the one that you have and require some Compaq branding?

... Let him who hath understanding reckon the Number Of The Beast ...


#9
togermano

togermano

    Member

  • Member
  • PipPip
  • 105 posts
  • Joined 07-July 08
those are the drivers i downloaded yes...

Edited by togermano, 12 January 2013 - 03:06 PM.


#10
submix8c

submix8c

    Inconceivable!

  • Patrons
  • 4,331 posts
  • Joined 14-September 05
  • OS:none specified
  • Country: Country Flag
Seriously find it hard to believe that the Drivers are somehow "branded".

Would it be possible to give us a SPECIFIC "Error Message"?

unfort the compaq drivers check to see if its a windows 98 that came from compaq off their restore cd

Your initial post is really vague.

Someday the tyrants will be unthroned... Jason "Jay" Chasteen; RIP, bro!

Posted Image


#11
CharlotteTheHarlot

CharlotteTheHarlot

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,054 posts
  • Joined 24-September 07
  • OS:none specified
  • Country: Country Flag

Seriously find it hard to believe that the Drivers are somehow "branded".

That's what I thought too.

I downloaded the driver files ( see the direct links above ) and noticed that many of them cannot be easily extracted. They are using a custom installshield wrapper so I am guessing that the dependency is buried in there. They probably seek out a registry value or file location before they extract.

This is not normally the case in my experience. I like to grab all the drivers, extract them, build a folder tree with all the drivers and then copy that tree to a hard drive root before windows setup so that when the installer is looking for drivers I can just aim it at the tree and kind of pre-configure windows to have a set location for the required INFs and system files.

Compaq chose a terrible strategy, one that matches its reputation really. Its no wonder so many people complain about them.

... Let him who hath understanding reckon the Number Of The Beast ...


#12
bpalone

bpalone

    Member

  • Member
  • PipPip
  • 175 posts
  • Joined 04-March 09
  • OS:Windows 2000 Professional
  • Country: Country Flag

Donator

I have that same model and I don't recall ever having a problem installing from a straight 98se CD (i.e. non Compaq). I am thinking that I downloaded my drivers from Compaq (may of been before the merger). It has been a while since I have installed the OS on any of them (I have more than one, I like the sound system they have), but I don't recall any issues. I'm wondering if maybe the website is serving up the wrong drivers?

If you don't have some luck getting them to work, let me know and maybe we can figure a way to get you copies of my drivers. I will have to look to find them, but I know I have them around here and I'm to tired right now to take the time.

Let me know.

#13
dencorso

dencorso

    Iuvat plus qui nihil obstat

  • Supervisor
  • 5,952 posts
  • Joined 07-April 07
  • OS:98SE
  • Country: Country Flag

Donator

WinRAR 4.20 can unpack the drivers, at least those I tested, then the Universal Extractor can take care of the cabs.

#14
CharlotteTheHarlot

CharlotteTheHarlot

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,054 posts
  • Joined 24-September 07
  • OS:none specified
  • Country: Country Flag

WinRAR 4.20 can unpack the drivers, at least those I tested, then the Universal Extractor can take care of the cabs.

I guess maybe they added more installshield formats to WinRar 4.x because v3.9x doesn't understand it, nor does anything else like 7zip.

Try this one: Presario Notebook Trident Cyberblade Cbi7 Graphic Drivers 2001-02-18 , Version:5495-19A, 14.3M

If you use UniExtract can you let me know which application it uses to open it? I'm pretty sure I have all the utilities it uses.

Thanks.

P.S. Just getting the files out might still be the easy part. What I want to see are any dependency checks ( or pre-install and post-install actions ) are coded into the wrapper to find what Compaq branding it is looking for. Getting these out of Inno sometimes work ( Disasm.exe CompiledCode.bin ) but most of the others like installshield, NSIS, Indigo are lost in the extraction. This is one of the gripes I always had about setup programs, their native ability to process secretly with no real way to see the detailed script.

... Let him who hath understanding reckon the Number Of The Beast ...


#15
dencorso

dencorso

    Iuvat plus qui nihil obstat

  • Supervisor
  • 5,952 posts
  • Joined 07-April 07
  • OS:98SE
  • Country: Country Flag

Donator

Try this one: Presario Notebook Trident Cyberblade Cbi7 Graphic Drivers 2001-02-18 , Version:5495-19A, 14.3M

That's what Murphy's Law is all about. I was able to unpack both installers I tried (just two of them)... But the one above resists the WinRAR 4.20 / UE strategy I used with those others. It seems you're right: it says it's a "Compaq Builder Generated Installation Executable", and seems to be a customized InstallShield. It'd be necessary to run them through a debugger to get them to brute-force unpack case-by-case... And that's more work than I can do right now. Sorry for raising unwarranted hopes. :blushing:

#16
CharlotteTheHarlot

CharlotteTheHarlot

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,054 posts
  • Joined 24-September 07
  • OS:none specified
  • Country: Country Flag
Some of this probably does not directly affect the OP ( togermano ) who is doing a full re-install, but this information might help those that Google into this thread looking for information about those Compaq files.

I took a closer look at those Compaq drivers since every so often I get a Compaq in for repairs, virus cleaning, reinstall, etc and always wind up trying to get the drivers out of the setup wrappers. This has been a pain in the butt for years and I am still looking for the key to extracting these and I am afraid to say that with what I found yesterday, it may never be possible due to very erratic and sloppy programming by the geniuses at Compaq. I have already tried the usual methods besides WinRar, that is WinZip, 7zip, InstExpl, and a variety of other generic tools. I also tried the specific Installshield decompilers ( Icomp, I5, I6, etc ) and they fail as well. There may be a few more left to use that I will eventually get around to. I also heard that some Compaq internal tools leaked out but I do not believe I have yet come across them.

Anyway I located a PDF that purportedly explains a way to get the files out of the installer ...

Spoiler

Frankly, I've seen these instructions before and they never worked before, but I gave it a shot again on this group. For this laptop there are 20 available downloads and only 4 are perfectly extractable using WinRar. Out of the 16 remaining maybe another 5 can be partially or wholly examined by gathering files from various folders ( Temp, Root, etc ) from the installer while it is running.

From testing those 16 non-extractable files ... I got 9 completely different kinds of results! This means that there are at least 9 different ways these Compaq ( mostly custom installshield wrappers ) installers were compiled. They simply did not follow their own guidelines meaning those extraction instructions will not work except perhaps on one file. Here is a summary of what actually happened ...

sp11763.exe .... 8,268,891 ... Extracted with WinRar
sp12659.exe ... 15,365,177 ... Failed (7)
sp14107.exe ...... 377,504 ... Failed (6)
sp14776.exe ...... 280,149 ... Failed (7)
sp15238.exe ...... 718,941 ... Failed (6)
sp15535.exe .... 1,289,288 ... Failed (5)
sp15602.exe ...... 810,833 ... Extracted with WinRar
sp15770.exe ...... 296,296 ... Failed (2)
sp15932.exe ...... 586,142 ... Failed (3)
sp15949.exe ... 12,528,827 ... Failed (4)
sp16205.exe ... 21,795,313 ... Failed (4)
sp16211.exe ...... 337,033 ... Failed (3)
sp16212.exe ...... 300,522 ... Failed (3)
sp16778.exe ... 14,998,950 ... Failed (8)
sp17363.exe .... 9,197,688 ... Failed (9)
sp17385.exe .... 8,909,407 ... Failed (4)
sp17398.exe ...... 380,075 ... Failed (2)
sp18184.exe .... 3,958,640 ... Failed (1)
sp18759.exe .... 4,815,008 ... Extracted with WinRar
sp20598.exe ... 10,478,980 ... Extracted with WinRar


More details and notes are here ...

Spoiler


Speaking for myself, the main reason to be able to extract the files is to construct a directory with them all expanded that can be copied onto a HDD before or during a Windows install so that the Windows setup can be directed to the folders and use them at will. Those PDF instructions are meant for similar scenarios like making a driver disc or deployment image. Anyway, there are good reasons not to trust an installer created by career under-achievers masquerading as programmers at a company like Compaq ( and others :yes: ) who have little adult supervision and certainly no real quality control. Those reasons quickly became quite clear. Here are some important notes ...

None of those installers followed the commandline parameters outlined in the PDF, disregarding both the /e to cancel automatic and the /f to select a target folder. Worse, two of them used /s silent install even without it being specified. This is sloppy and dangerous. At compile time they are supposed to import a template that embeds common modes and commandline parameters. That is how a real company ( and independents ) operate. That's professional. Since almost all these files originate in the same timeframe it does not bode well for the sum total of Compaq and HP ( don't get me started ) history because there must be hundreds of different variations in existence now.

Files were written into C:\Cpqs and C:\Cpqdrv and C:\Sp15770 and C:\Sptemp and C:\Appl.zip ( that is a folder ), not to mention C:\Temp and C:\Windows\Temp and even %UserProfile%\Local Settings\Temp. All these locations from the few of those installers that even ran. Additionally, they managed to create two executable autorun files ( on WinXP no less ) C:\Cleanbl.bat and C:\Windows\Dosstart.bat. Their contents here ...

Spoiler


At least one of them created a buttload of registry gargbage that has no purpose I can see. I recognize some of these as from Vcomm System Commander or one of their related programs ...

Spoiler


The OP ( togermano ) might want to take note of this: At least one of the installers has a programming error, sp14776.exe ( "SMSC USB Ethernet Driver" ), where the installer is looking for the wrong file in the TEMP folder, it is trying to unzip "156080.zip" but the actual payload the installer drops into TEMP is 156323.zip. I see no way for ths update to actually work unless it is only a mistake in a dialog box. But the files can be retrieved from TEMP if it does not work ...

Spoiler


Finally saving the worst for last, at least one of those installers which I have not yet identified, deleted the entire contents of C:\Temp, including all subfolders!. WTF! This is not just sloppy, it is incomprehensible. No setup program should ever remove files that it did not install, and even then they should still be prompted with a choice. Real programmers create private sub-directories off the TEMP folder and work in there, and delete that and ONLY that during cleanup. These programmers are lucky I am not their boss. Seriously, this kind of thing puts in perspective why long time veterans go through all the trouble of tearing apart setups rather than simply trusting the authors.

EDIT: typos

Edited by CharlotteTheHarlot, 14 January 2013 - 03:06 PM.

... Let him who hath understanding reckon the Number Of The Beast ...


#17
M()zart

M()zart

    Member

  • Member
  • PipPip
  • 279 posts
  • Joined 17-June 08
May be you could use regmon/filemon to determine which registry keys/files are actually accessed by the installer when performing this check.

#18
CharlotteTheHarlot

CharlotteTheHarlot

    MSFN Master

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,054 posts
  • Joined 24-September 07
  • OS:none specified
  • Country: Country Flag

May be you could use regmon/filemon to determine which registry keys/files are actually accessed by the installer when performing this check.

Yeah, that is pretty much the only way other than firing up WinDbg. What I was trying to do was complete an old bucket list item, extracting these stupid Compaq drivers and hopefully get the install script directly, but it is probably impossible. I won't be repeating the experiment again soon because as I said the OP has a Compaq and is doing a full install and should probably have no problem. But if he does have more problems, someone here can walk him through RegMon/FileMon. If I had more time when I did these tests, since I was on WinXP I could have used ProcMon to locate the references the installer searched for. But time is money.

... Let him who hath understanding reckon the Number Of The Beast ...





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users