Your problem with software is mine, but I found a way to get over it. Most Unix based

OS's use text files to configure and start up the machine. Indeed there is something

called Linux From Scratch (LFS):

http://www.linuxfromscratch.org/

It will take you by the hand and show you how to build your own OS, and in the process

you will learn how the innards work. Since the config files are text you will learn how to

follow them and see exactly how the system boots up and manages the whole thing.

In my view Windows is like a car with the hood welded shut.

Unix based systems for the most part are like a car that provides all of the documentation

to dig into the vehicle and fix it your self.

Even Apple Macs are in my view easier to work on than Windows because of the BSD

based OS. I can go in and follow what the machine is doing, at least until it gets into

the GUI, there it gets a bit hermetic, but still more open than Windows.

LFS is all on line so you can go in and follow it, repeat the parts you do not understand

and see the results as you go through it.

Take a look at it, I think it will help you gain a better idea of what is going on. Even for

the MS environments, they all have to do certain things about the same on any given

piece of hardware, it is just that with Linux you can go in and see how it is done then

use that to have an idea of what MS is doing with Windows.

On Mon, Jun 18, 2018 at 7:26 AM <mike-2007@elp.rr.com> wrote:

I feel bad for people like this, because I am one of them. I have no
problem at all digging into an electronics circuit. Shoot, I'm certified to
run the power grid, so electronics/electrical doesn't scare me a bit. I
have no problem laying out under my JEEP for days with a pile of tools
modifying the suspension or working on something I broke. But software is
magical. I can't wrap my head around how it works, so when it doesn't work
it is frustrating to the max. And when it doesn't work, I need like
step-by-step 1-2-3-4-5 directions or I likely cannot fix it. This is why
I'm willing to pay for the more expensive but totally reliable cables. I
feel certain if I have a problem, the cables are eliminated.

We all have skills, and we all have challenges. You folks who jump in and
try to help others, you're great! Thanks for trying, sometimes even when
the frustration level on the other end is running high.

Speaking of running the power grid, I'm out the door. Training today and
tomorrow. Running the generation desk Thu-Fri. Everyone - have a safe day!
And if you're on the Western Grid, we'll be doing our best to keep it steady
at 60 Hz.

Vy73 - Mike - KD5KC
El Paso, Texas - DM61rt

-----Original Message-----
From: chirp_users-bounces@intrepid.danplanet.com
<chirp_users-bounces@intrepid.danplanet.com> On Behalf Of Tom Henderson
Sent: Monday, June 18, 2018 5:13 AM
To: chirp_users@intrepid.danplanet.com
Subject: Re: [chirp_users] CHIPRP AND TYT TH-9800

Aha! Thanks for setting the record straight then.

Tom Henderson

On 06/18/2018 04:59 AM, Jim Unroe wrote:
> On Mon, Jun 18, 2018 at 5:45 AM, Tom Henderson <Tom@henderson4.us> wrote:
>> It's the same fix for windows. The only difference is those of us who
>> run it in linux don't know where it's stored under the windows version.
>>
>> Did you see the line that says "Not sure where it is in Windows, so
>> just search for it?"
>>
>> Tom Henderson
>>
> It isn't the same for Windows. The user doesn't have access to the
> individual *.py files with Windows. As far as I know, the best a
> Windows user can do is to download the th9800.py driver from the CHIRP
> repository, edit it as needed, then after enabling "Enable developer
> functions" load the modified driver using File -> Load module
> selection. And this custom driver would have to be loaded every time
> CHIRP was launched.
>
> Jim KC9HI
> _______________________________________________
> chirp_users mailing list
> chirp_users@intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Tom KM4UQB at tom@henderson4.us To
> unsubscribe, send an email to
> chirp_users-unsubscribe@intrepid.danplanet.com
>

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to mike-2007@elp.rr.com at mike-2007@elp.rr.com To
unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Chuck Hast at kp4djt@gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com