Nealius Posted February 8, 2018 Posted February 8, 2018 Trying to reinstall 2.5 here, but downloading a 47gb file at 1mb/s is absurd, so I'm trying to convert my 1.5.8 release to open beta in order for the installer to copy over some files. According to this thread I should be able to run a Powershell command to switch from release to open beta: DCS_Updater.exe update @openbeta This does not work. It simply tells me that my release version is current (1.5.8.12823).
Rudel_chw Posted February 8, 2018 Posted February 8, 2018 Not a powershell command ... dcs_updater is an executable utility, you have to open a command prompt with admin privileges, then navigate to program files/eagle dynamics/your-dcs-folder/bin and on that place resides the utility and you can run the command. For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Nealius Posted February 8, 2018 Author Posted February 8, 2018 That doesn't work on Windows 10. Powershell is required.
Silver_Dragon Posted February 8, 2018 Posted February 8, 2018 CMD command working on Windows 10. You not require Powershell. For Work/Gaming: 28" Philips 246E Monitor - Ryzen 7 1800X - 32 GB DDR4 - nVidia RTX1080 - SSD 860 EVO 1 TB / 860 QVO 1 TB / 860 QVO 2 TB - Win10 Pro - TM HOTAS Warthog / TPR / MDF
Len62 Posted February 8, 2018 Posted February 8, 2018 The CMD prompt is still available in Win 10, just not available on the context menus. There is a registry hack that allows you to add CMD prompt back to the context menu. From another post: to update do this: You can update stable 1.5.8 to 2.5 already by opening a command window from the DCS bin folder and running DCS_Updater.exe update 2.5.0.13818@openbeta
QuiGon Posted February 8, 2018 Posted February 8, 2018 The CMD prompt is still available in Win 10, just not available on the context menus. There is a registry hack that allows you to add CMD prompt back to the context menu. From another post: to update do this: You can update stable 1.5.8 to 2.5 already by opening a command window from the DCS bin folder and running DCS_Updater.exe update 2.5.0.13818@openbeta No need for hacking. It's still a regular windows app. Just open the windows menu and search for cmd... and there it is! And you don't need to specify the version. If you jsut want to update to the current OB version just type DCS_Updater.exe update @openbeta Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Nealius Posted February 8, 2018 Author Posted February 8, 2018 (edited) Got it. Some tutorials specifically stated to use Powershell with ./\ before starting the command, but that never worked. After figuring out how to get out of \Windows\system32 in CMD I managed to get it. Edited February 8, 2018 by Nealius
Len62 Posted February 8, 2018 Posted February 8, 2018 No need for hacking. It's still a regular windows app. Just open the windows menu and search for cmd... and there it is! And you don't need to specify the version. If you jsut want to update to the current OB version just type DCS_Updater.exe update @openbeta Yes, it's still available in the windows menu but it does not allow you to open the cmd prompt in a specific folder, which is what the context menu lets you do. As for updating to 2.5 OB I'll let the others comment on it, different users have had varying results depending on if they were updating from 1.5 beta or release versions.
Rudel_chw Posted February 8, 2018 Posted February 8, 2018 None of which worked via either CMD or Powershell, while some tutorials specifically stated to use Powershell with ./\ before starting the command. CMD won't even let me access anything other than Windows\system32 Strange ... I've Windows 10 and cmd Works fine to me, perhaps you have some security software that its interfering? For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
QuiGon Posted February 8, 2018 Posted February 8, 2018 Yes, it's still available in the windows menu but it does not allow you to open the cmd prompt in a specific folder, which is what the context menu lets you do. Yes, but then you navigate to the DCS folder within the CMD using the cd command. I wasn't even aware that there is such a possibility to open the CMD on a specific folder. As for updating to 2.5 OB I'll let the others comment on it, different users have had varying results depending on if they were updating from 1.5 beta or release versions. As far as I have seen, all the people that could not make it work did something wrong (mostly not beeing in the correct folder within the cmd, just like in this case). Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Rudel_chw Posted February 8, 2018 Posted February 8, 2018 Yes, but then you navigate to the DCS folder within the CMD using the cd command. I wasn't even aware that there is such a possibility to open the CMD on a specific folder. Since the DCS_updater utility is so useful, I actually made a custom shortcut for CMD, that has this destination: %windir%\system32\cmd.exe /k pushd "c:\Program Files\Eagle Dynamics" I could in fact made it to open located exactly on the Bin folder, but this one is better as it allows me to cd into any instance of DCS that I may have (stable or open beta for example) For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
Nealius Posted February 8, 2018 Author Posted February 8, 2018 Navigating the CMD with the 'cd' command was new to me. In Windows 7 you could just right click inside the \DCS World\bin folder and open CMD there, and it always worked. In Windows 10 that ability was replaced with Powershell.
Rudel_chw Posted February 8, 2018 Posted February 8, 2018 Navigating the CMD with the 'cd' command was new to me. :) its a benefit of being old .. I learned the command line back on CP/M days and got to personally enjoy SubLogic's first Flight Simulator as well as Spectrum's original Falcon. For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar Mobile: iPad Pro 12.9" of 256 GB
QuiGon Posted February 8, 2018 Posted February 8, 2018 Navigating the CMD with the 'cd' command was new to me. In Windows 7 you could just right click inside the \DCS World\bin folder and open CMD there, and it always worked. In Windows 10 that ability was replaced with Powershell. Ah, now I get what you meant there. Yeah, the CMD has indeed been replaced in the right click menu, although the CMD still remains to exist in Win10 in general. :thumbup: Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
Len62 Posted February 8, 2018 Posted February 8, 2018 Navigating the CMD with the 'cd' command was new to me. In Windows 7 you could just right click inside the \DCS World\bin folder and open CMD there, and it always worked. Yes, but you can modify the registry to bring back that same functionality. I think it was the Fall Creators Update that removed that ability.
Recommended Posts