Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Does anyone out there know how I can use a Dell reinstalltion CD on a non Dell machine ?
I Purchased a Dell Precision 330 a few weeks ago and it comes with a CD containg Win 2K and SP1. I already had a copy of Win 2K Server which I have installed on the Precision. This means that the copy of Win 2K Proffesional that came with the Precision is not being used. I want to install this copy of Win 2K on my old PC, but when I boot from the CD it says its a non Dell machine and won't go any further.
So I booted to my existing operating system and tried running the Win 2K setup from there. That didn't work either.
When I run the setup from within my existing operating system, it seems to look for a file called 'bchk32.exe' in the i386 directory. So I copied the entire CD to my hard drive and deleted the 'bchk32.exe' from the i386 directory. Unfortunately, when I tried to run the setup.exe from the hard drive it didn't do anything. So I put the 'bchk32.exe' back in the i386 directory, ran the setup.exe from the hard drive again and it ran as if it was running from the CD - in other words, it brought up a message saying this was a non Dell PC.
I know that this protection is here for a reason, but as I now have Win 2K Server on my new Precision, the licence that came with the copy of Win 2K Pro is not being used. So I want to install it on my old PC.
Sorry about the long explanation, but I wanted to make things as clear as possible.
Can anyone help out with this ?
Thanks in advance for any help.
rich

I don't believe that it is possible to do what you are describing.
When Dell distributes recovery disks, it is created by building images based on preconfigured machines (i.e. - it builds the OS kernels/hives/driver lists/etc. on the machine's existing microprocessor, motherboard, bus speeds, HDD, RAM, BIOS, etc.)
If trying to install this image on a totally different type of machine, (assuming you could get Windows to install) you will encounter nothing but instability and other assorted errors.
There may be some sort of Internet tool to trick the program into running, but as I said you will encounter many unrepairable problems.

here is a thought. I dont know how this works, but logically, the only way your system can figure out that it is not a dell machine is by checking your bios. it looks for 'bchk32.exe' (which could be a short for bios check) and then says it is not a dell machine. if try to replace it with 'bchk32.exe' from regular, non-dell w2k CD, it might just work(even the file from your server cd might work, what do you have to loose if it doesnt?) give it a shot, and let me know if it works. I can see this info becoming useful sometimes.

Yes, you will probably be able to trick the installation into working.
BUT
The image will NOT be stable! You WILL run into a MYRIAD of problems, so I DONT see the point in doing is. It seems kinda of silly to waste a great deal of time in getting something to work only to realize that it is not a workable solution to reinstalling an OS.

Have you tried it GrtOne???
If a guy has some time on his hands, why not give it a shot? It only takes an hour to do that. I dont think Dell would go through all that trouble. If I had a dell CD, I would give it a shot just for the hell of it. He did pay for a copy of W2K when he bought dell, he has every right to use it as he likes, legally. So if dell is being a b...tch about it, it would only make me feel good if it could be done.

I was sent this solution a long time ago by one of this sites regulars.
Subject: New Dell OS won't install On Different machine.Reply:
THis is a copy of an email I received from someone that visits this site often, so you may get a more complete answer later on. There was no attachment sent to me so don't ask for it. I have read this letter and it sounds like he knows what he's talking about,so good luck to you....After you do the fix you may want to burn a new cd with the updated file
for future use or run the installer from a harddrive if you dont have a
burner.
Let me know if you have any questions.
Good luck.
The file in question is "Bchk32.exe", you will find it in the "I386"
directory of the win2k install CD. Simply deleting this file will not
work you have to edit the file with a hex editor as described below or
just replace it with the attached file that I have already edited.
Here's how bchk32.exe works:
When setup.exe is executed, it launches bchk32.exe or launches some
other program which in turn launches bchk32.exe. Then, bchk32.exe
checks the bios to determine if the computer is a Dell or not. When
bchk32.exe is launched, it is passed a command line argument (i.e.,
when you type "unrar file.rar", the file.rar is a command line
argument), this argument is a directory/file name that tells
bchk32.exe where to save the results of the bios check. The file name
is generated randomly but always ends in .tmp (a temporary file), the
directory when the file is saved depends on your system (on win 95,
its "C:\WINDOWS\TEMP\"). If a Dell bios is detected, the file will
contain "+++" (3 bytes), if it fails the test, the file will contain
"---". I have tried replacing bchk32.exe with my own program that
simply creates the file with the name and location supplied in the
command line arguments, writes "+++" to the file, and then closes the
file and exits. This program however, did not work. So, obvioulsy
bchk32.exe does something in addition to this. While viewing
bchk32.exe with a hex editor, I found where it stored the "+++" and
"---". With the hex editor, I changed the "---" to "+++" so that even
if the test failed, "+++" would be the result and would get stored in
the file. To my surprise, this worked.
If you have a hex editor follow these instructions:
1) start the hex editor and load "bchk32.exe"
2) goto offset/location 1F92 (hex) or 8082 (decimal)
3) you should see "---" displayed at this location, change it to "+++"
4) save the edited file using the original name
If you don't have a hex editor, you can download one form just about
anywhere, I like UltraEdit-32. Its time limited for 45 days but is
fully functional until then and with a little searching you should be
able to find a serial number for it. I'm still looking for the seial
number myself. You can D/L UltraEdit from http:\\www.ultraedit.com.
If you don't want to go the hex editor route, just replace your
bchk32.exe file with the attached one that has already been edited,
this option may only work on Dell systems.

I used HackMan Hex Editor And did the above and it indeed does work. The thing is.. at least on my Dell CD. the offset/location 1F92 (hex) or 8082 (decimal) is different. Its really simple to do. And it works. Just look in the file for the "---" "+++" it says dell system inbetween. I guess on some dell cds its in different hex locations or something.
-Tim

The listed comments in response 5 get you started on a non dell pc, but as stated apparently only work if you have a dell system. You get as far as the first reboot then it tells you your system is not a dell pc, mine is but the dell needs to run NT4 because our network boys run NT on all the machines and won't let me have the dell on the network, hence my attempt to install it on a completely non Dell pc as a standalone.

I also can only get to the first restart and then I get the message that the software is for a Dell only.
My situation is similar to others. My Dell system is running different OS and I want to install the original DELL OEM software on another non-Dell pc.
Any help would be greatly appreciated.

Same first-restart problem.
WINNT.EXE won't run in DOS at all whereas WINNT32.exe will get to the first retstart (via Windows). Is there a link?
Can anyone out there help?

if any1 comes up w/ something on this please let me know i can get to first boot the boom nothing. I think its loading a program like boot.ini or something like that if i come up w/ any thing i will let u guys know..

Thanks Booty..I got as far as hex-ed bchk32,
..lol...I've converted 6 cd's into coasters,
but now got win98/w2k pro/red hat triple boot.
(looking at w2k pro..me thinks...was it worth it)

You can make life much easier by using the command line argument for \setup that forces it to bypass the search for hardware devices..
Unfortunately I don't have my cd handy to tell you what it is but type setup /? to find out.

![]() |
Quotas in Win2k
|
Disaster Recovery w2k ser...
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |