Results 1 to 9 of 9
  1. #1
    2 Star Lounger
    Join Date
    May 2013
    Posts
    126
    Thanks
    0
    Thanked 0 Times in 0 Posts

    ramdiskoptions and alphanumeric object in the DVD BCD

    Hi

    Can you explain one thing:

    I copied the contents of the DVD of Windows 10 on my hard disk and then I wrote the following commands:

    Code:
    C:\WINDOWS\system32>bcdedit /store "C:\Users\Balubeto\Downloads\DVD\boot\bcd"
    
    Windows Boot Manager
    --------------------
    identifier              {bootmgr}
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {globalsettings}
    default                 {default}
    displayorder            {default}
    toolsdisplayorder       {memdiag}
    timeout                 30
    
    Windows Boot Loader
    -------------------
    identifier              {default}
    device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    path                    \windows\system32\boot\winload.exe
    description             Windows Setup
    locale                  en-US
    inherit                 {bootloadersettings}
    osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    systemroot              \windows
    bootmenupolicy          Standard
    detecthal               Yes
    winpe                   Yes
    ems                     No
    
    C:\WINDOWS\system32>bcdedit /store "C:\Users\Balubeto\Downloads\DVD\boot\bcd" /set {default} osdevice ramdisk=[boot]\sources\boot.wim,{ramdiskoptions}
    Operazione completata.
    
    C:\WINDOWS\system32>bcdedit /store "C:\Users\Balubeto\Downloads\DVD\boot\bcd" /set {default} device ramdisk=[boot]\sources\boot.wim,{ramdiskoptions}
    Operazione completata.
    
    C:\WINDOWS\system32>bcdedit /store "C:\Users\Balubeto\Downloads\DVD\boot\bcd"
    
    Windows Boot Manager
    --------------------
    identifier              {bootmgr}
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {globalsettings}
    default                 {default}
    displayorder            {default}
    toolsdisplayorder       {memdiag}
    timeout                 30
    
    Windows Boot Loader
    -------------------
    identifier              {default}
    device                  ramdisk=[boot]\sources\boot.wim,{ramdiskoptions}
    path                    \windows\system32\boot\winload.exe
    description             Windows Setup
    locale                  en-US
    inherit                 {bootloadersettings}
    osdevice                ramdisk=[boot]\sources\boot.wim,{ramdiskoptions}
    systemroot              \windows
    bootmenupolicy          Standard
    detecthal               Yes
    winpe                   Yes
    ems                     No
    
    C:\WINDOWS\system32>
    Why, in the final output, the ramdiskoptions alias is not converted into its alphanumeric code as it is done in the initial output?

    Thanks

    Bye
    Last edited by balubeto; 2015-09-08 at 13:43.

  2. #2
    Super Moderator bbearren's Avatar
    Join Date
    Dec 2009
    Location
    Polk County, Florida
    Posts
    3,761
    Thanks
    26
    Thanked 424 Times in 338 Posts
    Those alpha-numeric groups are the hexadecimal GUID's (Globally Unique ID) for those objects. The alias is the name preceding the GUID; in this case "ramdisk=[boot]\sources\boot.wim".

    Yes, I'm sure.

    Bye
    Create a fresh drive image before making system changes, in case you need to start over!

    "The problem is not the problem. The problem is your attitude about the problem. Savvy?"—Captain Jack Sparrow "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware.
    Unleash Windows

  3. #3
    2 Star Lounger
    Join Date
    May 2013
    Posts
    126
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by bbearren View Post
    Those alpha-numeric groups are the hexadecimal GUID's (Globally Unique ID) for those objects. The alias is the name preceding the GUID; in this case "ramdisk=[boot]\sources\boot.wim".

    Yes, I'm sure.

    Bye
    Could you reread the first post and respond?

    Thanks

    Bye

  4. #4
    Super Moderator bbearren's Avatar
    Join Date
    Dec 2009
    Location
    Polk County, Florida
    Posts
    3,761
    Thanks
    26
    Thanked 424 Times in 338 Posts
    Quote Originally Posted by balubeto View Post
    Could you reread the first post and respond?

    Thanks

    Bye
    You seem to be trying to use Vista/7 era tweaks in Windows 10; I'm not so sure that they are relevant. The identifier "ramdiskoptions" may not be recognized in Windows 10; I don't really know.
    Create a fresh drive image before making system changes, in case you need to start over!

    "The problem is not the problem. The problem is your attitude about the problem. Savvy?"—Captain Jack Sparrow "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware.
    Unleash Windows

  5. #5
    2 Star Lounger
    Join Date
    May 2013
    Posts
    126
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by bbearren View Post
    You seem to be trying to use Vista/7 era tweaks in Windows 10; I'm not so sure that they are relevant. The identifier "ramdiskoptions" may not be recognized in Windows 10; I don't really know.
    Code:
    C:\WINDOWS\system32>bcdedit /store "C:\Users\Balubeto\Downloads\DVD\boot\bcd" /v /enum all
    
    Windows Boot Manager
    --------------------
    identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    default                 {7619dcc9-fafe-11d9-b411-000476eba25f}
    displayorder            {7619dcc9-fafe-11d9-b411-000476eba25f}
    toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
    timeout                 30
    
    Windows Boot Loader
    -------------------
    identifier              {7619dcc9-fafe-11d9-b411-000476eba25f}
    device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    path                    \windows\system32\boot\winload.exe
    description             Windows Setup
    locale                  en-US
    inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    systemroot              \windows
    bootmenupolicy          Standard
    detecthal               Yes
    winpe                   Yes
    ems                     No
    
    Windows Memory Tester
    ---------------------
    identifier              {b2721d73-1db4-4c62-bf78-c548a880142d}
    device                  boot
    path                    \boot\memtest.exe
    description             Windows Memory Diagnostic
    locale                  en-US
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    
    Settings Emergency Management Services
    ------------
    identifier              {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
    bootems                 No
    
    debugger settings
    -----------------
    identifier              {4636856e-540f-4170-a130-a84776f4c654}
    debugtype               Serial
    debugport               1
    baudrate                115200
    
    Global settings
    ---------------
    identifier              {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
    inherit                 {4636856e-540f-4170-a130-a84776f4c654}
                            {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
    
    Boot Loader Settings
    -------------------
    identifier              {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
    inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
                            {7ff607e0-4395-11db-b0de-0800200c9a66}
    
    Hypervisor Settings
    -------------------
    identifier              {7ff607e0-4395-11db-b0de-0800200c9a66}
    description             Hypervisor Settings
    hypervisordebugtype     Serial
    hypervisordebugport     1
    hypervisorbaudrate      115200
    
    Device options
    --------------
    identifier              {7619dcc8-fafe-11d9-b411-000476eba25f}
    ramdisksdidevice        boot
    ramdisksdipath          \boot\boot.sdi
    
    C:\WINDOWS\system32>bcdedit /store "C:\Users\Balubeto\Downloads\DVD\boot\bcd" /enum all
    
    Windows Boot Manager
    --------------------
    identifier              {bootmgr}
    description             Windows Boot Manager
    locale                  en-US
    inherit                 {globalsettings}
    default                 {default}
    displayorder            {default}
    toolsdisplayorder       {memdiag}
    timeout                 30
    
    Windows Boot Loader
    -------------------
    identifier              {default}
    device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    path                    \windows\system32\boot\winload.exe
    description             Windows Setup
    locale                  en-US
    inherit                 {bootloadersettings}
    osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
    systemroot              \windows
    bootmenupolicy          Standard
    detecthal               Yes
    winpe                   Yes
    ems                     No
    
    Windows Memory Tester
    ---------------------
    identifier              {memdiag}
    device                  boot
    path                    \boot\memtest.exe
    description             Windows Memory Diagnostic
    locale                  en-US
    inherit                 {globalsettings}
    
    Settings Emergency Management Services
    ------------
    identifier              {emssettings}
    bootems                 No
    
    debugger settings
    -----------------
    identifier              {dbgsettings}
    debugtype               Serial
    debugport               1
    baudrate                115200
    
    Global settings
    ---------------
    identifier              {globalsettings}
    inherit                 {dbgsettings}
                            {emssettings}
    
    Boot Loader Settings
    -------------------
    identifier              {bootloadersettings}
    inherit                 {globalsettings}
                            {hypervisorsettings}
    
    Hypervisor Settings
    -------------------
    identifier              {hypervisorsettings}
    description             Hypervisor Settings
    hypervisordebugtype     Serial
    hypervisordebugport     1
    hypervisorbaudrate      115200
    
    Device options
    --------------
    identifier              {7619dcc8-fafe-11d9-b411-000476eba25f}
    ramdisksdidevice        boot
    ramdisksdipath          \boot\boot.sdi
    
    C:\WINDOWS\system32>
    By chance, this is an internal alias for the "Device options" object?

    Its alphanumeric string is fixed or changes each boot or any device used? If it changes, what should I put in the osdevice and device elements to avoid boot problems?

    Thanks

    Bye

  6. #6
    Super Moderator bbearren's Avatar
    Join Date
    Dec 2009
    Location
    Polk County, Florida
    Posts
    3,761
    Thanks
    26
    Thanked 424 Times in 338 Posts
    Quote Originally Posted by balubeto View Post
    By chance, this is an internal alias for the "Device options" object?

    Its alphanumeric string is fixed or changes each boot or any device used? If it changes, what should I put in the osdevice and device elements to avoid boot problems?

    Thanks

    Bye
    You need to get your terms straight. The "alias" is the stuff you can read in English (or whatever language is chosen during installation). The "alphanumeric string" is the "Globally Unique ID" or GUID that Windows uses internally to identify objects. It is assigned and fixed; it does not change each boot.

    I can't help you with whatever it is you're trying to do with BCDEDIT, because I don't know what you're trying to do or why you're trying to do it, and I don't intend to guess.
    Create a fresh drive image before making system changes, in case you need to start over!

    "The problem is not the problem. The problem is your attitude about the problem. Savvy?"—Captain Jack Sparrow "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware.
    Unleash Windows

  7. #7
    2 Star Lounger
    Join Date
    May 2013
    Posts
    126
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by bbearren View Post
    You need to get your terms straight. The "alias" is the stuff you can read in English (or whatever language is chosen during installation). The "alphanumeric string" is the "Globally Unique ID" or GUID that Windows uses internally to identify objects. It is assigned and fixed; it does not change each boot.

    I can't help you with whatever it is you're trying to do with BCDEDIT, because I don't know what you're trying to do or why you're trying to do it, and I don't intend to guess.
    Then, the {7619dcc8-fafe-11d9-b411-000476eba25f} string always identifies the "Device options" object . Right?

    This also applies to Windows 7/8.x or this string is different?

    Thanks

    Bye

  8. #8
    Super Moderator bbearren's Avatar
    Join Date
    Dec 2009
    Location
    Polk County, Florida
    Posts
    3,761
    Thanks
    26
    Thanked 424 Times in 338 Posts
    Quote Originally Posted by balubeto View Post
    Then, the {7619dcc8-fafe-11d9-b411-000476eba25f} string always identifies the "Device options" object . Right?

    This also applies to Windows 7/8.x or this string is different?

    Thanks

    Bye
    Read the link in post #2.
    Create a fresh drive image before making system changes, in case you need to start over!

    "The problem is not the problem. The problem is your attitude about the problem. Savvy?"—Captain Jack Sparrow "When you're troubleshooting, start with the simple and proceed to the complex."—M.O. Johns "Experience is what you get when you're looking for something else."—Sir Thomas Robert Deware.
    Unleash Windows

  9. #9
    2 Star Lounger
    Join Date
    May 2013
    Posts
    126
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by bbearren View Post
    Read the link in post #2.
    From what I understand, the answer to both questions is "yes". Right?

    Thanks

    Bye

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •