Hello there, Hope everyone is doing fine in this ongoing pandemic.
I'm asking you guys two questions
1. How was your first experience with your first VPS!
2. How was your experience with your first Free VPS (obtained from somewhere)
i'll write mine a bit :
My first VPS was actually my Free VPS It was i guess 2012-2013, At that time Swift Panel was so famous like everyone use to host it. I was so dumb i thought hosting it would get me a Game Server, So hosted, I got my first VPS from Haphost having 128MB RAM and 128 Swap Memory and 10GB Disk with 100 or maybe mbit port. I literally spent like 9 hours on PC straight didn't slept out of excitement that i actually got a VPS and then i installed centos 5 i guess. Logged into the VPS and literally was just literally looking at the screen now what i do. Watched a youtube tutorial how to install Swift Panel and i literally copied each and every word and they did not provided any type of notepad with commands in the youtube so literally i wrote those links so many times i ilterally remembered epel repo link with every "-" "/". that made me learn different aspects of linux like hosting stuff websites and many different things.
List of Free VPS i have used in past :
1. HapHost (Had a really great experience got alot to learn for start)
2. FreeVPS.US (Contributes a really great part in my learning stage, Learned many things from people there and admins and mods!)
3. Post4VPS (Current! A really nice , decent and friendly forum. Gonna stick here for a good time)
Stay Safe Everyone!
Regards,
sAmI
I'm asking you guys two questions
1. How was your first experience with your first VPS!
2. How was your experience with your first Free VPS (obtained from somewhere)
i'll write mine a bit :
My first VPS was actually my Free VPS It was i guess 2012-2013, At that time Swift Panel was so famous like everyone use to host it. I was so dumb i thought hosting it would get me a Game Server, So hosted, I got my first VPS from Haphost having 128MB RAM and 128 Swap Memory and 10GB Disk with 100 or maybe mbit port. I literally spent like 9 hours on PC straight didn't slept out of excitement that i actually got a VPS and then i installed centos 5 i guess. Logged into the VPS and literally was just literally looking at the screen now what i do. Watched a youtube tutorial how to install Swift Panel and i literally copied each and every word and they did not provided any type of notepad with commands in the youtube so literally i wrote those links so many times i ilterally remembered epel repo link with every "-" "/". that made me learn different aspects of linux like hosting stuff websites and many different things.
List of Free VPS i have used in past :
1. HapHost (Had a really great experience got alot to learn for start)
2. FreeVPS.US (Contributes a really great part in my learning stage, Learned many things from people there and admins and mods!)
3. Post4VPS (Current! A really nice , decent and friendly forum. Gonna stick here for a good time)
Stay Safe Everyone!
Regards,
sAmI
WPExtractor - WordPress Blog Post Extractor in JSON Format
WPExtractor is a python-based tool specifically made for Artificial Intelligence-based projects to make datasets. This helps to collect data from blogs which can be used to train bot in many useful ways.
Features
Usage
Usage:
By default, it will fetch posts from the website. To fetch pages, use the following.
Credits
Manal Shaikh & Somil Gumber.
WPExtractor is a python-based tool specifically made for Artificial Intelligence-based projects to make datasets. This helps to collect data from blogs which can be used to train bot in many useful ways.
Features
- Automatically extract all posts from a WordPress website within seconds.
- Saves the data in the JSON file in the directory for you.
- Easily understandable JSON format to make your life easier
- Responsive developers. Just make an issue, we'll fix it for you
Usage
Usage:
Code:
python main.py -u https://csrockers.inBy default, it will fetch posts from the website. To fetch pages, use the following.
Code:
python main.py -u https://fulltimehosting.net --pagesCredits
Manal Shaikh & Somil Gumber.
This might be a controversial suggestion as the 20-posts policy is strictly implemented here.
I was thinking if it is possible to give someone dispensation automatically if someone forget to make 5 or lower posts when the month end (so they have done 15 or more posts posted). The uncompleted number will be brought to next month so they will need to make more than 20 posts e.g. 22 posts if he/she forgot to do 2 posts at previous month.
Take an example: https://post4vps.com/Thread-VPS-Holder-M...or-October. OldMeister forgot to do 4 of his posts for October and his VPS will be taken down if he did forgot (but somehow he still hold VPS holders role, applied again?). From my point of view, it's like a waste of 16 posts created and time spent for October.
I think this suggestion may only be applied to a holder which already done 15 posts (or 17?) or more but didn't finish at 20 posts. Remainder post(s) should be made maximum next month where holder didn't finish, and if they don't finish at 20 posts + their remainder, VPS will be taken down.
What do you think?
I was thinking if it is possible to give someone dispensation automatically if someone forget to make 5 or lower posts when the month end (so they have done 15 or more posts posted). The uncompleted number will be brought to next month so they will need to make more than 20 posts e.g. 22 posts if he/she forgot to do 2 posts at previous month.
Take an example: https://post4vps.com/Thread-VPS-Holder-M...or-October. OldMeister forgot to do 4 of his posts for October and his VPS will be taken down if he did forgot (but somehow he still hold VPS holders role, applied again?). From my point of view, it's like a waste of 16 posts created and time spent for October.
I think this suggestion may only be applied to a holder which already done 15 posts (or 17?) or more but didn't finish at 20 posts. Remainder post(s) should be made maximum next month where holder didn't finish, and if they don't finish at 20 posts + their remainder, VPS will be taken down.
What do you think?
I'm preparing for doing an upgrade from Windows 7 to Windows 10. I've got a Dell Optiplex 9020 i7 computer. When I did research on driver updates, Dell has a package of drivers for Optiplex 9020 for Windows 10 in a .cab folder.
I'm wondering. Do I wait until after the upgrade and then go through each device to update the drivers, or does Microsoft have a library of drivers of better known brand computers as part of the upgrade?
Or do I download the drivers to a folder that Microsoft can select from during the upgrade process?
I'd like to know whether I could download this cab folder, unzip it and then file it in a folder where Microsoft would find it during the upgrade process - would Microsoft be looking for drivers for Windows 10? Or is that wasted energy and I should wait until after the upgrade?
During my research I noted that the drivers are usually found in the Windows/System32 Driver folders. Any specific folder where one should download the driver update package as there is a pick between Drivers or DriverStore Folders.
Why this is important to me before the upgrade, is that I did a simulation exercise of upgrading my old Lenovo Thinkpad X201 from Windows 7 Professional to Windows 10 Professional. All went well, except I noticed (could also be my imagination) a slight deterioration in the quality of the display - it's a little fuzzy - not a lot, but enough to get my attention. So first thing I did was to go to the Device Manager and update the driver but Windows then said that it has installed the best driver that is available. Problem is when I then checked the details of the driver it says Version 1.3.1.0. I then did lots of research and downloaded the Intel Driver & Support Assistant and then found both Windows 7 and Windows 10 drivers for Version: 8.15.10.2900 Intel HD Graphics the last update dated 2012. I then managed to download a .cab folder and unzipped it, but when I then tried to update the driver again, Windows 10 insists it has the most up to date driver loaded.
Do I need to load the unzipped folder to a specific directory? What should I do for Windows to really update the driver?
I'm wondering. Do I wait until after the upgrade and then go through each device to update the drivers, or does Microsoft have a library of drivers of better known brand computers as part of the upgrade?
Or do I download the drivers to a folder that Microsoft can select from during the upgrade process?
I'd like to know whether I could download this cab folder, unzip it and then file it in a folder where Microsoft would find it during the upgrade process - would Microsoft be looking for drivers for Windows 10? Or is that wasted energy and I should wait until after the upgrade?
During my research I noted that the drivers are usually found in the Windows/System32 Driver folders. Any specific folder where one should download the driver update package as there is a pick between Drivers or DriverStore Folders.
Why this is important to me before the upgrade, is that I did a simulation exercise of upgrading my old Lenovo Thinkpad X201 from Windows 7 Professional to Windows 10 Professional. All went well, except I noticed (could also be my imagination) a slight deterioration in the quality of the display - it's a little fuzzy - not a lot, but enough to get my attention. So first thing I did was to go to the Device Manager and update the driver but Windows then said that it has installed the best driver that is available. Problem is when I then checked the details of the driver it says Version 1.3.1.0. I then did lots of research and downloaded the Intel Driver & Support Assistant and then found both Windows 7 and Windows 10 drivers for Version: 8.15.10.2900 Intel HD Graphics the last update dated 2012. I then managed to download a .cab folder and unzipped it, but when I then tried to update the driver again, Windows 10 insists it has the most up to date driver loaded.
Do I need to load the unzipped folder to a specific directory? What should I do for Windows to really update the driver?
I'm trying to figure out what Windows key Microsoft will register if I should do an upgrade to Windows 10. My current Windows 7 is Windows 7 Professional. However it is an OEM upgrade on the same computer. There was a copy of a 32-bit Windows 7 Home on it before.
What happened was when I purchased the computer and asked for Windows 7 Professional 64-bit, the retail store unbeknownst to me loaded Windows 7 Home 32-bit instead. I never thought to check this. It was completely daft. Like how would one load a 32-bit system on a computer with 8GB RAM - also Dell Optiplex 9020 is a business computer - why load Windows 7 Home on it? Problem was that I didn't use the computer for approx 10 months after I purchased it, as I was still very much attached to Windows XP and my previous computer of the time. So by the time I started using it there was little I could do to sort the retail store out. It was a discount back street little shop as well. Outcome of this was I was only able to use 4GB RAM out of the 8GB available RAM and it seriously bugged me that I was conned.
Any way, I lived with this for two years until end of 2016 when I did a major upgrade of my computer RAM from 8GB to 16GB RAM. I also purchased an OEM Windows 7 Professional 64-bit Disk and License and had that installed and successfully activated on my computer. It obviously had a different Microsoft Key than what was originally installed. When I check my current computer system for the MS Key it shows the latest one for Windows 7 Professional.
So I'm trying to figure out if I should go for an upgrade to Windows 10. Will I end up with Windows 10 Professional or Windows 10 Home? What key is attached to my mother board or would Microsoft be able to see with its upgrade process? Maybe I should do a clean install instead of an upgrade and then enter my last activated Windows 7 Professional Key? Instead of a simple upgrade?
What happened was when I purchased the computer and asked for Windows 7 Professional 64-bit, the retail store unbeknownst to me loaded Windows 7 Home 32-bit instead. I never thought to check this. It was completely daft. Like how would one load a 32-bit system on a computer with 8GB RAM - also Dell Optiplex 9020 is a business computer - why load Windows 7 Home on it? Problem was that I didn't use the computer for approx 10 months after I purchased it, as I was still very much attached to Windows XP and my previous computer of the time. So by the time I started using it there was little I could do to sort the retail store out. It was a discount back street little shop as well. Outcome of this was I was only able to use 4GB RAM out of the 8GB available RAM and it seriously bugged me that I was conned.
Any way, I lived with this for two years until end of 2016 when I did a major upgrade of my computer RAM from 8GB to 16GB RAM. I also purchased an OEM Windows 7 Professional 64-bit Disk and License and had that installed and successfully activated on my computer. It obviously had a different Microsoft Key than what was originally installed. When I check my current computer system for the MS Key it shows the latest one for Windows 7 Professional.
So I'm trying to figure out if I should go for an upgrade to Windows 10. Will I end up with Windows 10 Professional or Windows 10 Home? What key is attached to my mother board or would Microsoft be able to see with its upgrade process? Maybe I should do a clean install instead of an upgrade and then enter my last activated Windows 7 Professional Key? Instead of a simple upgrade?
This discussion started in the 62nd Giveaway Announcement about the possibility of a second VPS, how to get new members to join the Forum, how to increase the number of posts and member post experiences. It was suggested that the discussion be moved to the Discussion and Feedback Forum which it now has - thanks @tiwil:
That may not be as farfetched a notion as you think it is. Given the low number of VPS Requests. But not straight away though. @Dynamoishes to give it a couple or more months first to see whether the number of VPS requests improve. If not, we may well think of making a second VPS available in exchange for additional posts.
In the meanwhile, given that we only received one VPS Request, we've decided to keep the VPS Request Forum open for a few more days. Since the application was for VPS 1, and there are 6 available VPSs in the Plan, we have issued VPS 1 immediately. @Rehanishes to see whether he can get VPS 1 to work as a Games Server. If he does, that would be awesome for sure.
For now the VPS Requests Forum will remain open for applications until end of the weekend, 8th-9th of November.
(11-05-2020, 02:51 PM)tbelldesignco Wrote: If I had the time to manage another... I probably would sign up for another haha.
That may not be as farfetched a notion as you think it is. Given the low number of VPS Requests. But not straight away though. @Dynamoishes to give it a couple or more months first to see whether the number of VPS requests improve. If not, we may well think of making a second VPS available in exchange for additional posts.
In the meanwhile, given that we only received one VPS Request, we've decided to keep the VPS Request Forum open for a few more days. Since the application was for VPS 1, and there are 6 available VPSs in the Plan, we have issued VPS 1 immediately. @Rehanishes to see whether he can get VPS 1 to work as a Games Server. If he does, that would be awesome for sure.
For now the VPS Requests Forum will remain open for applications until end of the weekend, 8th-9th of November.
Hello everyone
hope everyone is having a great day!
I am a new member
Looking forward to learning from everyone who has experience related to me and VPS management
hope everyone is having a great day!
I am a new member
Looking forward to learning from everyone who has experience related to me and VPS management
I am very curious to learn whether there are experienced Android flashers here who do flashing of their Android devices on a regular basis, or have experiences to share or tips to give.
When I was researching how to flash my Samsung Tablet I learned to do this with great caution only, and preferably not at all if one is not very advanced, experienced or have taken every possible care to do it right. For starters, with a Samsung device the warranty will be immediately voided with flashing as it has something included in its firmware that would detect when flashing is used.
I found two tools for flasing a device - Google Developer SDK Tools and Samsung's Odin3. Which one are you using? Is the difference perhaps to do with SDK Google tools would only be used for Google devices like Nexxus, and Odin3 has specifically been created for use with Samsung? I learned that the Samsung developers are officially using Odin3, and have unofficially released it for use by Samsung users, but strictly at the users' own risk with loss of warranty.
From my research, this is my summary of steps to follow for flashing my Samsung Tablet. If experienced users notice a "not to do" step - please let me know:
1. Check the specific model of my Samsung Tablet - which is SM-T819. What I learned during my research was that the Android firmware is tablet model specific rather than tablet version specific. This means the Android firmware of one Samsung Galaxy S2 may not work on another Samsung Galaxy S2 with a different model number.
2. I had to search very deep to find a reliable source for downloading the exact Android firmware for my model Samsung tablet. The challenge was every possible tutorial directed one to Sammobile, the Web authority for Samsung mobile firmware, but then it looks like not only does this Website want you to register an account, but also to take a paid subscription - which it does in a sneaky way. So eventually I dropped this Website and thankfully if one searches deep enough there are reliable alternatives. After a very long search I found this source that looked reliable although I can't vouch for it as I haven't used the firmware yet. I judge it by how professional the firmware is presented and operates, and my MalwareBytes hasn't found any malware or viruses when I was downloading a copy of the firmware:
https://desktop.firmware.mobi/
You need to input your device model at the page that comes up, and then you are taken to this page to download the firmware. You then have to choose a .tar.MD5 boot image:
https://desktop.firmware.mobi/device:825/firmware:2139
If you are downloading the firmware it's best to go for the last date in the firmware before it changed to the next Android version. I was looking at the possibility of changing from Nougat (Android 7) back to Marshmallow (Android 6.01). The last available Marshmallow version was dated 6 December 2016. After which the firmware changed to Nougat (Android 7.0) in 2017.
3. Next is to set up the flashing tool on your computer, which seems to be Odin3 for Samsung. Again, during my research it felt as though I was wading through risky Websites that may have malware attached. So I first downloaded free Malwarebytes trial, as a way to check possible virus sites. I then found this download place for Odin3 script:
https://updato.com/how-to/how-to-install...sing-odin/
One then has to set the tool up.
While I was researching this step, I also checked the Google SDK tools route. It looked very complicated. Looks like a couple or more years ago one was able to download the SDK tools separately from Google but now one has to get it after downloading Android Studio first.
Here are a few good YouTube tutorials by Jamie Wagner on how to set up the SDK Tools for flashing Nexxus mobile phones:
1. How To Download & Install Android Studio On Windows PC
2. How To Fastboot OEM Unlock & Lock Bootloader Android Nexus 7
3. How To Install/Flash Android KitKat Nexus Factory Images
4. How To Install Google USB Driver Android ADB Debugging Windows PC
5. How To Downgrade Android Nougat To Android Marshmallow
4. You then also discover that you may need a USB driver for the device you are going to flash on your computer. Otherwise your computer won't be able to communicate with the device. How I checked it was to connect my Samsung Tablet to my computer with a USB cable and then navigated to devices in the Control Panel of my computer. My Samsung Tablet had a yellow exclamation mark next to it which indicated there was an issue with the computer finding a USB driver for the device. Then after finding the right driver (below), and I was able to install the driver by rightclicking the Yellow Exclamation mark, the yellow exclamation mark went away. The driver is a very important tool so your flashing tool in your computer can communicate with the device while you are flashing the firmware. You won't be able to do it otherwise.
https://developer.samsung.com/mobile/and...river.html
5. You then have to set up your Samsung device - unlock it. You do this by going into the settings of the device and getting to the Developer Tools. Samsung seems to like to hide the Developer Tools in the settings, as to get to it I had to tap 5-7 times on the "About Tablet" tablet details for it to open up. You then have to enable OEM Unlocking and USB Debugging.
6. Next very important preparation is to make a backup of the contents of your device. It is very important that you don't use the backup feature on the device itself. As this may create issues with the flashing. You do the backup to your computer by using a USB cable as you would do with uploading photos etc. There are many ways to do this - you may already have your preferred way, but for Samsung there is Samsung Smart Switch that can be downloaded from here:
https://www.samsung.com/za/support/smart-switch/
7. After all of the preparation one is ready to do the flashing. I haven't done this yet as I'm not quite convinced it is really necessary relative to the risk involved. You start the flashing process by first turning off the Samsung device. Following this you press at the same time the home, power and volume down buttons. You then use the volume up button to scroll down to download mode and use the power button to OK it. You then connect the device with a USB cable to the computer. When you click on Odin it should come up with the flash load page and there will be a green box indicating it is successfully communicating with the device. If it isn't, then the first issue to investigate would be the USB driver for the device. And then the settings. Great caution is needed to ensure that the partition box in the Odin page is unticked. One then drops the firmware .tar.mb5 file into Odin in the exact right place (refer tutorials below), and the flashing should ideally happen then.
Here are two tutorials to show you how it works - one is a YouTube tutorial and the other a Web page. The Web page tutorial gives much more information on the benefits of flashing, and also troubleshooting when things go wrong. It prepares you for typical issues and how to get out of them if they should happen to you.
https://www.youtube.com/watch?v=nOGpFJnLP3A
https://updato.com/how-to/how-to-install...sing-odin/
8. When one uses SDK Tools for Google devices the steps are slightly different and more complicated. Best to refer to the tutorials by Jamie Wagner above and don't miss any of them. From what I can understand the flashing tools are included in the firmware download, and you have to add the SDK Platform Tools (you get it from the Userapp folder) to the package. You need to navigate to the appdata/Android/ folder until you get to SDK_platform_tools and add the contents of this to your firmware folder. You then have to unlock the device, get the device in download mode, and you do that with the command CMD of your computer. The tutorials I listed under (3) above by Jamie Wagner explain how to do it. It's best to study very carefully through all of the tutorials and not giving any of them a miss.
Odin3 sounds easier to me, but maybe with more room for error - it's not fail safe. SDK Tools sound more controlled and detailed, but also with room for error, particularly in setting up the firmware and tool package. My choice for my Samsung device would be Odin3. But only if my need for doing any flashing outways the risks. I'm still hoping one day that Android will allow one to change firmware versions easier with no need for flashing, or at least more fail safe.
When I was researching how to flash my Samsung Tablet I learned to do this with great caution only, and preferably not at all if one is not very advanced, experienced or have taken every possible care to do it right. For starters, with a Samsung device the warranty will be immediately voided with flashing as it has something included in its firmware that would detect when flashing is used.
I found two tools for flasing a device - Google Developer SDK Tools and Samsung's Odin3. Which one are you using? Is the difference perhaps to do with SDK Google tools would only be used for Google devices like Nexxus, and Odin3 has specifically been created for use with Samsung? I learned that the Samsung developers are officially using Odin3, and have unofficially released it for use by Samsung users, but strictly at the users' own risk with loss of warranty.
From my research, this is my summary of steps to follow for flashing my Samsung Tablet. If experienced users notice a "not to do" step - please let me know:
1. Check the specific model of my Samsung Tablet - which is SM-T819. What I learned during my research was that the Android firmware is tablet model specific rather than tablet version specific. This means the Android firmware of one Samsung Galaxy S2 may not work on another Samsung Galaxy S2 with a different model number.
2. I had to search very deep to find a reliable source for downloading the exact Android firmware for my model Samsung tablet. The challenge was every possible tutorial directed one to Sammobile, the Web authority for Samsung mobile firmware, but then it looks like not only does this Website want you to register an account, but also to take a paid subscription - which it does in a sneaky way. So eventually I dropped this Website and thankfully if one searches deep enough there are reliable alternatives. After a very long search I found this source that looked reliable although I can't vouch for it as I haven't used the firmware yet. I judge it by how professional the firmware is presented and operates, and my MalwareBytes hasn't found any malware or viruses when I was downloading a copy of the firmware:
https://desktop.firmware.mobi/
You need to input your device model at the page that comes up, and then you are taken to this page to download the firmware. You then have to choose a .tar.MD5 boot image:
https://desktop.firmware.mobi/device:825/firmware:2139
If you are downloading the firmware it's best to go for the last date in the firmware before it changed to the next Android version. I was looking at the possibility of changing from Nougat (Android 7) back to Marshmallow (Android 6.01). The last available Marshmallow version was dated 6 December 2016. After which the firmware changed to Nougat (Android 7.0) in 2017.
3. Next is to set up the flashing tool on your computer, which seems to be Odin3 for Samsung. Again, during my research it felt as though I was wading through risky Websites that may have malware attached. So I first downloaded free Malwarebytes trial, as a way to check possible virus sites. I then found this download place for Odin3 script:
https://updato.com/how-to/how-to-install...sing-odin/
One then has to set the tool up.
While I was researching this step, I also checked the Google SDK tools route. It looked very complicated. Looks like a couple or more years ago one was able to download the SDK tools separately from Google but now one has to get it after downloading Android Studio first.
Here are a few good YouTube tutorials by Jamie Wagner on how to set up the SDK Tools for flashing Nexxus mobile phones:
1. How To Download & Install Android Studio On Windows PC
2. How To Fastboot OEM Unlock & Lock Bootloader Android Nexus 7
3. How To Install/Flash Android KitKat Nexus Factory Images
4. How To Install Google USB Driver Android ADB Debugging Windows PC
5. How To Downgrade Android Nougat To Android Marshmallow
4. You then also discover that you may need a USB driver for the device you are going to flash on your computer. Otherwise your computer won't be able to communicate with the device. How I checked it was to connect my Samsung Tablet to my computer with a USB cable and then navigated to devices in the Control Panel of my computer. My Samsung Tablet had a yellow exclamation mark next to it which indicated there was an issue with the computer finding a USB driver for the device. Then after finding the right driver (below), and I was able to install the driver by rightclicking the Yellow Exclamation mark, the yellow exclamation mark went away. The driver is a very important tool so your flashing tool in your computer can communicate with the device while you are flashing the firmware. You won't be able to do it otherwise.
https://developer.samsung.com/mobile/and...river.html
5. You then have to set up your Samsung device - unlock it. You do this by going into the settings of the device and getting to the Developer Tools. Samsung seems to like to hide the Developer Tools in the settings, as to get to it I had to tap 5-7 times on the "About Tablet" tablet details for it to open up. You then have to enable OEM Unlocking and USB Debugging.
6. Next very important preparation is to make a backup of the contents of your device. It is very important that you don't use the backup feature on the device itself. As this may create issues with the flashing. You do the backup to your computer by using a USB cable as you would do with uploading photos etc. There are many ways to do this - you may already have your preferred way, but for Samsung there is Samsung Smart Switch that can be downloaded from here:
https://www.samsung.com/za/support/smart-switch/
7. After all of the preparation one is ready to do the flashing. I haven't done this yet as I'm not quite convinced it is really necessary relative to the risk involved. You start the flashing process by first turning off the Samsung device. Following this you press at the same time the home, power and volume down buttons. You then use the volume up button to scroll down to download mode and use the power button to OK it. You then connect the device with a USB cable to the computer. When you click on Odin it should come up with the flash load page and there will be a green box indicating it is successfully communicating with the device. If it isn't, then the first issue to investigate would be the USB driver for the device. And then the settings. Great caution is needed to ensure that the partition box in the Odin page is unticked. One then drops the firmware .tar.mb5 file into Odin in the exact right place (refer tutorials below), and the flashing should ideally happen then.
Here are two tutorials to show you how it works - one is a YouTube tutorial and the other a Web page. The Web page tutorial gives much more information on the benefits of flashing, and also troubleshooting when things go wrong. It prepares you for typical issues and how to get out of them if they should happen to you.
https://www.youtube.com/watch?v=nOGpFJnLP3A
https://updato.com/how-to/how-to-install...sing-odin/
8. When one uses SDK Tools for Google devices the steps are slightly different and more complicated. Best to refer to the tutorials by Jamie Wagner above and don't miss any of them. From what I can understand the flashing tools are included in the firmware download, and you have to add the SDK Platform Tools (you get it from the Userapp folder) to the package. You need to navigate to the appdata/Android/ folder until you get to SDK_platform_tools and add the contents of this to your firmware folder. You then have to unlock the device, get the device in download mode, and you do that with the command CMD of your computer. The tutorials I listed under (3) above by Jamie Wagner explain how to do it. It's best to study very carefully through all of the tutorials and not giving any of them a miss.
Odin3 sounds easier to me, but maybe with more room for error - it's not fail safe. SDK Tools sound more controlled and detailed, but also with room for error, particularly in setting up the firmware and tool package. My choice for my Samsung device would be Odin3. But only if my need for doing any flashing outways the risks. I'm still hoping one day that Android will allow one to change firmware versions easier with no need for flashing, or at least more fail safe.
24 VPSs are Available
- 6x VPS 1 [Games Servers not advised]
- 1x VPS 2 [Games Servers allowed]
- 1x VPS 3 [Games Servers allowed]
- 2x VPS 6 [Games Servers allowed]
- 5x VPS 7 [Games Servers not allowed] [USA Locations: Atlanta, NY, Seattle, LA]
- 3x VPS 9 [Games Servers are allowed][USA Locations: Buffalo, Phoenix, Seattle]
- 2x VPS 10 [Games Servers not advised]
- 1x VPS 11 [Games Servers not allowed]
- 1x VPS 12 [Games Servers not allowed]
- 1x VPS 15 [Games Servers not allowed - zero tolerance policy]
- 1x VPS 18 [Until end of Dec only - Games Servers allowed]
Note that VPS 18 will only be available until the end of December.
As mentioned every where, PLEASE study the Terms of Service of the VPS/s you request very carefully BEFORE you apply.
For comparing the VPS Specifications, users can check https://post4vps.com/compare/#1,2,3,6,7,...1,12,15,18
PLEASE READ AND UNDERSTAND THE TERMS AND CONDITIONS OF THE SPONSOR BEFORE YOU APPLY - REFER BELOW:
- Users must read and agree to all terms of the SPONSOR (of the VPS which they want) when they apply. These can be found on our Plans Page.
- When you apply, please let us know your preferred OS and the Domain you will be using with the VPS.
- Read Our Forum Rules before applying.
- You should have met our minimum requirements to get VPS.
- Read Application Format before applying. (If the application format is wrong then your Request will be rejected)
- You must post your VPS application in VPS Request Forum.
- Read TOS of VPS providers before applying.
Use RDP Wrapper Library with latest Windows 10 / Server OS Versions
Howdy Post4VPS Staff & Community
Before I start writing about the main subject of today's guide I will start off with explaining what the "RDP Wrapper" library actually is:
Above was a little explanation about the RDP Wrapper library. Now let's talk about the subject of this guide. The RDP Wrapper is no longer in development and has no support since the end of 2018. That means that newer Windows 10 Version that came out after 2018 aren't really supported or rather said the RDP Wrapper library doesn't properly work on newer / latest Windows 10 builds. This guide will show you how to fix this issue and be able to use the RDP Wrapper library on the latest Windows 10 / Server builds (e.g. Windows 10 2009 Home or Windows Server 2019).
The actual constellation / my setup: Windows 10 Home Build 20H2 (2009) with a license inside a Hyper-V VM with 2 CPU Cores, 4 GB RAM and a 64 GB vSSD. It doesn't matter whether your computer is physical or virtual. I'm just using a virtual system because I don't have a device with Windows 10 Home in physical form. Due to the limited feature set of Windows 10 Home RDP is not available. I however want to use RDP to access the VM remotely from my tablet to do some stuff without always being at my computer. I'm going to install RDP Wrapper and fix it up to work on my setup.
![[Image: qg94ofh.png]](https://i.imgur.com/qg94ofh.png)
![[Image: yDTxrvo.png]](https://i.imgur.com/yDTxrvo.png)
Disclaimer: You are performing all actions at your own risks. You cannot make me responsible for anything that happens. I hold no responsibility for the actions performed by you with this guide. This is solely for educational and non commerical use only! The legality of the subject of this guide is not clearly defined. See here for more information.
Let's get started. Make sure you have administrative rights / access on your machine as this level of access is required to perform actions in this guide.
Step #1
Open your web browser, go to https://github.com/stascorp/rdpwrap/releases and download the latest version of RDP Wrapper (currently and as of 2018 it is version 1.6.2). Choose the .zip file version of the release as the .MSI installer will not work at all on latest Windows 10 / Server builds.
Or click this link to download the .zip file directly from the release page.
Also download this file.
Step #2
Press the Windows key and the R key at the same time. In the small "Run" window type in the following text and hit the ENTER key:
The Windows explorer will open up. Inside the directory that opened up create a folder called "RDP Wrapper". Do not use another path than %ProgramFiles%\RDP Wrapper!
Full path should normally be "C:\Program Files\RDP Wrapper".
![[Image: GIIeDv6.png]](https://i.imgur.com/GIIeDv6.png)
Step #3
Extract the content of the RDP Wrapper .zip file into the RDP Wrapper folder you have created.
Additionally extract the content of the autoupdate.zip file that you have downloaded into the RDP Wrapper folder.
The RDP Wrapper folder should look like below:
![[Image: NUpRmYr.png]](https://i.imgur.com/NUpRmYr.png)
Step #4
Open the "Helper" folder in the RDP Wrapper folder and run "autoupdate__enable_autorun_on_startup.bat" as an administrator (right click the .bat file and click on "Run as Administrator").
If a small and blue Windows protection window opens click on "More info" and then on the "Run anyway" button to run the .bat file. Alternatively you can disable Windows smart screen to get rid of this blue Windows protection windows.
A CMD window will open up. Once its done you will see a message saying to press any key to close the window. Just press any key to close that windows.
Set in your Antivirus an exclusion for the folder "%ProgramFiles%\RDP Wrapper" to prevent the deletion of RDP Wrapper files.
Step #5
After the step above run "autoupdate.bat" inside the RDP Wrapper folder as an administrator (right click the bat file and click on "Run as Administrator").
If a small and blue Windows protection window opens click on "More info" and then on the "Run anyway" button to run the .bat file. Alternatively you can disable Windows smart screen to get rid of this blue Windows protection windows.
A CMD window will open up. It will perform a lot of tasks and install fixes for the RDP Wrapper library 1.6.2 that we downloaded. Once everything is finished the CMD window will close.
After that you can run the "RDPConf.exe" file in the RDP Wrapper folder to see whether the RDP Wrapper library was installed and is working properly. Below an example of a working RDP Wrapper:
![[Image: xpN38nD.png]](https://i.imgur.com/xpN38nD.png)
Now you can verify that RDP is working on your Windows 10 Home computer by using a different device with a RDP client and typing in the IP address of your Windows 10 Home computer. If everything works you will be connect to your computer via RDP and you can login with your user.
![[Image: llq9AA6.png]](https://i.imgur.com/llq9AA6.png)
![[Image: dzUFprr.png]](https://i.imgur.com/dzUFprr.png)
![[Image: V95OU9c.png]](https://i.imgur.com/V95OU9c.png)
As you can see I'm connected to my Windows 10 Home VM. Windows still says that RDP is not available because of Windows 10 Home but we're connected via RDP. We have successfully enable RDP on our Windows 10 Home computer.
That's it! Couldn't be easier, right? You can configure RDP Wrapper further by editing the rdpwrapper.ini file inside the RDP Wrapper folder. WARNING: You shouldn't touch the file if you don't know what you are doing. Some options can be guessed easily by the names but others aren't that easy to understand and can break RDP on your system.
Before I start writing about the main subject of today's guide I will start off with explaining what the "RDP Wrapper" library actually is:
Quote:Imagine you are a normal Windows user and your computer came with Windows 10 Home preinstalled. Now you might know that the Windows 10 Home edition is very limited in many aspects such as a lot less control over the system settings (e.g. updates are forced and cannot be turned off). Another locked down feature is the absolute lack of the remote desktop feature / the remote desktop server. That means you cannot connect to your computer remotely in your network from e.g. a tablet or something similar.
Such a feature, while not many normal users may use it, is actually a very useful feature. So for those who are very interested in this feature... what should these people do? The next higher up version that comes with the remote desktop feature / server is Windows 10 Pro. Would you be willing to go out and buy a Windows 10 Pro license? Of course you could get a cheap license from some random or weird site. You don't have to do this! It could especially be a dangerous scam / rip off.
Here is where the "RDP Wrapper" library comes into play. It is a RDP library with a lot of modifications and tweaks. You can install RDP Wrapper on your Windows 10 Home computer to get back the Windows remote desktop feature / server for free. Not only that - it also supports concurrent RDP sessions which is usually only a premium Windows Server feature (2 sessions by default and many more with the expensive RDS-CAL licenses). RDP Wrapper library can also be used on Windows Server products to unlock more than 2 concurrent RDP sessions for free (grey area subject). It is compatible from Windows Vista to Windows 10.
Above was a little explanation about the RDP Wrapper library. Now let's talk about the subject of this guide. The RDP Wrapper is no longer in development and has no support since the end of 2018. That means that newer Windows 10 Version that came out after 2018 aren't really supported or rather said the RDP Wrapper library doesn't properly work on newer / latest Windows 10 builds. This guide will show you how to fix this issue and be able to use the RDP Wrapper library on the latest Windows 10 / Server builds (e.g. Windows 10 2009 Home or Windows Server 2019).
The actual constellation / my setup: Windows 10 Home Build 20H2 (2009) with a license inside a Hyper-V VM with 2 CPU Cores, 4 GB RAM and a 64 GB vSSD. It doesn't matter whether your computer is physical or virtual. I'm just using a virtual system because I don't have a device with Windows 10 Home in physical form. Due to the limited feature set of Windows 10 Home RDP is not available. I however want to use RDP to access the VM remotely from my tablet to do some stuff without always being at my computer. I'm going to install RDP Wrapper and fix it up to work on my setup.
Disclaimer: You are performing all actions at your own risks. You cannot make me responsible for anything that happens. I hold no responsibility for the actions performed by you with this guide. This is solely for educational and non commerical use only! The legality of the subject of this guide is not clearly defined. See here for more information.
Let's get started. Make sure you have administrative rights / access on your machine as this level of access is required to perform actions in this guide.
Step #1
Open your web browser, go to https://github.com/stascorp/rdpwrap/releases and download the latest version of RDP Wrapper (currently and as of 2018 it is version 1.6.2). Choose the .zip file version of the release as the .MSI installer will not work at all on latest Windows 10 / Server builds.
Or click this link to download the .zip file directly from the release page.
Also download this file.
Step #2
Press the Windows key and the R key at the same time. In the small "Run" window type in the following text and hit the ENTER key:
Code:
%ProgramFiles%The Windows explorer will open up. Inside the directory that opened up create a folder called "RDP Wrapper". Do not use another path than %ProgramFiles%\RDP Wrapper!
Full path should normally be "C:\Program Files\RDP Wrapper".
Step #3
Extract the content of the RDP Wrapper .zip file into the RDP Wrapper folder you have created.
Additionally extract the content of the autoupdate.zip file that you have downloaded into the RDP Wrapper folder.
The RDP Wrapper folder should look like below:
Step #4
Open the "Helper" folder in the RDP Wrapper folder and run "autoupdate__enable_autorun_on_startup.bat" as an administrator (right click the .bat file and click on "Run as Administrator").
If a small and blue Windows protection window opens click on "More info" and then on the "Run anyway" button to run the .bat file. Alternatively you can disable Windows smart screen to get rid of this blue Windows protection windows.
A CMD window will open up. Once its done you will see a message saying to press any key to close the window. Just press any key to close that windows.
Set in your Antivirus an exclusion for the folder "%ProgramFiles%\RDP Wrapper" to prevent the deletion of RDP Wrapper files.
Step #5
After the step above run "autoupdate.bat" inside the RDP Wrapper folder as an administrator (right click the bat file and click on "Run as Administrator").
If a small and blue Windows protection window opens click on "More info" and then on the "Run anyway" button to run the .bat file. Alternatively you can disable Windows smart screen to get rid of this blue Windows protection windows.
A CMD window will open up. It will perform a lot of tasks and install fixes for the RDP Wrapper library 1.6.2 that we downloaded. Once everything is finished the CMD window will close.
After that you can run the "RDPConf.exe" file in the RDP Wrapper folder to see whether the RDP Wrapper library was installed and is working properly. Below an example of a working RDP Wrapper:
Now you can verify that RDP is working on your Windows 10 Home computer by using a different device with a RDP client and typing in the IP address of your Windows 10 Home computer. If everything works you will be connect to your computer via RDP and you can login with your user.
As you can see I'm connected to my Windows 10 Home VM. Windows still says that RDP is not available because of Windows 10 Home but we're connected via RDP. We have successfully enable RDP on our Windows 10 Home computer.
That's it! Couldn't be easier, right? You can configure RDP Wrapper further by editing the rdpwrapper.ini file inside the RDP Wrapper folder. WARNING: You shouldn't touch the file if you don't know what you are doing. Some options can be guessed easily by the names but others aren't that easy to understand and can break RDP on your system.
| Welcome, Guest |
|
You have to register before you can post on our site. |
| Search Forums |
|
(Advanced Search) |
| Forum Statistics |
|
» Members: 2,271 » Latest member: orzpainter » Forum threads: 3,103 » Forum posts: 34,831 Full Statistics |
| Online Users |
|
There are currently 456 online users. » 0 Member(s) | 453 Guest(s) Bing, Yandex, Google |
| Latest Threads |
|
How Virtual Cards Are Cha...
Forum: Offtopic Last Post: bestadvisor 07-07-2025, 08:35 PM » Replies: 0 » Views: 23 |
|
LLHOST — 40% OFF Netherla...
Forum: Free VPS Providers Last Post: LLHOST 07-02-2025, 08:42 AM » Replies: 0 » Views: 105 |
|
✅ Affordable VPS Hosting ...
Forum: Cheap VPS Providers Last Post: RIYAD 07-02-2025, 03:02 AM » Replies: 0 » Views: 125 |
|
15% Lifetime Discount on ...
Forum: Cheap Providers Last Post: LLHOST 06-25-2025, 05:03 AM » Replies: 0 » Views: 99 |
|
Get 50% Off Your First Ne...
Forum: Others Last Post: LLHOST 06-19-2025, 10:09 AM » Replies: 0 » Views: 203 |
|
Buy DemoTiger Videos on c...
Forum: Others Last Post: DewlanceHosting 06-14-2025, 05:32 PM » Replies: 7 » Views: 3,993 |
|
KVM & OpenVZ Yearly VPS f...
Forum: Cheap VPS Providers Last Post: HostNamaste 06-10-2025, 11:53 AM » Replies: 1 » Views: 733 |
|
Budget Dedicated Servers ...
Forum: Others Last Post: HostNamaste 06-10-2025, 11:49 AM » Replies: 1 » Views: 752 |
|
Multiple IPs VPS in Franc...
Forum: Cheap Providers Last Post: HostNamaste 06-10-2025, 11:47 AM » Replies: 1 » Views: 790 |
|
60 % OFF on unmanaged VPS...
Forum: Others Last Post: LLHOST 06-09-2025, 02:21 PM » Replies: 0 » Views: 132 |