I want to create a file which is locked to host id of computer. can anyone tell me how to detect host id of a computer in excel.

hi,

sHostName = Application.UserName

isabelle


Le 2013-01-05 11:33, a écrit :
I want to create a file which is locked to host id of computer. can anyone tell me how to detect host id of a computer in excel.

also,

sHostName2 = Environ$("computername")

isabelle

Le 2013-01-05 11:55, isabelle a écrit :
hi,

sHostName = Application.UserName

isabelle


Le 2013-01-05 11:33, a écrit :
I want to create a file which is locked to host id of computer. can
anyone tell me how to detect host id of a computer in excel.

try...

Private Function Get_BIOSserialNum() As String
' Gets the serial number of a PC's BIOS
Dim oWMI As Variant, vSettings As Variant, vBIOS As Variant

Const sComputer$ = _
"winmgmts:{impersonationLevel=impersonate}!\\.\roo t\cimv2"
Set oWMI = CreateObject(sComputer)
Set vSettings = oWMI.ExecQuery("Select * from Win32_BIOS")
For Each vBIOS In vSettings
Get_BIOSserialNum = Trim(vBIOS.SerialNumber): Next
End Function '//Get_BIOSserialNum

...note, though, that some clones won't have a serial number and so
you'll need to handle what to do in this case.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

wrote:
I want to create a file which is locked to host id of computer. can anyone tell me how to detect host id of a computer in excel.


what is host id?

On Sat, 05 Jan 2013 14:05:33 -0500, GS wrote:

try...

Private Function Get_BIOSserialNum() As String
' Gets the serial number of a PC's BIOS
Dim oWMI As Variant, vSettings As Variant, vBIOS As Variant

Const sComputer$ = _
"winmgmts:{impersonationLevel=impersonate}!\\.\roo t\cimv2"
Set oWMI = CreateObject(sComputer)
Set vSettings = oWMI.ExecQuery("Select * from Win32_BIOS")
For Each vBIOS In vSettings
Get_BIOSserialNum = Trim(vBIOS.SerialNumber): Next
End Function '//Get_BIOSserialNum

..note, though, that some clones won't have a serial number and so
you'll need to handle what to do in this case.


Where do I place a private function? I have not previously ever
defined one.

So far, the macro area of my worksheet does not do it.

And how do I call it? no arguments, right? Just =call() in the
cell and it resolves?

So far I get a name error. I have yet to place it in the right
location so that it shows up in the function list.

On Sat, 5 Jan 2013 08:33:39 -0800 (PST), wrote:

I want to create a file which is locked to host id of computer. can anyone tell me how to detect host id of a computer in excel.

Here's a routine to obtain the MACAddress, from http://www.ehow.com/how_6920281_use-...c-address.html

============================
Option Explicit
Function GetMACAddress()
Dim objVMI As Object
Dim vAdptr As Variant
Dim objAdptr As Object
Dim adptrCnt As Long
Dim GetNetworkConnectionMACAddress As String
Set objVMI = GetObject("winmgmts:\\" & "." & "\root\cimv2")
Set vAdptr = objVMI.execquery("SELECT * FROM Win32_NetworkAdapterConfiguration WHERE IPEnabled = True")

For Each objAdptr In vAdptr
If Not IsNull(objAdptr.MACAddress) And IsArray(objAdptr.IPAddress) Then
For adptrCnt = 0 To UBound(objAdptr.IPAddress)
If Not objAdptr.IPAddress(adptrCnt) = "0.0.0.0" Then
GetNetworkConnectionMACAddress = objAdptr.MACAddress
Exit For
End If
Next adptrCnt
MsgBox "Your MAC Address is: " & GetNetworkConnectionMACAddress
End If
Next objAdptr

End Function
======================================

The function is scoped Private because it belongs to my licensing
component. You can delete that keyword.

The function is not designed to be called/use on a worksheet. It should
be called from another Sub in a standard module. Also, the function
should reside in a standard module. To use it...

Range("A1").Text = Get_BIOSserialNum

HTH

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

I recommend using WMI to obtain the BIOS serial number because all the
values recommended by you and Isabelle (thus far) can be
edited/changed. The only way to change the BSN is to replace the
motherboard. In the case of a clone machine returning an empty BSN, I
substitute with a hash value of that empty string via SHA256. When this
is combined with make & model it serves well enough for my purposes.<g

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

On Sat, 05 Jan 2013 18:34:51 -0500, GS wrote:

I recommend using WMI to obtain the BIOS serial number because all the
values recommended by you and Isabelle (thus far) can be
edited/changed. The only way to change the BSN is to replace the
motherboard. In the case of a clone machine returning an empty BSN, I
substitute with a hash value of that empty string via SHA256. When this
is combined with make & model it serves well enough for my purposes.<g

I agree with what you have written in terms of identification of a specific machine. However, the OP requested a method for obtaining the "Host ID". The various definitions I have seen for Host ID have been satisfied by the MAC address (or IP address) in Windows machines. I believe that is also the case for Unix machines (see hostid command).

On Sat, 05 Jan 2013 18:34:51 -0500, GS wrote:

I recommend using WMI to obtain the BIOS serial number because all the
values recommended by you and Isabelle (thus far) can be
edited/changed. The only way to change the BSN is to replace the
motherboard. In the case of a clone machine returning an empty BSN, I
substitute with a hash value of that empty string via SHA256. When this
is combined with make & model it serves well enough for my purposes.<g

Oh, and my machine is built by myself; your routine returns "To Be Filled By O.E.M." (Which is what is in all the Chassis Information slots except for Type: Desktop)

Ron Rosenfeld used his keyboard to write :
On Sat, 05 Jan 2013 18:34:51 -0500, GS wrote:

I recommend using WMI to obtain the BIOS serial number because all the
values recommended by you and Isabelle (thus far) can be
edited/changed. The only way to change the BSN is to replace the
motherboard. In the case of a clone machine returning an empty BSN, I
substitute with a hash value of that empty string via SHA256. When this
is combined with make & model it serves well enough for my purposes.<g

I agree with what you have written in terms of identification of a specific
machine. However, the OP requested a method for obtaining the "Host ID".
The various definitions I have seen for Host ID have been satisfied by the
MAC address (or IP address) in Windows machines. I believe that is also the
case for Unix machines (see hostid command).

No argument! The MAC address can be edited/changed and so if this
occurs it will break the methodology the OP is trying to implement.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

On Sat, 05 Jan 2013 20:03:28 -0500, Ron Rosenfeld wrote:

On Sat, 05 Jan 2013 18:34:51 -0500, GS wrote:

I recommend using WMI to obtain the BIOS serial number because all the
values recommended by you and Isabelle (thus far) can be
edited/changed. The only way to change the BSN is to replace the
motherboard. In the case of a clone machine returning an empty BSN, I
substitute with a hash value of that empty string via SHA256. When this
is combined with make & model it serves well enough for my purposes.<g

Oh, and my machine is built by myself; your routine returns
"To Be Filled By O.E.M." (Which is what is in all the Chassis
Information slots except for Type: Desktop)


Is there not a way to acquire the CPU ID (in Intel cases where it is
not turned off in the BIOS)?

After serious thinking Ron Rosenfeld wrote :
On Sat, 05 Jan 2013 18:34:51 -0500, GS wrote:

I recommend using WMI to obtain the BIOS serial number because all the
values recommended by you and Isabelle (thus far) can be
edited/changed. The only way to change the BSN is to replace the
motherboard. In the case of a clone machine returning an empty BSN, I
substitute with a hash value of that empty string via SHA256. When this
is combined with make & model it serves well enough for my purposes.<g

Oh, and my machine is built by myself; your routine returns "To Be Filled By
O.E.M." (Which is what is in all the Chassis Information slots except for
Type: Desktop)

Interesting that this is the stored value. Obviously this is different
than what's returned in a commercial unit. For example, I find it
typical of clone machines released by Gateway to return an empty
string. Your case is a new one for me!<g

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

It happens that CellShocked formulated :
On Sat, 05 Jan 2013 20:03:28 -0500, Ron Rosenfeld wrote:

On Sat, 05 Jan 2013 18:34:51 -0500, GS wrote:

I recommend using WMI to obtain the BIOS serial number because all the
values recommended by you and Isabelle (thus far) can be
edited/changed. The only way to change the BSN is to replace the
motherboard. In the case of a clone machine returning an empty BSN, I
substitute with a hash value of that empty string via SHA256. When this
is combined with make & model it serves well enough for my purposes.<g

Oh, and my machine is built by myself; your routine returns
"To Be Filled By O.E.M." (Which is what is in all the Chassis
Information slots except for Type: Desktop)


Is there not a way to acquire the CPU ID (in Intel cases where it is
not turned off in the BIOS)?

For all intents and purposes, the BIOS serial number IS the cpu's ID.
The only way to change it is to swap out the motherboard, which creates
a new cpu with a new ID.<g

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

On Sat, 05 Jan 2013 20:30:03 -0500, GS wrote:

Ron Rosenfeld used his keyboard to write :
On Sat, 05 Jan 2013 18:34:51 -0500, GS wrote:

I recommend using WMI to obtain the BIOS serial number because all the
values recommended by you and Isabelle (thus far) can be
edited/changed. The only way to change the BSN is to replace the
motherboard. In the case of a clone machine returning an empty BSN, I
substitute with a hash value of that empty string via SHA256. When this
is combined with make & model it serves well enough for my purposes.<g

I agree with what you have written in terms of identification of a specific
machine. However, the OP requested a method for obtaining the "Host ID".
The various definitions I have seen for Host ID have been satisfied by the
MAC address (or IP address) in Windows machines. I believe that is also the
case for Unix machines (see hostid command).

No argument! The MAC address can be edited/changed and so if this
occurs it will break the methodology the OP is trying to implement.


How do I call this: (remember to paste it all back together right)

[[[[[[dotnet.loadAssembly @"System.Management.dll"
mc = dotNetObject "System.Management.ManagementClass" "Win64_Processor"
moc = dotNetClass "System.Management.ManagementObjectCollection"
moc = mc.GetInstances()
enumerator = moc.GetEnumerator()
while enumerator.MoveNext() do
(
mo = enumerator.current
append CPUID ( mo.Properties.Item["ProcessorId"].value )
)]]]]]]

CellShocked explained :
How do I call this: (remember to paste it all back together right)

[[[[[[dotnet.loadAssembly @"System.Management.dll"
mc = dotNetObject "System.Management.ManagementClass" "Win64_Processor"
moc = dotNetClass "System.Management.ManagementObjectCollection"
moc = mc.GetInstances()
enumerator = moc.GetEnumerator()
while enumerator.MoveNext() do
(
mo = enumerator.current
append CPUID ( mo.Properties.Item["ProcessorId"].value )
)]]]]]]

This is dotnet code and so won't work with VBA. Use the code I posted
here earlier...

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

On Sat, 05 Jan 2013 20:35:58 -0500, GS wrote:

It happens that CellShocked formulated :
On Sat, 05 Jan 2013 20:03:28 -0500, Ron Rosenfeld wrote:

On Sat, 05 Jan 2013 18:34:51 -0500, GS wrote:

I recommend using WMI to obtain the BIOS serial number because all the
values recommended by you and Isabelle (thus far) can be
edited/changed. The only way to change the BSN is to replace the
motherboard. In the case of a clone machine returning an empty BSN, I
substitute with a hash value of that empty string via SHA256. When this
is combined with make & model it serves well enough for my purposes.<g

Oh, and my machine is built by myself; your routine returns
"To Be Filled By O.E.M." (Which is what is in all the Chassis
Information slots except for Type: Desktop)


Is there not a way to acquire the CPU ID (in Intel cases where it is
not turned off in the BIOS)?

For all intents and purposes, the BIOS serial number IS the cpu's ID.
The only way to change it is to swap out the motherboard, which creates
a new cpu with a new ID.<g


This claim is not true.

Intel CPUs have a unique identifier number which can be accessed though
their API. The motherboard serial number is an entirely different
animal, and BOTH numbers can be changed by way of changing either the CPU
itself, or the BIOS chip itself. some motherboards have a separate,
fixed chip which the real BIOS chip 'reads' to assign certain variables
in its operation. So, on those MOBOs, you will not change that ID
easily.

On Sat, 05 Jan 2013 21:27:14 -0500, GS wrote:

CellShocked explained :
How do I call this: (remember to paste it all back together right)

[[[[[[dotnet.loadAssembly @"System.Management.dll"
mc = dotNetObject "System.Management.ManagementClass" "Win64_Processor"
moc = dotNetClass "System.Management.ManagementObjectCollection"
moc = mc.GetInstances()
enumerator = moc.GetEnumerator()
while enumerator.MoveNext() do
(
mo = enumerator.current
append CPUID ( mo.Properties.Item["ProcessorId"].value )
)]]]]]]

This is dotnet code and so won't work with VBA. Use the code I posted
here earlier...


Your code? On a 64 bit system? And what about answering the question
where I asked just how to store that code in the excel VB editor (where)
and how to call it?

On Sat, 05 Jan 2013 19:47:04 -0800, CellShocked
<cellshocked@thecellvalueattheendofthespreadsheet. org wrote:



Intel CPUs have a unique identifier number which can be accessed though
their API. The motherboard serial number is an entirely different
animal, and BOTH numbers can be changed by way of changing either the CPU
itself, or the BIOS chip itself. some motherboards have a separate,
fixed chip which the real BIOS chip 'reads' to assign certain variables
in its operation. So, on those MOBOs, you will not change that ID
easily.

CORRECTION: (Ooops)

According to Intel, it has not been implemented since the i386.

http://www.intel.com/content/dam/www...ction-note.pdf

So, the BIOS ID thing is very likely the only unique identifier
mechanism for a machine.

Makes me wonder what my iPad reads when examining its underpinnings...

i don't agree, simply connect a modulo on the cpu of motherboard and
record anything else, but it is not vba, so ...

isabelle

Le 2013-01-05 22:47, CellShocked a écrit :

This claim is not true.

Intel CPUs have a unique identifier number which can be accessed though
their API. The motherboard serial number is an entirely different
animal, and BOTH numbers can be changed by way of changing either the CPU
itself, or the BIOS chip itself. some motherboards have a separate,
fixed chip which the real BIOS chip 'reads' to assign certain variables
in its operation. So, on those MOBOs, you will not change that ID
easily.

On Sat, 05 Jan 2013 20:33:38 -0500, GS wrote:

After serious thinking Ron Rosenfeld wrote :
On Sat, 05 Jan 2013 18:34:51 -0500, GS wrote:

I recommend using WMI to obtain the BIOS serial number because all the
values recommended by you and Isabelle (thus far) can be
edited/changed. The only way to change the BSN is to replace the
motherboard. In the case of a clone machine returning an empty BSN, I
substitute with a hash value of that empty string via SHA256. When this
is combined with make & model it serves well enough for my purposes.<g

Oh, and my machine is built by myself; your routine returns "To Be Filled By
O.E.M." (Which is what is in all the Chassis Information slots except for
Type: Desktop)

Interesting that this is the stored value. Obviously this is different
than what's returned in a commercial unit. For example, I find it
typical of clone machines released by Gateway to return an empty
string. Your case is a new one for me!<g

Doing a little more digging, using CPUID PC Wizard 2012, I note that my BIOS information does, indeed, contain an entry termed "Motherboard ID". However, as I wrote before, that is NOT what is returned by your code. It is obviously accessible, since PC Wizard accesses it, but I don't know how to approach this in VBA.

On Sat, 05 Jan 2013 20:33:38 -0500, GS wrote:

After serious thinking Ron Rosenfeld wrote :
On Sat, 05 Jan 2013 18:34:51 -0500, GS wrote:

I recommend using WMI to obtain the BIOS serial number because all the
values recommended by you and Isabelle (thus far) can be
edited/changed. The only way to change the BSN is to replace the
motherboard. In the case of a clone machine returning an empty BSN, I
substitute with a hash value of that empty string via SHA256. When this
is combined with make & model it serves well enough for my purposes.<g

Oh, and my machine is built by myself; your routine returns "To Be Filled By
O.E.M." (Which is what is in all the Chassis Information slots except for
Type: Desktop)

Interesting that this is the stored value. Obviously this is different
than what's returned in a commercial unit. For example, I find it
typical of clone machines released by Gateway to return an empty
string. Your case is a new one for me!<g

Some interesting further investigation, the significance of which I have no idea.
PCWizard returns the following in the "Mainboard" section:

----------------------------------------------
<<< Mainboard

Manufacturer : To Be Filled By O.E.M.

General Information
Product : To Be Filled By O.E.M.
Version : To Be Filled By O.E.M.
Serial Number : To Be Filled By O.E.M.
Unique ID : 00020003-00040005-00060007-00080009
SKU : To Be Filled By O.E.M.
Family : To Be Filled By O.E.M.
Start mode : Power Switch

OEM Information
OEM #1 : To Be Filled By O.E.M.

Chassis Information
Intrusion detected : Unspecified

Mainboard : ASRock Z77 Extreme6

General Information
Manufacturer : ASRock
Product : Z77 Extreme6
Version : Unspecified
Serial Number : Unspecified
Support MP : Yes, 4 CPU(s)
Version MPS : 1.4

Chassis Information
Manufacturer : To Be Filled By O.E.M.
Type : Desktop
Version : To Be Filled By O.E.M.
Serial Number : To Be Filled By O.E.M.
Asset : To Be Filled By O.E.M.
--------------------------------------------
So there does seem to be a UUID associated with this system.

In the original version of your Get_BIOSserialNum function, if I examine vBIOS in the Watch window and look at Qualifiers_ Item 4, I see, (in part):
: Name : "UUID"
: Value : "{8502C4E1-5FBB-11D2-AAC1-006008C78BC7}"
I don't really know what this represents.

If I modify your Get_BIOSserialNum function to look at Win32_ComputerSystemProduct, then the UUID returned is similar but not identical to that returned by PC Wizard:
vbios.UUID -- 03000200-0400-0500-0006-000700080009

Thoughts?

On Sun, 06 Jan 2013 09:42:51 -0500, Ron Rosenfeld wrote:

In the original version of your Get_BIOSserialNum function, if I examine vBIOS in the Watch window and look at Qualifiers_ Item 4, I see, (in part):
: Name : "UUID"
: Value : "{8502C4E1-5FBB-11D2-AAC1-006008C78BC7}"
I don't really know what this represents.

Hmmm. I doubt that UUID represents a machine specific value, because the identical UUID appears in an example he http://include.wutils.com/wmi/ROOT%5...in32_BIOS.html

On Sun, 06 Jan 2013 09:50:40 -0500, Ron Rosenfeld wrote:

On Sun, 06 Jan 2013 09:42:51 -0500, Ron Rosenfeld wrote:

In the original version of your Get_BIOSserialNum function, if I examine vBIOS in the Watch window and look at Qualifiers_ Item 4, I see, (in part):
: Name : "UUID"
: Value : "{8502C4E1-5FBB-11D2-AAC1-006008C78BC7}"
I don't really know what this represents.

Hmmm. I doubt that UUID represents a machine specific value, because
the identical UUID appears in an example he

http://include.wutils.com/wmi/ROOT%5...in32_BIOS.html


They have not implemented these things for a while. There must be some
way for a John Doe OEM Machne maker who buys Joe Bloe MOBO maker's cheap
run MOBO series in M quantities to go in and set these parameters.

I'd bet the main drawback is that each BIOS chip would have to be
individually burned with a unique code block, as opposed to mass burning
a bank of BIOS chips all at one time with the same code. But a modern
flash chip could do both. Burn the base code, and update the S/N later.
but that STILL requires individual chip attention and handling, as well
as the tracking aspect imposed on the maker.

CellShocked laid this down on his screen :
On Sat, 05 Jan 2013 21:27:14 -0500, GS wrote:

CellShocked explained :
How do I call this: (remember to paste it all back together right)

[[[[[[dotnet.loadAssembly @"System.Management.dll"
mc = dotNetObject "System.Management.ManagementClass" "Win64_Processor"
moc = dotNetClass "System.Management.ManagementObjectCollection"
moc = mc.GetInstances()
enumerator = moc.GetEnumerator()
while enumerator.MoveNext() do
(
mo = enumerator.current
append CPUID ( mo.Properties.Item["ProcessorId"].value )
)]]]]]]

This is dotnet code and so won't work with VBA. Use the code I posted
here earlier...


Your code? On a 64 bit system?

Yes!

And what about answering the question
where I asked just how to store that code in the excel VB editor (where)
and how to call it?

Store the code in a standard module, but remove the Private scope
keyword. Read my other replies for sample of how to use it.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

on 06/01/2013, Chairman Meow supposed :
On Sun, 06 Jan 2013 09:50:40 -0500, Ron Rosenfeld wrote:

On Sun, 06 Jan 2013 09:42:51 -0500, Ron Rosenfeld wrote:

In the original version of your Get_BIOSserialNum function, if I examine
vBIOS in the Watch window and look at Qualifiers_ Item 4, I see, (in part):
: Name : "UUID" : Value :
"{8502C4E1-5FBB-11D2-AAC1-006008C78BC7}" I don't really know what this
represents.

Hmmm. I doubt that UUID represents a machine specific value, because
the identical UUID appears in an example he

http://include.wutils.com/wmi/ROOT%5...in32_BIOS.html


They have not implemented these things for a while. There must be some
way for a John Doe OEM Machne maker who buys Joe Bloe MOBO maker's cheap
run MOBO series in M quantities to go in and set these parameters.

I'd bet the main drawback is that each BIOS chip would have to be
individually burned with a unique code block, as opposed to mass burning
a bank of BIOS chips all at one time with the same code. But a modern
flash chip could do both. Burn the base code, and update the S/N later.
but that STILL requires individual chip attention and handling, as well
as the tracking aspect imposed on the maker.

You hit the nail on the head! Good point. It also explains why some
clones don't have a BSN...

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

On Sun, 06 Jan 2013 08:13:02 -0800, Chairman Meow wrote:

They have not implemented these things for a while. There must be some
way for a John Doe OEM Machne maker who buys Joe Bloe MOBO maker's cheap
run MOBO series in M quantities to go in and set these parameters.

I'd bet the main drawback is that each BIOS chip would have to be
individually burned with a unique code block, as opposed to mass burning
a bank of BIOS chips all at one time with the same code. But a modern
flash chip could do both. Burn the base code, and update the S/N later.
but that STILL requires individual chip attention and handling, as well
as the tracking aspect imposed on the maker.

That explains a lot. Even the UUID can, according to some stuff I've read, change if the MB loses all power (including the battery backup).

I wonder how MS ties an installation to a particular motherboard? Do they use the machine GUID in the registry? Or something else?

Ron,
In your case *you* are the manufacturer and so it's your responsibility
to provide the OEM values.<g

There doesn't seem to be any -standard- as to the format of a BSN. For
example, my Dell Precision90 portable workstation (which is just a
Sherman tank version of a laptop) has this BSN: "570WHC1", which is
also its ServiceTag ID. The same holds true for my Dell Precision60
(older model of portable workstation laptop): "BPJQS51".

My Acer machines use a different format:
Acer Aspire One notebook: "LXPH10202693966A391601"
Acer TravelMate TimelineX: "LXV0603083103003EB2300"

So the format appears to be entirely the OEM's preference. I have other
BSNs from various makes/models which are different again than the
Dell/Acer examples.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

On Sun, 06 Jan 2013 12:28:29 -0500, Ron Rosenfeld wrote:

On Sun, 06 Jan 2013 08:13:02 -0800, Chairman Meow wrote:

They have not implemented these things for a while. There must be some
way for a John Doe OEM Machne maker who buys Joe Bloe MOBO maker's cheap
run MOBO series in M quantities to go in and set these parameters.

I'd bet the main drawback is that each BIOS chip would have to be
individually burned with a unique code block, as opposed to mass burning
a bank of BIOS chips all at one time with the same code. But a modern
flash chip could do both. Burn the base code, and update the S/N later.
but that STILL requires individual chip attention and handling, as well
as the tracking aspect imposed on the maker.

That explains a lot. Even the UUID can, according to some stuff I've read, change if the MB loses all power (including the battery backup).

I wonder how MS ties an installation to a particular motherboard? Do they use the machine GUID in the registry? Or something else?


They use the HD UUID and whatever other HW UUIDs they can find and even
S/Ns that get extracted and published via vendor drivers in operation.

I have had to call them in the past after a HW change and rectify my
re-activation.

So, some "found and stored" s/N or ID figure(s) in the registry get
tested, and if they change, the activation gets negated. That way, they
do not have to do any specific phone-home type snooping. The machine has
the engine built in, and then they service the customer with the raised
flag when they call... if they call. Much less labor for them that way.

Ron Rosenfeld expressed precisely :
On Sun, 06 Jan 2013 08:13:02 -0800, Chairman Meow
wrote:

They have not implemented these things for a while. There must be some
way for a John Doe OEM Machne maker who buys Joe Bloe MOBO maker's cheap
run MOBO series in M quantities to go in and set these parameters.

I'd bet the main drawback is that each BIOS chip would have to be
individually burned with a unique code block, as opposed to mass burning
a bank of BIOS chips all at one time with the same code. But a modern
flash chip could do both. Burn the base code, and update the S/N later.
but that STILL requires individual chip attention and handling, as well
as the tracking aspect imposed on the maker.

That explains a lot. Even the UUID can, according to some stuff I've read,
change if the MB loses all power (including the battery backup).

I wonder how MS ties an installation to a particular motherboard? Do they
use the machine GUID in the registry? Or something else?

A GUID is not the same as a BSN. Most GUIDs are listed under
HKCR\CLSID, which is where I used to store app license info back when I
was using the Registry. (Now my stuff is 100% reg-free) It's quite
likely where MS puts stuff!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

Chairman Meow explained on 06/01/2013 :
On Sun, 06 Jan 2013 12:28:29 -0500, Ron Rosenfeld wrote:

On Sun, 06 Jan 2013 08:13:02 -0800, Chairman Meow
wrote:

They have not implemented these things for a while. There must be some
way for a John Doe OEM Machne maker who buys Joe Bloe MOBO maker's cheap
run MOBO series in M quantities to go in and set these parameters.

I'd bet the main drawback is that each BIOS chip would have to be
individually burned with a unique code block, as opposed to mass burning
a bank of BIOS chips all at one time with the same code. But a modern
flash chip could do both. Burn the base code, and update the S/N later.
but that STILL requires individual chip attention and handling, as well
as the tracking aspect imposed on the maker.

That explains a lot. Even the UUID can, according to some stuff I've read,
change if the MB loses all power (including the battery backup).

I wonder how MS ties an installation to a particular motherboard? Do they
use the machine GUID in the registry? Or something else?


They use the HD UUID and whatever other HW UUIDs they can find and even
S/Ns that get extracted and published via vendor drivers in operation.

I have had to call them in the past after a HW change and rectify my
re-activation.

This is precisely why I use BSNs for locking my software to a machine.
Albeit that it only takes up 1 element in my 4 element MachineID, in
cases where there is no BSN I generate a SHA256 hash value in its
place.

What I'm saying here is that I don't rely on a BSN solely as a
MachineID because of the associated ambiguities. There's enough other
(unambiguous) system info that I use that I can afford to generate my
own BSN where/when necessary.

A license profile has 17 elements. MachineID is only 1 of those. Each
profile element can have as many item elements as I want! That should
give you some indication of the weighted value a BSN has overall!

So, some "found and stored" s/N or ID figure(s) in the registry get
tested, and if they change, the activation gets negated. That way, they
do not have to do any specific phone-home type snooping. The machine has
the engine built in, and then they service the customer with the raised
flag when they call... if they call. Much less labor for them that way.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

On Sun, 06 Jan 2013 12:43:28 -0500, GS wrote:

Ron,
In your case *you* are the manufacturer and so it's your responsibility
to provide the OEM values.<g

There doesn't seem to be any -standard- as to the format of a BSN. For
example, my Dell Precision90 portable workstation (which is just a
Sherman tank version of a laptop) has this BSN: "570WHC1", which is
also its ServiceTag ID. The same holds true for my Dell Precision60
(older model of portable workstation laptop): "BPJQS51".

My Acer machines use a different format:
Acer Aspire One notebook: "LXPH10202693966A391601"
Acer TravelMate TimelineX: "LXV0603083103003EB2300"

So the format appears to be entirely the OEM's preference. I have other
BSNs from various makes/models which are different again than the
Dell/Acer examples.


The figures are likely in the same places (require the same API calls
to retrieve), but are likely BIOS maker specific as to elements like
'field formatting' and the actual data string nomenclature.

Had CPU IDs from Intel not been so flatly rejected back in the 386
days, we would probably have more of a standard for the whole thing going
by now, certainly.

Oh, and remember how the "hard sectored floppy" idea almost killed
Broderbund at one point? I do.

Chairman Meow wrote on 06/01/2013 :
The figures are likely in the same places (require the same API calls
to retrieve), but are likely BIOS maker specific as to elements like
'field formatting' and the actual data string nomenclature.

Had CPU IDs from Intel not been so flatly rejected back in the 386
days, we would probably have more of a standard for the whole thing going
by now, certainly.

Oh, and remember how the "hard sectored floppy" idea almost killed
Broderbund at one point? I do.

Though I've been using Excel since v4, I only started programming in
2003 via MS Office 2000 Developer Edition on a Win NT 2000 OS. That
means I wouldn't have a slightest clue as to what "hard sector floppy"
is!<g

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

On Sun, 06 Jan 2013 12:43:28 -0500, GS wrote:

In your case *you* are the manufacturer and so it's your responsibility
to provide the OEM values.<g

And I might even do so, if there were some way to program the chip on the MB in my environment :-|

On Sun, 06 Jan 2013 13:50:28 -0500, Ron Rosenfeld wrote:

On Sun, 06 Jan 2013 12:43:28 -0500, GS wrote:

In your case *you* are the manufacturer and so it's your responsibility
to provide the OEM values.<g

And I might even do so, if there were some way to program the chip on the MB in my environment :-|


You have to make your own custom J-TAG probe. ;-)

On Sun, 06 Jan 2013 11:39:32 -0800, Chairman Meow wrote:

On Sun, 06 Jan 2013 13:50:28 -0500, Ron Rosenfeld wrote:

On Sun, 06 Jan 2013 12:43:28 -0500, GS wrote:

In your case *you* are the manufacturer and so it's your responsibility
to provide the OEM values.<g

And I might even do so, if there were some way to program the chip on the MB in my environment :-|


You have to make your own custom J-TAG probe. ;-)

Oh, is that all? :-)

on 06/01/2013, Ron Rosenfeld supposed :
On Sun, 06 Jan 2013 12:43:28 -0500, GS wrote:

In your case *you* are the manufacturer and so it's your responsibility
to provide the OEM values.<g

And I might even do so, if there were some way to program the chip on the MB
in my environment :-|

Perha[s you can check if the folks at SysInternals have a utility for
that!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

On Sun, 06 Jan 2013 16:45:22 -0500, Ron Rosenfeld wrote:

On Sun, 06 Jan 2013 11:39:32 -0800, Chairman Meow wrote:

On Sun, 06 Jan 2013 13:50:28 -0500, Ron Rosenfeld wrote:

On Sun, 06 Jan 2013 12:43:28 -0500, GS wrote:

In your case *you* are the manufacturer and so it's your responsibility
to provide the OEM values.<g

And I might even do so, if there were some way to program the chip on the MB in my environment :-|


You have to make your own custom J-TAG probe. ;-)

Oh, is that all? :-)


No. Then, you must research the chip maker's data sheet to see how you
have to "hit it" with the programming routine.

On Sun, 06 Jan 2013 13:50:28 -0500, Ron Rosenfeld wrote:

On Sun, 06 Jan 2013 12:43:28 -0500, GS wrote:

In your case *you* are the manufacturer and so it's your responsibility
to provide the OEM values.<g

And I might even do so, if there were some way to program the chip on the MB in my environment :-|


I found this amazing 'gadget'. It has a lot of this info when explored
(info page scrolled).

http://addgadgets.com/all_cpu_meter/