I like that idea. I did replace the screen on a phone once. Maybe there is something on youtube that will show me how to remove those parts.
Thanks.
Topic: Upgrade problems from legacy version of Electrum. Coins stuck on WinXP PC wallet (Read 723 times)
January 05, 2021, 11:00:03 PM
January 05, 2021, 06:18:03 PM
I might go with using a non-activated android phone. I don't really like this though because it seem like they are always trying to connect to some kind of network.
Well, I have an Android phone Samsung note 2 which is old I recently removed the wifi/Bluetooth IC module directly from the board to make sure it won't connect to any wifi network and only use it for airgap wallet.
If you want to do the same I think you can do the same but you need a phone tech and tell them to remove those ICs. Now I'm using it as my airgap wallet with a clear camera for scanning QR codes and singing transactions.
January 05, 2021, 05:06:56 PM
It is a PIII 850 with 384M Ram.
What I found is that any OS that will run on it, will not have a version of python which works with the current release of Electrum.
I might go with using a non-activated android phone. I don't really like this though because it seem like they are always trying to connect to some kind of network.
What I found is that any OS that will run on it, will not have a version of python which works with the current release of Electrum.
I might go with using a non-activated android phone. I don't really like this though because it seem like they are always trying to connect to some kind of network.
January 05, 2021, 03:10:32 PM
Unfortunately, getting it running on that old hardware is not going to be a simple "point and click" type task... Granted there are still Linux distros out there catering to "old hardware", but they usually involve an amount of customisation to run on CPUs missing certain "modern" features and instruction sets (PAE, SSE3 etc).
Without knowing the exact specs of what you're running... ie. the exact CPU/mobo model and the amount of RAM we're working with, it's difficult to make a specific recommendation on which linux distro you should try (and how to configure it).
Alternatively, the "easy but more expensive" option is to simply buy updated hardware
Without knowing the exact specs of what you're running... ie. the exact CPU/mobo model and the amount of RAM we're working with, it's difficult to make a specific recommendation on which linux distro you should try (and how to configure it).
Alternatively, the "easy but more expensive" option is to simply buy updated hardware
January 05, 2021, 12:21:44 PM
I think people are steering me in the wrong direction. My question was about how to get an Electrum offline wallet running again on a very old desktop. Most of the advice is ignoring my hardware and assuming this is a newer PC. I think I am forced to upgrade now.
Thanks.
Thanks.
January 05, 2021, 11:17:35 AM
Electrum is actually 32 bit and can run on both 32 and 64 bit operating systems. You should make sure that the Linux distribution that you are installing is a 32 bit version because you can't install it otherwise.
Which download are you speaking about? The Linux version located at: https://download.electrum.org/4.0.9/electrum-4.0.9-x86_64.AppImage is a 64 bit executable.The Windows binary can be run on a 32 bit system.
And on linux, you could simply use python to run it on a 32 bit system. You don't need to use the .AppImage file, given that python3.6+ is installed.
January 05, 2021, 11:06:24 AM
Electrum is actually 32 bit and can run on both 32 and 64 bit operating systems. You should make sure that the Linux distribution that you are installing is a 32 bit version because you can't install it otherwise.
Which download are you speaking about? The Linux version located at: https://download.electrum.org/4.0.9/electrum-4.0.9-x86_64.AppImage is a 64 bit executable.
January 04, 2021, 11:48:12 PM
I tried Ubuntu 16.4, Lubuntu 18.4 & 16.4, a few versions of puppy.
I don't feel it matters though. I think the idea was doomed to fail from the start. I see that the Linux build of Electrum is for 64bit. My hardware is 32bit.
Electrum is actually 32 bit and can run on both 32 and 64 bit operating systems. You should make sure that the Linux distribution that you are installing is a 32 bit version because you can't install it otherwise. I don't feel it matters though. I think the idea was doomed to fail from the start. I see that the Linux build of Electrum is for 64bit. My hardware is 32bit.
January 04, 2021, 09:25:49 PM
OK. Tried it. Kernal panic.
It does not matter, but I am pretty sure I will have problems with a 64 bit on a 32 bit os anyway.
It does not matter, but I am pretty sure I will have problems with a 64 bit on a 32 bit os anyway.
January 04, 2021, 08:11:36 PM
I saw it, but I did not try that OS. I will give it a try.
But, How were you able to get the 64 bit electrum to run on a 32 bit OS?
But, How were you able to get the 64 bit electrum to run on a 32 bit OS?
January 04, 2021, 04:18:17 PM
I tried Ubuntu 16.4, Lubuntu 18.4 & 16.4, a few versions of puppy.
I don't feel it matters though. I think the idea was doomed to fail from the start. I see that the Linux build of Electrum is for 64bit. My hardware is 32bit.
Maybe you didn't see my post above? I use LXLE 32-bit, it's a very light system and the latest Electrum installs on it without problems and works fine.I don't feel it matters though. I think the idea was doomed to fail from the start. I see that the Linux build of Electrum is for 64bit. My hardware is 32bit.
https://lxle.net/
It should...with a few issues
There is no need for all this. It's more convenient and reliable to work with QR codes. 
January 04, 2021, 12:55:47 PM
Hey guys,
I just noticed that the documentation suggests that I could use an android phone to sign the transactions. I am sure I have an old phone around here that I could factory reset and leave in airplane mode. That might be a good solution. Does anyone know if the Android version will work in this fashion? (Completely off line.)
Thanks,
James.
I just noticed that the documentation suggests that I could use an android phone to sign the transactions. I am sure I have an old phone around here that I could factory reset and leave in airplane mode. That might be a good solution. Does anyone know if the Android version will work in this fashion? (Completely off line.)
Thanks,
James.
It should...with a few issues:
1) You will have to get an OTG cable so you can plug a USB drive into the phone.
2) Not all phones allow this.
3) On the ones that do not all of them like all USB drives some do not put out enough power to actually run them.
4) Now does your phone see the files on the stick and allow you to read / write to it?
I don't know where you are in the world or what your budget is, but you can get a cheap ($50 or less) Win 7 laptop that you can update to Win 10 in most places.
-Dave
January 04, 2021, 12:48:30 PM
Hey guys,
I just noticed that the documentation suggests that I could use an android phone to sign the transactions. I am sure I have an old phone around here that I could factory reset and leave in airplane mode. That might be a good solution. Does anyone know if the Android version will work in this fashion? (Completely off line.)
Thanks,
James.
I just noticed that the documentation suggests that I could use an android phone to sign the transactions. I am sure I have an old phone around here that I could factory reset and leave in airplane mode. That might be a good solution. Does anyone know if the Android version will work in this fashion? (Completely off line.)
Thanks,
James.
January 04, 2021, 11:49:17 AM
I tried Ubuntu 16.4, Lubuntu 18.4 & 16.4, a few versions of puppy.
I don't feel it matters though. I think the idea was doomed to fail from the start. I see that the Linux build of Electrum is for 64bit. My hardware is 32bit.
I am thinking about creating a Linux VM to run inside of Windows 10. Then keep my signing wallet inside that VM and only mount that VM when the laptop is not connect to WIFI. It is not exactly a cold wallet, but I think it gives me a little more security.
I don't feel it matters though. I think the idea was doomed to fail from the start. I see that the Linux build of Electrum is for 64bit. My hardware is 32bit.
I am thinking about creating a Linux VM to run inside of Windows 10. Then keep my signing wallet inside that VM and only mount that VM when the laptop is not connect to WIFI. It is not exactly a cold wallet, but I think it gives me a little more security.
January 03, 2021, 06:55:11 PM
Thank you Bob, maybe you missed the first part of the thread. I have a 20yo Pentium with XP that I was using as an offline cold wallet to sign transactions created with my online laptop. It is the only thing I was using that PC for. The most recent version of Electrum does not work on XP. There are legacy versions of Electrum which work on XP, but all of them are too old to connect to any server nodes.
The suggestion was to install Linux on the box. The bios only supports boot up from DVD, floppys or HD. I needed a DVD burner to create an installation disk. I wanted a DVD burner anyway. I have a bunch tvs and dvd players. I also have a couple hundred movie iso files. I wanted to be able to burn movies again too.
So my burner arrived and I gave it a shot, but no success. I tried about 5 varieties of Linux which claimed to be able to run on my hardware. All seem to start ok and show some kind of splash screen, but eventually all would hang and display a plain black screen.
I guess I will need to spend money on something else.
Thanks for all the help.
The suggestion was to install Linux on the box. The bios only supports boot up from DVD, floppys or HD. I needed a DVD burner to create an installation disk. I wanted a DVD burner anyway. I have a bunch tvs and dvd players. I also have a couple hundred movie iso files. I wanted to be able to burn movies again too.
So my burner arrived and I gave it a shot, but no success. I tried about 5 varieties of Linux which claimed to be able to run on my hardware. All seem to start ok and show some kind of splash screen, but eventually all would hang and display a plain black screen.
I guess I will need to spend money on something else.
Thanks for all the help.
December 31, 2020, 08:59:52 PM
You don't need to burn disks to run a live linux distro.
Nowadays, we use USB flash drives. They are reusable, smaller and more handy. And they even can store more than 4GB already!
Which would be a great idea, except his hardware doesn't support booting from USB... Nowadays, we use USB flash drives. They are reusable, smaller and more handy. And they even can store more than 4GB already!
As an aside, I decided that I am going to configure my old Win XP, to be a duel boot with ubuntu. Sadly, the hardware does not support boot from USB and I don't own a DVD burner. So I ordered a cheap one off of ebay and will have to try to install the os after that arrives.
It still doesn't cease to amaze me the lengths people will go to, to keep old hardware ticking along... There is a point where it's just easier (and often cheaper) to simply purchase something a bit more modern
December 31, 2020, 12:48:30 PM
I am still waiting for my DVD burner to arrive. Once that gets here I will try to update my legacy hardware with ubuntu and let you know if I get my offline wallet working again.
Windows XP, DVD burner, ... which century are you from?
You don't need to burn disks to run a live linux distro.
Nowadays, we use USB flash drives. They are reusable, smaller and more handy. And they even can store more than 4GB already!
December 30, 2020, 03:42:09 PM
Ah.. I got it now. I agree. The transaction always comes first and then that tells you the quantity of input and output maps that follow.
I might have considered making the key values unique across all scopes to eliminate the possibility of confusion.
I think all my questions are answered. Thank you. It is a very good discussion.
I am on the lookout for a web based utility that will accept an uploaded psbt file and return a json representation of the transaction. Please let me know if you are aware of one.
I am still waiting for my DVD burner to arrive. Once that gets here I will try to update my legacy hardware with ubuntu and let you know if I get my offline wallet working again.
Kind Regards,
James.
I might have considered making the key values unique across all scopes to eliminate the possibility of confusion.
I think all my questions are answered. Thank you. It is a very good discussion.
I am on the lookout for a web based utility that will accept an uploaded psbt file and return a json representation of the transaction. Please let me know if you are aware of one.
I am still waiting for my DVD burner to arrive. Once that gets here I will try to update my legacy hardware with ubuntu and let you know if I get my offline wallet working again.
Kind Regards,
James.
December 30, 2020, 01:53:51 PM
I apologize for letting this go way beyond the scope of my original question. But, I am intrigued by this and I want to learn more.
I feel ya... it's why I've been delving into these PSBTs and trying to decode them by hand in a text editor Quote
I completely understand your response. 2 inputs = 2 maps, 2 outputs = 2 maps. But, you created the transaction and know what to expect. How does a person, or algorithm decode this if they have no prior knowledge of the transaction.
All PSBT's must contain the unsigned transaction as part of the global map, which comes first. So, my "theory" is that you need to decode that transaction to identify the number of inputs/outputs involved. That then allows you to "assume" what the following maps are going to be, knowing that the order is: "Global - Inputs - Outputs"Quote
My confusion is with the data types that duplicate the values from the other scope.
Scope Type Values Name BIP Number
Input 0 PSBT_IN_NON_WITNESS_UTXO BIP 174
Input 1 PSBT_IN_WITNESS_UTXO BIP 174
Input 2 PSBT_IN_PARTIAL_SIG BIP 174
Output 0 PSBT_OUT_REDEEM_SCRIPT BIP 174
Output 1 PSBT_OUT_WITNESS_SCRIPT BIP 174
Output 2 PSBT_OUT_BIP32_DERIVATION BIP 174
Do I need to also look at the format of the data to determine which scope it belongs to? Or, am I guaranteed that each map will contain at least one data type value which is unique across both Input and Output and I can use that to determine which scope the map belongs to?
Yeah, I know what you mean... it's weird seeing the same "Type" value for both Inputs and Outputs and trying to determine which one it is... that confused the hell out of me until I figured out that the unsigned transaction must be included and must be the first item. Scope Type Values Name BIP Number
Input 0 PSBT_IN_NON_WITNESS_UTXO BIP 174
Input 1 PSBT_IN_WITNESS_UTXO BIP 174
Input 2 PSBT_IN_PARTIAL_SIG BIP 174
Output 0 PSBT_OUT_REDEEM_SCRIPT BIP 174
Output 1 PSBT_OUT_WITNESS_SCRIPT BIP 174
Output 2 PSBT_OUT_BIP32_DERIVATION BIP 174
Do I need to also look at the format of the data to determine which scope it belongs to? Or, am I guaranteed that each map will contain at least one data type value which is unique across both Input and Output and I can use that to determine which scope the map belongs to?
So you can derive the number of inputs/outputs from that unsigned tx and then process the rest of the maps.
December 30, 2020, 09:52:31 AM
Thank you HCP,
I apologize for letting this go way beyond the scope of my original question. But, I am intrigued by this and I want to learn more.
I completely understand your response. 2 inputs = 2 maps, 2 outputs = 2 maps. But, you created the transaction and know what to expect. How does a person, or algorithm decode this if they have no prior knowledge of the transaction.
My confusion is with the data types that duplicate the values from the other scope.
Scope Type Values Name BIP Number
Input 0 PSBT_IN_NON_WITNESS_UTXO BIP 174
Input 1 PSBT_IN_WITNESS_UTXO BIP 174
Input 2 PSBT_IN_PARTIAL_SIG BIP 174
Output 0 PSBT_OUT_REDEEM_SCRIPT BIP 174
Output 1 PSBT_OUT_WITNESS_SCRIPT BIP 174
Output 2 PSBT_OUT_BIP32_DERIVATION BIP 174
Do I need to also look at the format of the data to determine which scope it belongs to? Or, am I guaranteed that each map will contain at least one data type value which is unique across both Input and Output and I can use that to determine which scope the map belongs to?
I apologize for letting this go way beyond the scope of my original question. But, I am intrigued by this and I want to learn more.
I completely understand your response. 2 inputs = 2 maps, 2 outputs = 2 maps. But, you created the transaction and know what to expect. How does a person, or algorithm decode this if they have no prior knowledge of the transaction.
My confusion is with the data types that duplicate the values from the other scope.
Scope Type Values Name BIP Number
Input 0 PSBT_IN_NON_WITNESS_UTXO BIP 174
Input 1 PSBT_IN_WITNESS_UTXO BIP 174
Input 2 PSBT_IN_PARTIAL_SIG BIP 174
Output 0 PSBT_OUT_REDEEM_SCRIPT BIP 174
Output 1 PSBT_OUT_WITNESS_SCRIPT BIP 174
Output 2 PSBT_OUT_BIP32_DERIVATION BIP 174
Do I need to also look at the format of the data to determine which scope it belongs to? Or, am I guaranteed that each map will contain at least one data type value which is unique across both Input and Output and I can use that to determine which scope the map belongs to?
Jump to: