On Oct 21, 2023, at 4:49 AM, D.J.J. Ring, Jr. <n1ea@arrl.net> wrote:<Windows Snips.odt>_______________________________________________Gene the OP sent this file (attached) showing he is running a 64 bit processor AMD Ryzen 5 2500U with 16 GB RAM 64 bit OS, x64 processor. Running Windows 10 Home version 22H2.He's tried the latest CHIRP-Next and one of the legacy CHIRP versions, and he cannot get past the license agreement, he answers that he agrees to the terms, but the installer seems to dissappear and CHIRP is never installed.I've suggested to him and sent him a tutorial to make a Live version of Ubuntu Long Term Support (LTS) with persistence and then install CHIRP in it.I've also told him that his Windows installation is messed up and perhaps will need a reinstall of his Windows 10 Home.I'm suggesting to him now additionally that it's possible or problem with RAM failure as I have had several similar issues that finally were found to be RAM failure. I ran RAM tests in the full expanded version from one of the Live Linux iso on a USB STICK made with Rufus. I replaced the RAM and I had no more issues with installation errors.I would like to suggest to anyone who has the knowledge that I lack and suggest that the CHIRP developers produce a version of a Puppy Linux with the latest version of Chirp-Next and upload it to Sourceforge.net as an update to what Sourceforge.net user bgiff158 did years ago for Legacy CHIRP.73DRN1EA---------- Forwarded message ---------
From: Gene <jedi1.gh@gmail.com>
Date: Fri, Oct 20, 2023, 5:33 PM
Subject: Re: [chirp_users] Chirp will not install
To: Dan Smith via chirp_users <chirp_users@intrepid.danplanet.com>I have attached my system information. Don't know what else is needed._______________________________________________On 10/20/2023 5:05:59 PM, D.J.J. Ring, Jr. <n1ea@arrl.net> wrote:
No, Marc, it's not necessicarily a PC issue. We don't know yet, because when he responds he has yet to give us the Type of Windows 10 he is running.I've asked him several times, he will get the emails eventually.He needs to tell us the Windows System type.Gene, this page tells you how to find your System type: https://www.howtogeek.com/697170/5-ways-to-quickly-open-the-system-window-on-windows-10/Or shortcut key is the Windows key then the SysRQ/Pause key - which is the third key to the right of F12 on standard keyboard.Copy the Device Specifications - there is a button to do this.Mine is:Device name DESKTOP-G62MJMS
Processor Intel(R) Celeron(R) N5105 @ 2.00GHz 2.00 GHz
Installed RAM 16.0 GB (15.8 GB usable)
Device ID AD3CA7D7-8EEE-44F8-A7DC-96906CC32031
Product ID 00355-60787-89786-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this displayThere's also a button for Windows Specifications. Mine is:Edition Windows 11 Pro
Version 22H2
Installed on 5/17/2023
OS build 22621.2428
Experience Windows Feature Experience Pack 1000.22674.1000.0Send them back to the list please.73DRN1EA_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Gene at jedi1.gh@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.comOn Fri, Oct 20, 2023 at 3:53 PM Marc <marcptramontana@gmail.com> wrote:Thanks for clarifying this info. So if this is true, the installer should not be crashing midway or early on through the install. So he is having a PC issue. Most likely antivirus or malware.Marc_______________________________________________On Fri, Oct 20, 2023 at 3:37 PM Nigel A. Gunn G8IFF/W8IFF <nigel@ngunn.net> wrote:It's not the processor type that's the problem. It's the OS version.
> On 20/10/2023 15:33 EDT Roger Jane via chirp_users <chirp_users@intrepid.danplanet.com> wrote:
>
>
> Could the 64 bit installer be compiled as 32 bit then warn the user, politely 🙂, that it can’t continue and why when it checks the processor type?
>
ngunn.net
_______________________________________________
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to Marc T. at marcptramontana@gmail.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com
Searchable archive: https://www.mail-archive.com/chirp_users@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 D.J.J. Ring, Jr. at n1ea@arrl.net
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com
Searchable archive: https://www.mail-archive.com/chirp_users@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 D.J.J. Ring, Jr. at n1ea@arrl.net
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com
Searchable archive: https://www.mail-archive.com/chirp_users@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 Eric Oyen at eric.oyen@icloud.com
To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com
Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
