@Jdobbs Machine ID changes on same computer with no hardware changes [Archive]

View Full Version : @Jdobbs Machine ID changes on same computer with no hardware changes

johnnyquid

17th December 2005, 13:24

@Jdobbs

I love your program and I do not have a problem with paying for it however I have noticed that even minor configuration changes to one's computer can cause the machine id the change. For example, the machine ID changes for me depending whether or not I am connected to the internet and wheter or not I have my wireless network enable. For my one machine without any hardware changes, I already have the following machine ID's:

350089E3 (not connected to internet)
1948E0F8 (Connected to internet)
FF48AA77 (wireless network enabled)

Since I registered while connected to internet now I must be connected to the internet or RB complains about the machine ID not being the same and wants me to get another key. I am concerned that it appears that only minor configuration changes on the computer causes machine ID changes, I will use my allowed 5 changes very quickly. Might I suggest that the code that calculates the machine ID be changed to not cause different machine ids for minor hardware and configuration changes.

jdobbs

17th December 2005, 14:35

Adding or removing a network card changes the SYSTEM_ID -- I thought that was something that wouldn't happen very often.... apparently wrong.

I'll fix it and get a new version out.

I really wish this keying crap wasn't needed. This is a real pain-in-the-ass and takes way too much time from real programming... Hell, when I first started this I though the fact that there was a freeware version would make this all unnecessary. Silly me.

rachel0227

17th December 2005, 15:14

I was initially able to update to Rebuilder Pro V1.05 and download a key. However, after completing a Disk Cleanup and defrag via Windows XP, Rebuilder again was asking for me to download a key (same computer, no other changes). When I tried to get another key file, I get the message 'Could not connect to server'.

Jdobbs, I know you are working on this, but just wanted to let you know that a Disk Cleanup (no hardware changes) also causes issues with the key file.

Thanks again for a great program!

jdobbs

17th December 2005, 15:22

Your key is still the same, though, right? I have no idea how that might have happened, as nothing associated with a defrag or cleanup should change the system id. Was the system id the same?

idbirch2

17th December 2005, 19:43

I just ran a disk cleanup and tried DVD-RB again, still works fine. Its a coincidence, something else is causing your System-ID to change. There are some theories being thrown around about computers with multiple NICs, maybe you should look into this....

jdobbs

17th December 2005, 20:09

rachel0227

17th December 2005, 21:38

arsmori

17th December 2005, 22:13

If you have a NIC that is removed or added -- that definitely has an effect. I've removed that portion of the SYSID check for v1.05.1 -- as I've realized it probably wasn't the best idea for notebooks...

I think the way XP deactivate a network is by disabling access to the device (virtual or real) driver. If I go in network connections and I simply deactivate the local network (to which my NIC is associated), my system identifier change... I'm guessing some third party network manager might do exactly that too.

jdobbs

17th December 2005, 22:20

@jdobbs:
I'm not sure if it is the same key, as I failed to write the first key down when I initially updated to V1.05. I did do an install and remove of a program not associated with DVDRebuilder or video processing prior to doing the disk cleanup. I also did not add or change my NIC.

Update: After having shutdown and re-booted my computer, I was successful in opening Rebuilder without being asked to download a key. This is very strange, but I'm glad I'm up and running! If you run something that cleans the registry, there's a chance it may remove your registered e-mail name. If that happens, a screen will pop up asking you for the registered e-mail -- but it doesn't change the SYSTEM ID or require that you download the key again as long as you enter the correct address. But it would have done that with any of the previous versions as well.

apfraats

18th December 2005, 01:55

@JDOBBS:

Just a thought, no more no less....

But if yoiu determine a machine-id, are you really looking at the hardware layer ??

Because if you look to the machine configuration on a somewhat highher level, you'll get these kind of problems....

So if you look at the presence of a NIC at the lowest level, it won't make a difference if it is enabled or disabled in Windows... It's always there....

I suppose you let compute the ID at a somewhat to high abstraction level, maybe using the HAL or even above, but you should look into the 'real' hardware configuration.

I'm no specialist at all about this, but you should be able to compute a number based on real hardware, bypassing all possible layers that can infuence the configuration on a higher abstraction level.

To mention just an example: Using a driver that adds a 'DVD-ROM' drive from a mounted ISO file.

To make this work this driver will be implemented at the lowest level possible, to prevent any programm from seeing it's not a real DVD-ROM.....

So you have to look beyond these layers and go to real hardware if possible.

Then that added DVD-ROM will NOT show up...

I'm glad you implemented a strict copy-protection, simply because you have to....

I won't allow anyone to use any computer-id that's counting on behalve of my license.

5 is enough I think, for most people. However with my new system I will reach this limit already...

there is one laptop now using DVD-RB-PRO, that I use with external huge harddisk when I'm not at home.

And I use 3 'power' computers already to leave them doing work at night.

With a new system I reach 5....

jdobbs

18th December 2005, 02:29

I do look at the lower layer layers... but unfortunately there are exceptions to everything. For example, if you are using a notebook computer and you insert a PCMCIA NIC ---> suddenly there is new hardware. Removed it and insert a wireless adapter... it changed again. That was the mistake on this one. For desktop machines it's pretty safe. Most NICs these days are part of the motherboard, but then there are those "virtual devices" that pop up on the USB bus...

I've just removed the NIC from any consideration in determining the SYSTEM ID... it's too risky. There are plenty of less volatile factors that can be used...

I'll be releasing a new version (v1.05.1) tomorrow that doesn't consider the NIC. It also includes a fix for the connection problem and upgrades of HC Encoder and ReJig. I'd planned to do it tonight, but it's just too late -- as you have to babysit the mail servers continually while the distribution occurs.

I really feel bad about the folks who couldn't connect... I never expected that. It was an error in the way I processed the connection that caused it. I sent out a zip file with test code to a group of folks who had the connection problems, and so far it fixed it on all of them.

As for the 5 SYSTEM ID limit... that's just an arbitrary number that is managed at the server end. If it seems like it's too small I can flip a switch and raise it... or start over at zero. Just as long as it is for the personal use of one person and his/her immediate family -- I'm not worried about it. My problem isn't what registered users do. It's that a crack gets released and the one-sies and two-sies I get in registered users completely stops. I don't mind working cheap... but working for nothing gets frustrating.

I truly wish I didn't have to do any of this... if I'd spent half as much time on menu encoding during the past two weeks as I have on this damn registration module and server, we'd all have been doing menus with v1.05.

Ok... enough whining.

SAPSTAR

18th December 2005, 13:06

Just a small contribution to the thread....
I'm working from home through a VPN, I started it, a few minutes later DVDRB died (when it started rebuilding), and then it asked to download a new key, I clicked Get it...and I had the reply : No connect possible. (I was able to connect to any IP port on internet...)

Knilch

18th December 2005, 13:27

Hell, when I first started this I though the fact that there was a freeware version would make this all unnecessary. Silly me.

I think the "problem" is that the features of DVD Rebuilder Pro are overwhelmingly superior to DVD Rebuilder Standard. People always want the best (which is understandable) but some of them seem to think, that god himself is a software engineer and provide them with the latest software, so why paying for it... In fact, I sell software for DVD archiving in Germany, Austria and Switzerland at a prize of 9,99 Euro (a feature-limited freeware version is existing, too!). I could hardly believe it, when I saw pirated copies of this software on different websites and p2p networks. This led me to the conclusion that piracy will always prevail, no matter the prize.

jdobbs, you are not alone :) Silly me, too *g*

Merry Christmas to all of you!
Knilch

jdobbs

18th December 2005, 13:57

CirTap

18th December 2005, 14:02

Hi,
I'm glad I have not yet updated to 1.05 :-) I frequently swap harddrives (ext. USB) and I'm going to replace one next week in my desktop machine. Basically there are only 2 computers "involved" here doing DVD stuff, so 5 IDs would be enough, but I suppose I may hit this limit pretty fast if I install 1.05 now -- I'm patient, and wait for a fix.

@jdobbs: can you create a "dummy" version of the app that just calculates IDs but does not save them for DVD-RB, so VIPs can test-proof your concept, and find out when the system-ID changes if they remove/deaktivate pluggable devices? I believe people would be happy to help you iron this out.
The test-app could create a log file with device-info and the system ID we could send to you for further diagnostics, an "annotion" should be possible if you plan to send this from inside the application.
That should give you a possible list of circumstances of "invalid" recalculations.

Have fun,
CirTap

jdobbs

18th December 2005, 14:13

If you run REG-RB.EXE that is included in DVD-RB v1.05 and v1.05.1, it will tell you what your SYSTEM ID is. You can make changes, etc, and run it again. But I think you'll find that (other than the NIC issue which has been fixed for v1.05.1) the system id won't change without a major system modification.

I'd like to reemphasize that even the problems that have been fixed in v1.05.1 don't affect most DVD Rebuilder users. But, of course, they still have to be fixed, and that's why I'm releasing it.

As I said earlier, this system isn't intended to limit registered users at all... if you run into a problem with the 5 System ID limit, just send an e-mail.

jdobbs

18th December 2005, 14:21

@SAPSTAR

I tried to send you a PM but your box is full...

CirTap

18th December 2005, 14:54

this system isn't intended to limit registered users at all if this is addressing my post, I didn't intend to make it sound like this. I'm fine with having 5 keys.
the system id won't change without a major system modification. pls. define "major system modification", just to know, what to expect. Would installing/replacing hard disc(s) fall into this category, or a new DVD drive/burner? I believe this is nothing uncommong for people dealing with Gigs of data :-)
And, yes I understood that you're willing to "grant" more keys to someone upon request. I (we?) really appreciate that, and thanks a bunch!
I admit I have not even installed 1.04 yet, I just want to take the proper procautions if I have time again to focus on that matter in a week or two.

Have fun,
CirTap