Yet another Windows 11 problem?

Aries

Aries

New Member
In the end I had to make the move from Windows 10 to Windows 11, because the hard drive on the (9 years) old machine was getting a bit unreliable. I moved all the data files across and installed the latest versions of the software, including Picaxe editor. It works - I have managed to update and download a program onto one of my Picaxe projects - but ...
  • If I start Picaxe from the icon (I have a shortcut on the taskbar), then it starts correctly, with the previous workspace loaded and displayed.
  • If I start Picaxe by double-clicking on the workspace name in File Explorer, I get a request to allow an installer app to modify my device. It is the same installer every time - see picture "Installer" - from RevEd. This was my second full installation of Picaxe on this machine. The previous one did exactly the same thing, but with an installer name ending in 80 f bad (make of the abbreviation what you will). It makes no difference whether the AXE027 is plugged in or not.
In addition, it looks as if the AXE027 installation has not completed properly, even though it all seems to work. Looking at the "Events" tab of the properties of the AXE027 in Device Manager under Ports (COM & LPT) I see what is in the picture ("AXE027") -
"Device FTDIBUS\VID_0403+PID_BD90+7&207afd0&0&1\0000 requires further installation."

I can't see any way to do any more installation. The USB controllers section shows AXE027 with a whole lot of "Device configured" messages, but nothing about not being installed properly, and I don't know how or where to find the FDTIBUS\etc device.

Has anyone else hit this and is there a way to cure it? It seems to be no more than an irritation, but I fear there may be someting deeper down that is not as it should be.
 

Attachments

  • AXE027Events.jpg
    AXE027Events.jpg
    34.6 KB · Views: 9
  • Installer14a93.jpg
    Installer14a93.jpg
    37 KB · Views: 9
I think the AXE027 is now supported by Windows Update - so you might be able to delete all traces of the drivers, including 'hidden' ones (via Device Manager) and then just plug the AXE027 in to re-install from Windows Update. There are two bits to the AXE027, so you need to look under "COM Ports" and "Universal Serial Bus Controllers".

I reverted to Picaxe Editor 6.1.0.0 (on Windows 10), because Windows insisted on 'reconfiguring' 6.2.0.0, every time I invoked it. I got bored, trying to find out why!

(I'm sticking with Windows 10, until the support options become too expensive!)
 
PhilHornby said:
I reverted to Picaxe Editor 6.1.0.0 (on Windows 10), because Windows insisted on 'reconfiguring' 6.2.0.0, every time I invoked it. I got bored, trying to find out why!

(I'm sticking with Windows 10, until the support options become too expensive!)
Click to expand...
I've stuck with 6.1.0.0 too - "If it aint broke, don't fix it." And, while I probably will upgrade to Windows 11, I will be among the last to do so.
 
I've been running win 11 (now 24H2 VER) on my 2 laptops and desktop from the beginning with no problems running picaxe programming 6.1 on all machines.

bILL
 
Aries said:
Is it still possible to download it? Although the download directory https://picaxe.com/downloads/pe6100 seems to exist, I don't know what's in it.
Click to expand...

UPDATED

Expanding that URL, there is an installer at: https://picaxe.com/downloads/pe6100/picaxeeditor6.exe but I don't know what version it is (I've not tried installing it). It is different to both the 6.1 and 6.2 installers that I have previously saved locally.

It is 6.1.0.0, but there must be something else different in the installer (different AXE027 driver perhaps).

The "Wayback Machine" archived a version that matches 'my' 6.1 here: https://web.archive.org/web/20210306162318/https://picaxe.com/downloads/pe6100/picaxeeditor6.exe
 
Last edited:
Sidestepping a bit here to ask if your old WIn10 HD is in good enough shape to copy to another HDD. since that prompted your move to Windows 11. I recently used a free 30-day trial of Macrium Reflect to copy several drives and it worked perfectly. https://www.macrium.com/reflectfree Copy/image an old drive to a blank one that's the same size or larger. You can also select and create various partitions but I didn't need that. One option if you have a dozen spare computers laying about like the rest of us. It can't be just me...?

I had a smooth transition to Windows 11 but I don't use aa AXE027 cable. I make my own cables using CP2012/CH340 adapters and the inverter mod here (SHOUTOUT TO GOEYTEX!). IIRC neither USB driver (CP210x or CH340) claimed Windows 11 compatibility but worked fine.

Worked fine...
Worked fine...
Worked fi.... ... ... ... ... :)
 
I've used the free DiskGenius to migrate Windows 10 with no problems. Don't plan to use Win 11 until forced to, but I have a copy of Linux Mint waiting to be installed and that might be my next OS. Just need to spend a few days exploring its features and "gotcha's".

How to Migrate Windows Operating System to an SSD/HDD? [FREE]

Want to migrate Windows from HDD to a new SSD? This guide shows how to transfer Windows 11/10 to an SSD or HDD with the help of a free Windows migration tool DiskGenius.
www.diskgenius.com
 
I tested on both Win 10 and Win 11, and both PE 6.1.0.0. and PE 6.2.0.0 versions. The issue indicated by the topic starter (2nd bullet point) is related to PE 6.2.0.0. specifically, not the Windows version (and I actually strongly prefer W11 over W10, but that's another topic).
Technical, could you address this in 6.2.0.0? Indeed it is annoying that double-clicking on a Picaxe BAS file opens the installer first every time.
 
Last edited:
There is no difference at all between the installer process for those PE6 versions (i.e. same msi format / same installshield version) or within PE6 as to regards to double clicking on a file. The later installer does however use a more modern security signing method, as now required by Microsoft for all installers.

If double clicking on a .bas file calls up the installer then PE6 hasn't even started at that point, so it is normally a Windows system setup issue with not finding the associated resource for that file type (e.g. if PE6 has been installed for a single user rather than 'all users').
 
Thanks for the quick response!
Well, the version has been installed for 'all users' but the issue remains - even if the PE is already open because it will try to open a new PE instance anyway (and single user install does not even work). Not a blocker, but annoying, as Aries and Phil have also expressed. I went back to 6.1.0.0. for the moment.
 
Last edited:
I use PE6 on Tiny10(reluctantly), since it's not available for Linux. I prefer the full PE6 to the cut down Axepad. However, I'd still rather PE worked on Linux.
 
twanglpop said:
I use PE6 on Tiny10(reluctantly), since it's not available for Linux. I prefer the full PE6 to the cut down Axepad. However, I'd still rather PE worked on Linux.
Click to expand...
Why not run it under WINE on Linux? That's been working just fine for me for years.
 
You must log in or register to reply here.
Back
Top