"Mayayana" wrote in message news

"Bob_S" wrote

| I am not going to read this whole thread again to see what has been said
and
| not said

How are you going to be helpful if you don't read
the thread? It was established a couple of days ago
that he wants the hard disk serial number... assuming
that he *really* needs that at all.... and that volume
serial number won't be helpful.

| Can't believe all the paths this thread has taken from Linux to VB
scripts
| just to identify a hard drive
|

It did get complicated. There are several cooks
in the kitchen and Peter is in over his head with script.
He also seems to be on the other side of the world,
which means the discussion is going slo-mo because
there's not much time overlap.

You may not find script interesting, but for people
who do it's an interesting, informative discussion.
I might just as well say, "I can't believe someone
thinks they need to install an 8 MB program just
to find information about the hardware."

Speccy does look good. It's very thorough. But
for most situations a 10 KB script can do the job,
while Speccy is mostly just getting the same info,
using the same methods, with a great deal of
overhead.

Also, Peter should have a copy of Samsung Magician
that comes with their SSDs. That also shows
serial numbers. So there are various options, but
Peter is having difficulty figuring out what he needs.



Okay - if the 10K script worked that would have been less confusing but it
took awhile and caused confusion - right.

If you look closely, I was the first to respond to the OP's post which was
initially blank and just the subject line asking if SSD's serial number were
in the BIOS.

Your interest in scripting is good but I looked at this as a simple problem
with a quick answer to solve his stated issue. So what if it's an 8MB
program, it can be uninstalled. And just for clarification, Speccy shows
both the Volume Serial Number as well as manufactures serial number - the
scripts didn't.

I look to solve problems onsite the quickest way I can with the least amount
of time expended so clients don't end up paying for 'research time' - they
tend not to like paying for someone to learn on their dime. I tend to do
the same thing here and if the OP can't understand the direct methods and
says so, then I change tactics and will go into teach mode if I can actually
be of any benefit. Do you really think offering him scripts and Linux
advice solved "his" problem?

So as not to raise anyone's ire for making a simpler suggestion - I'll stay
away from this post and let you guy's solve the issue.

But... I will add one more tidbit. SSD controllers (the onboard SSD
controller) - even Samsung's EVO's (I have a dozen of them) have problems
with compatibility issues and should have their firmware updated before
being put to use. I just did a go-around this week with a PNY SSD on an
industrial grade motherboard. That same SSD worked perfect on two other
computers here in my office but would fail booting 50% of the time on the
other system. Put in an Intel and then a Samsung SSD to test and they
booted great every time.

I bring that up because you said he had the Samsung Magician which should
show him if he's on the latest revision or not and I don't recall reading
anyone mentioning that he needed to check for an update.
--

Bob S.