If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#61
|
|||
|
|||
SSDs serial No in BIOS.
"GS" wrote
Wow. $400?! I know Adobe prices are outrageous, but that's crazy. MS Help Workshop is free. I'm guessing the difference is that RoboHelp gives you some kind of WYSIWYG HTML editor so that you don't actually have to write the HTML pages. What's $400? When I bought RH it was $900+! (I was publishing ebooks for my daughter; -she wanted them to be multi-platform from single source.) Ah. It gets crazier by the minute. It may be $1,100 now. I couldn't quite figure it out from their webpage. They had 2 sets of prices and it wasn't clear what each was for. Maybe $400 is the update. To add insult to injury, the price is US$; -I'm in Canada! -- Garry Free usenet access at http://www.eternal-september.org Classic VB Users Regroup! comp.lang.basic.visual.misc microsoft.public.vb.general.discussion |
Ads |
#62
|
|||
|
|||
SSDs serial No in BIOS.
On Mon, 19 Mar 2018 18:41:46 -0400, Paul
wrote: Peter Jason wrote: On Mon, 19 Mar 2018 15:03:52 -0400, GS wrote: I can't get it started. How do I get it into the CMD screen? Can it be started with a RH mouse click? Either double-click the vbs file OR right-click and choose Open. I've posted updated scripts since this thread. Here's the final versions: 'GetDriveSerialNumberFromPath.vbs Dim oWMI, Path, vData, vInfo, sInfo, i, iNdx, bSelectedPath Set oWMI = GetObject("WinMgmts:") Path = UCase(InputBox("Enter the Drive Letter")) Set vData = oWMI.ExecQuery("Select * from Win32_LogicalDisk _ Where DriveType = 3") i = 0: Path = Left(Path, 1) & ":" For Each vInfo In vData 'Assign an index only if the USB DeviceID matches Path. If vInfo.DeviceID = Path Then iNdx = i: bSelectedPath = True: Exit For i = i + 1 Next If bSelectedPath Then 'Iterate the WMI.Win32_DiskDrive class to verify Path is a valid USB device, 'and determine an index for identifying our target USB device. Set vData = oWMI.ExecQuery("Select * from Win32_DiskDrive") i = 0 For Each vInfo In vData If UCase(vInfo.InterfaceType) = "IDE" Then If i = iNdx Then sInfo = Path & " SerialNumber: " _ & vInfo.SerialNumber: Exit For i = i + 1 End If Next End If MsgBox sInfo, vbInformation 'GetLogicalDiskInfo.vbs Dim sInfo Set objWMIService = GetObject("winmgmts:") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_LogicalDisk",,48) For Each objItem in colItems sInfo = sInfo & "Caption: " & objItem.Caption & vblf _ & "Description: " & objItem.Description & vblf _ & "VolumeSerialNumber: " & objItem.VolumeSerialNumber & vblf & vblf Next MsgBox sInfo, vbInformation 'GetDriveInfo.vbs Set objWMIService = GetObject("winmgmts:") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_DiskDrive",,48) For Each objItem in colItems sInfo = sInfo & "Caption: " & objItem.Caption & vblf _ & "Description: " & objItem.Description & vblf _ & "SerialNumber: " & objItem.SerialNumber & vblf _ & "Size: " & objItem.Size & vblf _ & "---------------------------------------" & vblf Next MsgBox sInfo, vbInformation Thanks, on my machine it gave an error message... https://postimg.org/image/lt45rd6g5/ Change the fifth line so it isn't extended with the underscore ? Set vData = oWMI.ExecQuery("Select * from Win32_LogicalDisk Where DriveType = 3") That got me a result on Win10. Paul Thanks, but I get another error message... https://postimg.org/image/q4y9x0syd/ |
#63
|
|||
|
|||
SSDs serial No in BIOS.
Please post the entire code of the script that raises the error.
-- Garry Free usenet access at http://www.eternal-september.org Classic VB Users Regroup! comp.lang.basic.visual.misc microsoft.public.vb.general.discussion |
#64
|
|||
|
|||
SSDs serial No in BIOS.
On Wed, 21 Mar 2018 10:09:09 +1100, Peter Jason wrote:
On Mon, 19 Mar 2018 18:41:46 -0400, Paul wrote: Peter Jason wrote: On Mon, 19 Mar 2018 15:03:52 -0400, GS wrote: I can't get it started. How do I get it into the CMD screen? Can it be started with a RH mouse click? Either double-click the vbs file OR right-click and choose Open. I've posted updated scripts since this thread. Here's the final versions: 'GetDriveSerialNumberFromPath.vbs Dim oWMI, Path, vData, vInfo, sInfo, i, iNdx, bSelectedPath Set oWMI = GetObject("WinMgmts:") Path = UCase(InputBox("Enter the Drive Letter")) Set vData = oWMI.ExecQuery("Select * from Win32_LogicalDisk _ Where DriveType = 3") i = 0: Path = Left(Path, 1) & ":" For Each vInfo In vData 'Assign an index only if the USB DeviceID matches Path. If vInfo.DeviceID = Path Then iNdx = i: bSelectedPath = True: Exit For i = i + 1 Next If bSelectedPath Then 'Iterate the WMI.Win32_DiskDrive class to verify Path is a valid USB device, 'and determine an index for identifying our target USB device. Set vData = oWMI.ExecQuery("Select * from Win32_DiskDrive") i = 0 For Each vInfo In vData If UCase(vInfo.InterfaceType) = "IDE" Then If i = iNdx Then sInfo = Path & " SerialNumber: " _ & vInfo.SerialNumber: Exit For i = i + 1 End If Next End If MsgBox sInfo, vbInformation 'GetLogicalDiskInfo.vbs Dim sInfo Set objWMIService = GetObject("winmgmts:") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_LogicalDisk",,48) For Each objItem in colItems sInfo = sInfo & "Caption: " & objItem.Caption & vblf _ & "Description: " & objItem.Description & vblf _ & "VolumeSerialNumber: " & objItem.VolumeSerialNumber & vblf & vblf Next MsgBox sInfo, vbInformation 'GetDriveInfo.vbs Set objWMIService = GetObject("winmgmts:") Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_DiskDrive",,48) For Each objItem in colItems sInfo = sInfo & "Caption: " & objItem.Caption & vblf _ & "Description: " & objItem.Description & vblf _ & "SerialNumber: " & objItem.SerialNumber & vblf _ & "Size: " & objItem.Size & vblf _ & "---------------------------------------" & vblf Next MsgBox sInfo, vbInformation Thanks, on my machine it gave an error message... https://postimg.org/image/lt45rd6g5/ Change the fifth line so it isn't extended with the underscore ? Set vData = oWMI.ExecQuery("Select * from Win32_LogicalDisk Where DriveType = 3") That got me a result on Win10. Paul Thanks, but I get another error message... https://postimg.org/image/q4y9x0syd/ That error is because you saved the entire text as a single vbs file. It's actually multiple files. Save each as a separate .vbs, then they should run from a double click. GetDriveSerialNumberFromPath.vbs GetLogicalDiskInfo.vbs GetDriveInfo.vbs |
#65
|
|||
|
|||
SSDs serial No in BIOS.
On 18/03/2018 04:49, Peter Jason wrote:
On Sun, 18 Mar 2018 15:44:01 +1100, Peter Jason wrote: I've just cloned my System SSD to a new one because of the endless "run CHKDSK" flags in the RHS notification panel. I bought the same brand & size as the old one, a "Samsunh 850 EVO". In the BIOS there seems to be no way to tell these apart, no serial numbers or other properties. How is one to tell them apart? I had to go to disk management and see which had the "offline" disabled, then shutting down and unplugging the old SSD & starting all up again. All seems well now; but we'll see. Why did you buty the same type after one of them failed? As I understand it the evolution in design that happened with the Samsung EVO series was a way of making them cheaper, NOT more reliable. -- Brian Gregory (in England). |
#66
|
|||
|
|||
SSDs serial No in BIOS.
"Peter Jason" wrote in message
... -- I am not going to read this whole thread again to see what has been said and not said but if the question is that the OP wants manufacturers serial numbers so he can distinguish between drives in his system, the scripts provided are not doing that. As shown, they are the Volume Serial Numbers which are generated when the drive is initialized and formatted and can be confusing if he's swapping drives around or reinitializing them during all this. As I suggested a few days ago, free programs are available that will tell you that answer, like Speccy from Piriform. Free, quick, done. But if he really wants the Volume Serial number - here's a simpler way: Open a command prompt and type vol C: and hit enter and it will show the volume name if it has one and the volume serial number. Repeat the command vol X: for each drive letter with X being the next drive letter you want to find. Can't believe all the paths this thread has taken from Linux to VB scripts just to identify a hard drive Bob S. |
#67
|
|||
|
|||
SSDs serial No in BIOS.
"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. |
#68
|
|||
|
|||
SSDs serial No in BIOS.
On Tue, 20 Mar 2018 22:39:53 -0400, "Mayayana"
wrote: "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. Yes I do. The new SSD (according to the RHS notification panel) is still showing up the need to run CHKDSK every day, even though Magician gives no indication of a problem, nor does "HD pro" nor does "CHKDSK" nor scannow. Clearly it's Windows10 and now I have a spare Samsung SSD. On cold startup the system does a scan/repair of "drive H" shown here on the System (new) SSD...... https://postimg.org/image/mkbl56npx/ This all happens every other day or so. |
#69
|
|||
|
|||
SSDs serial No in BIOS.
"Peter Jason" wrote in message
... On Tue, 20 Mar 2018 22:39:53 -0400, "Mayayana" wrote: "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. Yes I do. The new SSD (according to the RHS notification panel) is still showing up the need to run CHKDSK every day, even though Magician gives no indication of a problem, nor does "HD pro" nor does "CHKDSK" nor scannow. Clearly it's Windows10 and now I have a spare Samsung SSD. On cold startup the system does a scan/repair of "drive H" shown here on the System (new) SSD...... https://postimg.org/image/mkbl56npx/ This all happens every other day or so. Google "Dirty Bit" and you'll find this as one example: https://www.raymond.cc/blog/manually...ithout-chkdsk/ -- Bob S. |
#70
|
|||
|
|||
SSDs serial No in BIOS.
"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. |
#71
|
|||
|
|||
SSDs serial No in 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. You need to reread the post! The scripts show both the volume serial and the hardware serial; -the 3rd script shows the hardware serial given the drive's path! -- Garry Free usenet access at http://www.eternal-september.org Classic VB Users Regroup! comp.lang.basic.visual.misc microsoft.public.vb.general.discussion |
#72
|
|||
|
|||
SSDs serial No in BIOS.
"Peter Jason" wrote
| Magician gives no indication of a problem, nor does "HD pro" nor does | "CHKDSK" nor scannow. But Magician shows the disk serial number in the opening window, so at least that issue is solved. | Clearly it's Windows10 and now I have a spare Samsung SSD. On cold | startup the system does a scan/repair of "drive H" shown here on the | System (new) SSD...... | This is a good example of how it helps if you start out providing as much info as possible. |
#73
|
|||
|
|||
SSDs serial No in BIOS.
Bob_S wrote:
"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. I did offer a one-liner. But nobody cared. (Got this off the web.) wmic diskdrive get model,name,serialnumber Works in Win10, not in WinXP. (WinXP doesn't seem to have a serial number field.) The diskdrive is an alias for the actual Win32_diskdrive item. ******* For people who have somehow switched namespaces, you can try C:\WINDOWS\system32wmic /namespace:cimv2 diskdrive get model,name,serialnumber ******* Microsoft Windows [Version 10.0.17093.1000] === My Insider drive, (c) 2017 Microsoft Corporation. All rights reserved. couple days ago C:\WINDOWS\system32wmic diskdrive get model,name,serialnumber Model Name SerialNumber \\.\PHYSICALDRIVE1 WDC WD5003AZEX-00Kxxxx \\.\PHYSICALDRIVE0 WD-WCC6Y0VExxxx The value shown, happens to match the S/N of the drive. https://s10.postimg.org/y75ch1wex/Serial_Number.gif If you want to see everything the OS has got, try: wmic diskdrive get F:\out.txt notepad F:\out.txt HTH, Paul |
#74
|
|||
|
|||
SSDs serial No in BIOS.
Your script shows serial numbers that are showing ~45 digits for both a
Kinston and a Samsung SSD drive. I have a GPT drive with 4 partitions which is a 4TB drive and your script also shows 42 digits and both the SSD's and the 4TB drive should have 15 digits. Also, nothing in the serial numbers match in any combination like at least the next one does.. On a WDC 1.0TB drive your script shows W -DCWTAR7R412227 and Speccy shows the serial number as WD-WCATR7142272. Do you see how your script appears to be reversing the bytes on that? So while you think it's providing correct serial numbers - its not. Easy enough to verify. Either pull the drive, check the box it came in if you have it or use another program. "GS" wrote in message news 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. You need to reread the post! The scripts show both the volume serial and the hardware serial; -the 3rd script shows the hardware serial given the drive's path! Gary, Your script shows serial numbers that are showing ~45 digits for both a Kinston and a Samsung SSD drive. I have a GPT drive with 4 partitions which is a 4TB drive and your script also shows 42 digits and both the SSD's and the 4TB drive should have 15 digits if the WDC is included otherwise 12 digit serial number. Also, nothing in the serial numbers match in any combination like at least the next one does.. On a WDC 1.0TB drive your script shows W -DCWTAR7R412227 and Speccy shows the serial number as WD-WCATR7142272. Do you see how your script appears to be reversing the bytes on that? So while you think it's providing correct serial numbers - its not. Easy enough to verify. Either pull the drive, check the box it came in if you have it or use another program. So re-reading the post doesn't fix a broken script now does it. Great that you took the time to pound out a script for this but it should have been verified that it actually does work. Your welcome, -- Bob S. |
#75
|
|||
|
|||
Corrected Version: SSDs serial No in BIOS.
snip....
Gary, Your script shows serial numbers that are showing ~45 digits for both a Kinston and a Samsung SSD drive. I have a GPT drive with 4 partitions which is a 4TB drive and your script also shows 42 digits and both the SSD's and the 4TB drive should have 15 digits if the WDC is included otherwise 12 digit serial number. Also, nothing in the serial numbers match in any combination like at least the next one does.. On a WDC 1.0TB drive your script shows W -DCWTAR7R412227 and Speccy shows the serial number as WD-WCATR7142272. Do you see how your script appears to be reversing the bytes on that? So while you think it's providing correct serial numbers - its not. Easy enough to verify. Either pull the drive, check the box it came in if you have it or use another program. So re-reading the post doesn't fix a broken script now does it. Great that you took the time to pound out a script for this but it should have been verified that it actually does work. Your welcome, -- Bob S. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|