Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hey get this, I bought a new machine from Dell, I also got Win2k Pro with it. Well I decided that I couldn't use W2K on the new machine cause the kids kept messing it up. So I decided to put 98SE on it. But I like W2K, So I decided to put it on one my other computer, But guess what? I can't. It says for use with a Dell Only. So here I am with a 250.00 OS that I can't use. Any Ideas how Dell does this to the CD, and boot disks? I paid for It, I should be able to put It on any one machine I want to. Thanks

Well Jason,
Personally I would call DELL and B*tch.
As far as making your Current CD work with a Non Dell machine thats probably not gonna happen. But Call Dell and tell them to send you either $250 or a CD you can use on other machines =)

First, you paid for the right to use w2k (license), not for w2k itself. It's the same for any software!
The Win2k CD from Dell or several other PC manufacturer such as compaq contain an installation script. This is the reason why it cannot be used for other computers. the script would hang anyway without this security check.

So what now, Am I just stuck with this OS,I paid for the right to use one copy of it. I should be able to use it on any machine. How do they know if it's a Dell or not? BIOS?

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 nameIf 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.

Thanks to FJ for this little GEM...
I suspect this has all come about because of M$ pressure on Dell etc. regarding their (Dell etc.) issuing full version CD's of the M$ OS's... which can/may be used on other systems - and M$ wants to force folks to buy more copies - from M$... Also an attempt by M$ to prevent the clearance/discount outlets from selling on unused/surplus full version CD's... originally sourced to manufacturers...
M$ is pressuring 'big' names top issue only recovery CD's - much like Packard-Bell etc... which will really be near useless to everyone - including the original client.
When XP arrives M$ intend to restrict the number of (re-)installs for a given CD - probably to around 20 or 30 'uses'; after that one has to contact M$... to go further. The system will require a registration of the OS to M$, and this will included hard-coded info. regarding the actual PC involved (including current hardware etc). Change hardware (HD, VGA card, modem etc. etc.) and you may not be able to re-install the OS...
It's already been tried out in Beta-tests/mode in Canada (elsewhere too?) - 'clients' being polled on their response to the proposition... with an apparent decision to invoke this limit... The future does not look good!

Microsoft mandates computer manufactures use recovery disks now. What they do is the recovery disk you get checks the bios chip that has a programed code to match a disk, this is how they make it only work on your PC. As far as using W2k on another machine you have a OEM VERSION and is NOT licnesed to you but the machine and legalily can not be put on a another machine, thats why we recomend you buy retail version. On there new versions of XP & office you have to enable the software in 30 days or it is disabled, once you go to microsoft to enable you can NOT DO it again. I work for a PC manufacture and this is what we are required to do to keep selling Microsoft products.

I read that the number of installs of the XP OS is going to be limited to 3 - 5. That comes from the AnchorDesk of Zdnet. If your system crashes more than that you will need to call M$ for a new registration code.
Does anyone have any idea how it's possible for a non-writable disk to know how many times it's been used?

I edited the BCHK32.exe file as described, setup runs fine until the first time the machine has to reboot. During reboot the " This software is liscensed for use on Dell systems only" message flashes and the system halts. Does anyone have any ideas on how to correct this? I have all the Win 2000 files on my HD w/ only the edited version of BCHK32.exe on the machine.

Go to page 10 of this forum and look up a post by UNDO. It about halfway down the page. You better hurry though that page is going into archive fast. Email the guy with your question.

![]() |
Win2k NTLDR on seperate d...
|
Batch File directory crea...
|

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