Still With Eyes Closed
  • Home
  • My Books
  • Jesus Day
  • News
  • Eyes Wide Open
  • About
    • Contact
  • Home
  • My Books
  • Jesus Day
  • News
  • Eyes Wide Open
  • About
    • Contact

Joseph Rutherford in Beth-Sarim

9/6/2022

0 Comments

 

The intent of Beth-Sarim was for those resurrected early that would be princes in all the Earth. Moses, Abraham, David etc were expected to be returned to life in the 1920's. That was the understanding at the time. Brother Rutherford bought property in California and Beth-Sarim was created. This was where these resurrected ones were to live. Of course, the thinking was far too early, so when Brother Rutherford got sick it turned into his retirement home and a place of rest and ease for him. After his death the property was sold for profit. Although at the time of purchase and the reason for such seems odd to us today. Jehovah ended up using the property to the benefit of the organization.

In 1941, when working isolated territory in western Kentucky, we attended the zone (now circuit) assembly at Cape Girardeau, Missouri. While preparing the evening meal in the cafeteria I was called to answer a long-distance telephone call offering me the privilege of helping to nurse Brother Rutherford, then very ill in a hospital in Elkhart, Indiana. Shocked by news of his illness, overwhelmed by tremendous responsibility I would be expected to shoulder, my first reaction was to refuse; but, ever fearful of refusing an assignment for fear another would not be given, I prayerfully accepted. At once I left the assembly headquarters and made the necessary preparations for my new duties, upon which I entered thirty-six hours later when I entered the sick room of our stricken brother. A week later I was privileged to accompany Brother Rutherford and his party to California, where we lived in Beth-Sarim, the “House of the Princes,” for the next eight weeks until his death January 8, 1942. Had I not been a pioneer that unusual and precious service would not have been mine, as all his associates and helpers were from ranks of full-time workers.
(w55 11/1 pp 653-656)

Brother Rutherford, 72 years of age, survived the surgery. Shortly thereafter he was taken to a residence in California he had named Beth-Sarim. It was evident to his loved ones, and to medical experts, that he would not recover. In fact, he required further surgery.
(Proclaimers Book Chapter 7 Page 72)

Often we preached near Beth-Sarim, which was where the ailing president of the Watch Tower Society, Brother Rutherford, had spent the winters before his death in 1942. We visited regularly and had dinner with the full-time servants there. Such happy visits made me decide that this was truly the kind of life I wanted. I then made Gilead School and missionary service my goal in life.
(W92 3/1 pp 26-30)

0 Comments

Brother Rutherford Visits Australia 1938

9/6/2022

0 Comments

 

Very rare video clip of Brother Rutherford when he visited Australia in 1938, just a few years before his death.

0 Comments

Union Hill Tennessee, a Dead Town

9/6/2022

0 Comments

 

Before Livingston Tennessee, before Hilham, there was a town in Overton County Tennessee that would have been the county seat and stopped the formation of Rickman, Livingston and Hilham.
Once there was Union Hill. Settled due to its water source and meandering road connection to Cookeville Tennessee. It was spread out over several miles and connected several important roads at the time.
But progress took that away. The railroad from Algood wanted a line into to the heart of Overton County and the best route was to connect to a small town called Livingston. The line would bypass Union Hill.
When news spread many of the people of Union Hill tore down their houses and relocated to Livingston. In fact so many moved the town of Union Hill died. 
There is not much left today and before that disappeared I captured what I could as a remembrance to a town now dead and forgotten.

​This was Union Hill Tennessee.

0 Comments

My 1st Time Flying and Being a Pilot

9/6/2022

0 Comments

 

In March of 2012 a tornado touched down in Overton County Tennessee. A friend of mine had a helicopter and asked me if I would like to fly over the damaged area and film it. I of course said yes. After we filmed the damage, he asked me if I would like to pilot the helicopter and I said yes while he filmed. It was an experience I will never forget. We flew over Livingston Tennessee and Overton County.

0 Comments

If you see it Report it - Before Harm is Done

9/6/2022

0 Comments

 

There is a lot of encouragement from law enforcement to report dangerous activity, before harm, such as a mass shooting, takes place. In many areas law enforcement is now taking these red flag reports serious. 
However in my neighborhood is a man who has proven dangerous. He has an alleged past history and his behavior now suggest he has not changed. My wife has expressed concern for her safety and she feels that he is a danger to her. We have passed this on to the Overton County Sheriff, yet nothing is being taken seriously. Below are a few security videos, there rest are located on my YouTube Channel >CLICK HERE<.
David Wayne Reeder of Livingston TN has created a great deal of fear in the neighborhood. Some things that are not allegations.
1) He attempted to enter our home when he thought my wife was home alone.
2) When my wife was at my son's home, David followed her there in his car and pulled into the driveway, blocking her leaving. After she picked up a shovel and called me he left.
3) When my wife is working in the yard he will watch her for long periods of time over the fence.
4) When he thought my wife was on the porch couch he exposed himself, but this was not captured on security video so we did not report it.

0 Comments

Website Update in Progress

6/21/2022

0 Comments

 
I will be updating my website over the next few days, so hang in there with me as there will be some format issues and picture issues until complete.
0 Comments

Phonak App Defaults to Autosense and will Not Save Custom Setting

6/21/2022

0 Comments

 
For many wearing hearing aids is not an option, this is the case for my wife. The problem is she hates them. The primary reason she hates them is because she can create a custom setting on the Phonak App and then it defaults back to Autosense or the prescription setting. If you Google this issue, you will find that many are having the same problem and if you go to Phonak’s forums you will discover they appear to be clueless. After looking into my wife’s remote app, I not only discovered the fix, but the cause of the problem. Continue reading to discover the problem and the solution. However, do not drop to the solution for the quick fix, without understanding the why; you may not like the solution.
 
First the PROBLEM:
As a person needing hearing aids, like my wife yours may have cost over $6,000.00. At first you are excited, you can create custom settings on the Phonak app for just about any situation and by wearing them all the time, your brain will adjust to the background noise and in time you will adjust. But then you quickly discover that once you have created a custom setting on the Phonak remote app, it reverts back to Autosense and sometimes this is so unexpected that it causes hearing pain. The Phonak Company has identified the issue. Every time ANY sound is created on the phone, this includes keyboard sounds, ANY notification from any app, any audio sound made, the remote app defaults back to Autosense. On the Phonak website the suggested “fix” is to turn off ALL notifications, this even includes text, social media, and it would even include severe weather related notifications. This is simply NOT an option. Phonak’s expectation is the every sound and audio made on the phone is to be played through the hearing aids. However if you take them out at night and it is dangerous weather you need to hear notifications. The expectation is that you will go through the advanced settings on your phone EVERY time to turn notification on and off. This is not practical. The solution provided on Phonak’s website is not realistic.

So what is happening that is causing the Phonak Remote App to default to Autosense every time any audio sound is made on the phone? I will explain using Android, but the same applies to iPhone. In Android if you go to SETTINGS>CONNECTIONS>BLUETOOTH you will see your Phonak connection like in the image displayed.

​
Picture
Tap the TOP setting. The next image shows what you should see. PHONE and AUDIO, one or both sliders may be in the ON position. This is where the POF (Point of Failure) is. The point of the AUDIO slider is to allow ALL audio sounds made by the phone to be played through the hearing aids. This includes all notifications, all of them. People use thousands of different sounds, voices and beeps as notifications. Such a large scale of audio sounds is the POF. The hearing aids are not able to sort out such a large ongoing different amount of audio sounds, so the solution that hearing aids will do is to default to the prescription setting or Autosense. This is something that Phonak can’t fix because Android and iPhone will not allow any developer to access the internal settings of the system notifications or the code of another app. So in order for Phonak to overcome this issue with their code they would need to add code that would be able to sort through all these audio sounds and Android and Apple will not allow that. Each developer of each app is given a “key” to code their app only. So Phonak can’t create code for their app to sort through all the audio sounds.


Picture
Picture
The SOLUTION:
Sadly the only solution is to turn the sliders for Phone and Audio to the off position. Let’s look at this image. Here you see 3 Phonak settings under Bluetooth. The BOTTOM 2 please leave them on. These are for the remote settings to control the volume and custom settings that you will create on the remote app. The BOTTOM 2 are only for SETTINGS from the Phonak remote app to the hearing aids. However the TOP setting, if you tap on it will take you to the sliders for Phone and Audio. These settings allow AUDIO to be transmitted through Bluetooth to the hearing aids. Although you set the controls on the remote app, the changes occur in the hearing aids. As one tech taught me, each hearing aid is a tiny computer. So you control the hearing aids through the Phonak Remote app. With the 2 sliders in the on position for Phone and Audio all sounds made on the cellphone are transmitted to the hearing aids and some of those sounds are forcing the hearing aids to default to Autosense. So the only solution that I have found is to turn both sliders to the off position. This will of course not allow the user to answer calls or play music through the hearing aids.
So a choice has to be made.
  1. To stop the hearing aids from defaulting to Autosense turn off the feature to answer the phone through the hearing aids and hear music.
  2. Leave the feature to answer calls and listen to music through the hearing aids on and put up with the hearing aids defaulting to Autosense every time a notification is played.
  3. Turn off ALL sounds, notifications, tap sounds etc and uninstall any app that will transmit audio through Bluetooth from the phone and it basically becomes a remote for the hearing aids only.
The concept for the Phonak Remote app is great. But due to lockouts on access to certain Operating Systems features in Android and iPhone Phonak will never be allowed to sort through notifications. So unless another way of writing the Phonak code is found, turning off Phone and Audio is currently the only solution.
​
#Phonak #Deaf #Hearingloss #Hearingaids #signlanguage
[Gregory Watts has 5 IT degrees including a CompTIA A+ certification. He got his start in the IT field in 1983 writing computer code.]

The more technically explanation involves describing permissions, interrupt request, obtaining permissions from Android and iPhone and more. When writing this I kept in mind those who would be using the feature and not techs. 

0 Comments

Installing Windows 11 on Older Dell Latitude E6530

12/1/2021

0 Comments

 
Microsoft does not want users to install Windows 11 on older systems, I personally do not believe it has anything to do with Microsoft wanting people to buy a new system, but with security. However many of us have older systems and may want Windows 11. I have Windows 11 installed on my Surface Pro 3 with a 4th Gen Intel, I have a 10th Gen Acer desktop with Windows 11 and I wanted Windows 11 on my Dell Latitude. After much trial and frustration I managed to succeed. My issue turned out to be, the different steps required were posted on different sites. There was no start to finish anywhere. Part of the reason is there are 2 different ways to do it and instead of posting that, only bits and pieces are here and there. I will now post a start to finish for BOTH methods. 
So both methods have similar steps and I will simply repost the steps for each method.
Use the Windows 11 Media Creation Tool to created a USB Drive Boot. Download here


mediacreationtoolw11.exe
File Size: 9760 kb
File Type: exe
Download File

Method #1 a Clean Install.


Step 1: Back up your system, off the system. Back up to an external hard drive or USB drive.
Step 2: Enter the BIOS. On the Dell Latitude restart the system or from a cold start, press the F12 key before for the Dell logo or at the latest when you see the Dell logo. You will see a message that says you are entering ONE TIME BOOT MENU.
Step 3: Once in the BIOS look first for SETTINGS>GENERAL>BOOT SEQUENCE then Enable UEFI (After you do this you WILL NOT be able to boot back into Windows 10, but do not worry. Remember you created a USB key Windows 11 install from the Media Creation Tool before you got this far.
Picture
Step 4: VERY IMPORTANT, no matter what you read elsewhere DO NOT ENABLE SECURE BOOT, if you do you can't boot from the USB drive you made.
Step 5: We now need to enable TPM 1.2. The Dell Latitude does not have TPM 2.0, but Microsoft will allow users to install on systems with TPM 1.2. You simply have to agree to a warning message that also says you may not get updates, but you do get updates. 
Picture
As above DO NOT enable SECURE BOOT.

Step 6: In the image below enable Lagacy Option ROMs to boot from. This will allow the BIOS to load the option to boot from the USB key you created.
Picture
Step 7: This is a 2 screen process in the BIOS but I did not take a shot of the first screen. So find SECURITY>TPM SECURITY the first screen will explain what TPM is and sounds a bit scary but click the box, you can close your eyes if it helps. After you click the box the BIOS will put this screen up (below) leave the 2 boxes checked and only click ACTIVATE. That is it. You are set now set to install Windows 11 on this old Dell. 
Picture
Step 8: Now before restarting take that USB Drive that you made. Remember you used the Windows 11 Media Creation tool, you faithfully followed the instructions and put the Windows 11 install files on that USB Drive? So take that USB Drive you made and plug it into a USB port.
Step 9: Now click EXIT in the BIOS and if asked to SAVE say YES.


The Laptop restarts.
Again press the F12 key at the Dell Logo. It will again enter the ONE TIME BOOT OPTION.
But this time DO NOT enter the BIOS, you will see the option under Legacy Boot to boot to the USB Drive. It may have a different or odd name, but USB will be in the name. Choose that.
Follow the instructions and choose to do a fresh or clean install.
​About 1 hour later you are running Windows 11.

Windows 11 Install on Dell Latitude Option 2

This method is longer and follows much of the same steps above but has extra methods involved. So why post it? Well some people are very scared of messing up their system or may want to go back to Windows 10.
First download the Windows 10 Media Creation Tool and create a Windows 10 USB Install Drive. So choose to save the Windows 10 install files to the USB Drive.


Then follow the steps above, exactly including backing up your laptop. Follow Step 8 above but this time you are reinstalling Windows 10. So why can't you just boot back into Windows 10? When you change the option in BIOS from Legacy boot to UEFI the "file" pointing to the MBR on the Hard Drive has altered. So what was in Legacy BIOS to look for the Windows 10 boot files has been altered, so reinstalling Windows 10 created a new Boot record for UEFI.  

Now once Windows 10 is installed there is a great deal of work from here.
Go to SETTINGS>WINDOWS UPDATE and download ALL Windows 10 updates until you see the update 21H2 installed.

​Now we get to edit the registry. Here is the source for the following information >CLICK HERE<
Press Windows key + R and type in REGEDIT
Then look for and create the following

Warning: 
  • Microsoft recommends against installing Windows 11 on a device that does not meet the Windows 11 minimum system requirements. If you choose to install Windows 11 on a device that does not meet these requirements, and you acknowledge and understand the risks, you can create the following registry key values and bypass the check for TPM 2.0 (at least TPM 1.2 is required) and the CPU family and model.
  • Registry Key: HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup
  • Name: AllowUpgradesWithUnsupportedTPMOrCPU
  • Type: REG_DWORD
  • Value: 1
  • Note: Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
 If you see the above and think WHAT! I suggest you go to method 1 and stop here.
The above registry key change tells the Windows 11 install process to ignore the TPM security check.
You will now need to download the Windows 11 ISO files, they are huge, over 5GB. Click >THIS LINK< to download them.
If you updated to Windows 10 21H2 then you can install from the ISO file from within Windows.
After it has downloaded Double click the ISO file then Double Click SETUP, follow the instructions, it may take more than an hour.
​Thats it.
mediacreationtool21h1.exe
File Size: 19463 kb
File Type: exe
Download File

0 Comments

How to Install Android Subsystem for Windows 11 on Unsupported CPU

10/24/2021

0 Comments

 
The original article can be found >HERE< I am going to copy and paste it here but the author is By Mayank Parmar October 24, 2021.
​

Picture
Android Subsystem for Windows 11 is one of the biggest new features that was originally supposed to come on October 5. It turns out that Microsoft needs more time to test the subsystem and it has started rolling out the feature to Insiders, but a simple trick now lets you sideload Android apps on Windows 11 without joining the beta channel.
Microsoft has confirmed that testers in the United States can download and install Android apps from the Amazon AppStore on Windows 11. However, Android Subsystem for Windows 11 is rolling out in stages, so the Amazon AppStore may not download when the Store app is not updated.
Windows 11’s Android Subsystem is available on eligible devices with Intel, AMD, and Qualcomm processors. Additionally, a minimum of 8GB of RAM is required to sideload Android APKs on Windows 11, while 16GB of RAM is recommended for the best experience on supported devices.

Sideloading APKs on Windows 11Thanks to WSA, we can sideload Android apps on Windows 11 without Google Play Store. It also lets you install and use mobile apps that you can’t find through app stores like Amazon, Google or Samsung.
What’s great about the Android Subsystem for Windows is that it lets you install nearly all Android apps without making changes to device settings. The process is similar to sideloading apps on your phone, but you should be familiar with Command Prompt.
In this guide, we’ll talk about the simplest ways of sideloading apps on Windows 11 using Command Prompt. The method is easy to follow, so let’s take a look at how it works.
How to sideload apps on Windows 11 using Command PromptIf you know the basics of Command Prompt and ADB (Android Debug Bridge), sideloading APKs on your Windows 11 PC can be a piece of cake.
Before getting started, make sure you’ve downloaded APKs for apps you want to install on your device. For this article, we chose to install the Brave browser downloaded from APKMirror.

To sideload Android APKs on Windows 11 using WSA without joining the beta channel, follow these steps:
  1. Download Windows Subsystem for Android from here.
  2. Open PowerShell (admin).
  3. Enter Add-AppxPackage <path to file>
    (To get the path of WSA, right-click on it and select “Copy as path“, and paste it in the above command).
Picture
4.  Head to Google’s website and download the Android SDK Platform-Tools.
5,  Extract Android SDK Platform-Tools to a folder of your choice.
6.  Open Windows Search and type “Windows Subsystem for Android“, and click on it.
7.  Inside “Windows Subsystem for Android”, scroll down and turn on “Developer mode”.
8.  Click on “Files” to get the IP address. This step is required when the IP address is unavailable on the settings page.
Picture
9.  If you still do not see the IP address, click Refresh or reopen the settings.
10. Once done, open Command Prompt.
11. Use cd command to navigate to the folder of Android SDK Platform-Tools. For example, if you extracted the tools in the Downloads folder, you would need to type cd c:\users\username\downloads\platform-tools and press enter.
Picture
12. In the Command Prompt, enter adb connect ipaddress that you copied earlier.
13. To install the APK, use adb install appname.apk. In this case, we’re using brave.apk (brave browser), so we entered the following command: adb install brave.apk
Picture
14. If you followed the steps correctly, a success message will appear in the Command Prompt.

​You will find the app listed in your Start menu and these Android apps can be uninstalled like other apps.
0 Comments

Windows 11 Hacks

9/15/2021

0 Comments

 
Microsoft has gone to amazing lengths on the security to protect Windows 11. In fact that is the reason the systems requirements are so strict, an attempt to prevent hackers from getting any access to the OS or the computer. However I have come across 2 articles thus far where a user pr company has defeated or hacked a form of the Windows 11 security. I will update this article as I discover more. If you have one you would like to submit please reach out to me on About>Contact Us page.

The first "hack" was done by Mozilla Firefox. Microsoft has made setting anything but their apps as default difficult and deep. Mozilla wanted to be able to just allow the user to set the default browser from within the browser. Microsoft has claimed by making it difficult to alter the default apps it prevents hijacking and bad actors from hijacking existing apps or installing their own. So did Mozilla defeat this in Windows 11 before it was released. Read the full store. >
https://www.theverge.com/2021/9/13/22671182/mozilla-default-browser-windows-protections-firefox<   
Picture

Installing Windows 11 Without an Account

Windows 11 Home requires users to use an Internet connection and a Microsoft Account to install. However one user has already defeated this.

"
Neowin forum member warwagon has created a video illustrating how Windows 11 Home users can still create a local account at startup without being forced to use a Microsoft email. When you see the “Let’s connect you to a network” screen, hit Shift-F10, type “taskmgr” in the command prompt window, and kill the process called “Network connection flow.” According to the video, this will allow the OS to install normally after you insert a user login and password. You can also kill the application directly from the command line if you like, using the command “taskkill /F /IM oobenetworkconnectionflow.exe”
0 Comments
<<Previous
Forward>>

    RSS Feed

    Picture

    Author

    DeWayne Watts: I started out writing short stories and poetry. Some of which was published in the 1980's. I have parts of 5 novels written and have completed 2 novels. I have been married over 25 years and raised 2 wonderful sons who have been a great addition to the human family.

    Follow me on GOODREADS
    The 3 Novels/Books Written By DeWayne Watts
    Picture
    Still With Eyes Closed
    Click >Here< To Buy
    Picture
    "David's mark"
    Click Title to Buy the Book.
    Picture
    "The Boy in The Wood"
    Click Title To Buy The Book.
    Picture

    Archives

    December 2022
    November 2022
    October 2022
    September 2022
    June 2022
    December 2021
    October 2021
    September 2021
    August 2021
    July 2021
    May 2021
    March 2021
    November 2020
    July 2020
    June 2020
    March 2020
    February 2020
    October 2019
    September 2019
    July 2019
    June 2019
    April 2019
    March 2019
    February 2019
    November 2018
    October 2018
    September 2018
    August 2018
    July 2017
    November 2016
    October 2016
    September 2016
    July 2016
    May 2016
    March 2016
    February 2016
    January 2016
    December 2015
    November 2015
    September 2015
    August 2015
    May 2015
    March 2015
    February 2015
    January 2015
    December 2014
    November 2014
    October 2014
    September 2014
    August 2014
    July 2014
    June 2014
    May 2014
    April 2014
    March 2014

    Categories

    All

    RSS Feed

Powered by Create your own unique website with customizable templates.