Activity for ThaCrip
-
ThaCrip modified a comment on discussion Help
I am currently using Linux Mint 21.2-Xfce and I suggest using the 'standard way' to install Password Safe instead of Flatpak which are bloated/non-standard (in my opinion it's best to use standard installs unless one has no other choice to use Flatpak). to install the standard way you would simply issue the following from terminal... apt install passwordsafe while that will basically work, it will be a older version (I forgot exactly which version) but you can download the ".deb" file to install...
-
I am currently using Linux Mint 21.2-Xfce and I suggest using the 'standard way' to install Password Safe instead of Flatpak which are bloated/non-standard (in my opinion it's best to use standard installs unless one has no other choice to use Flatpak). to install the standard way you would simply issue the following from terminal... apt install passwordsafe while that will basically work, it will be a older version (I forgot exactly which version) but you can download the ".deb" file to install...
-
I noticed on your 'changelog' it showed... "Memtest86+ was updated to v6.00. Thanks to Lord65 for suggesting this." I just thought I would make a post saying v6.10 was released Feb 3rd 2023. so it's probably worth including that version now in future Clonezilla versions.
-
I finally got around to using 'clonezilla-live-3.0.1-7-amd64.iso' on my primary PC with the i5-3550 CPU and on my boot SSD (Samsung 850 EVO 250GB) to a image file on a 2TB hard drive and it did 9.63GB/min average (at it's peak during the imaging process it was a bit over 10GB/min). previously with that same general setup it was about 7.00GB/min, possibly a bit less in the mid-to-high 6's.
-
I finally got around to using 'clonezilla-live-3.0.1-7-amd64.iso' on my primary PC with the i5-3550 CPU and on my boot SSD (Samsung 850 EVO 250GB) to a image file on a 2TB hard drive and it did 9.63GB/min. previously with that same general setup it was about 7.00GB/min, possibly a bit less in the mid-to-high 6's.
-
I finally got around to using 'clonezilla-live-3.0.1-7-amd64.iso' on my primary PC with the i5-3550 CPU and on my boot SSD (Samsung 850 EVO 250GB) to a 2TB hard drive and it did 9.63GB/min. previously with that same general setup it was about 7.00GB/min, possibly a bit less in the mid-to-high 6's.
-
I finally got around to using 'clonezilla-live-3.0.1-7-amd64.iso' on my primary PC with the i5-3550 CPU and on my boot SSD (Samsung 850 EVO 250GB) it did 9.63GB/min. previously it was about 7.00GB/min, possibly a bit less in the mid-to-high 6's.
-
A easier way... I suggest creating a multi-boot USB stick (I use Ventoy on Linux but it's apparently for Windows to). this way you can just download the Clonezilla ISO and then put your Linux/Windows ISO's on there to and boot to the USB stick and select which ISO you want to load up.
-
Since I am currently using my i5-3550 setup, I thought I would do some testing on my backup computer, which is a... AMD Athlon X2 3600+ (socket 939) dual-core CPU overclocked from 2.0GHz to 2.3GHz (which is pretty much mid-to-late 2000's tech (I had the basic board since March 2006) as it's a high end board in it's day... ASUS A8N32-SLI Deluxe) imaging a 250GB SATA HDD (Clonezilla shows it as 16GB of data, which is my Linux Mint v20.3-Xfce installation) to a image file on a 80GB IDE hard drive and,...
-
Since I am currently using my i5-3550 setup, I thought I would do some testing on my backup computer, which is a... AMD Athlon X2 3600+ (socket 939) dual-core CPU overclocked from 2.0GHz to 2.3GHz (which is pretty much mid-to-late 2000's tech (I had the basic board since March 2006) as it's a high end board in it's day... ASUS A8N32-SLI Deluxe) imaging a 250GB SATA HDD (Clonezilla shows it as 16GB of data, which is my Linux Mint v20.3-Xfce installation) to a image file on a 80GB IDE hard drive and,...
-
Since I am currently using my i5-3550 setup, I thought I would do some testing on my backup computer, which is a... AMD Athlon X2 3600+ (socket 939) dual-core CPU overclocked from 2.0GHz to 2.3GHz (which is pretty much mid-to-late 2000's tech (I had the basic board since March 2006) as it's a high end board in it's day... ASUS A8N32-SLI Deluxe) imaging a 250GB SATA HDD (Clonezilla shows it as 16GB of data, which is my Linux Mint v20.3-Xfce installation) to a image file on a 80GB IDE hard drive and,...
-
Since I am currently using my i5-3550 setup, I thought I would do some testing on my backup computer, which is a... AMD Athlon X2 3600+ (socket 939) dual-core CPU overclocked from 2.0GHz to 2.3GHz (which is pretty much mid-to-late 2000's tech (I had the basic board since March 2006) as it's a high end board in it's day... ASUS A8N32-SLI Deluxe) imaging a 250GB SATA HDD (Clonezilla shows it as 16GB of data, which is my Linux Mint v20.3-Xfce installation) to a 80GB IDE hard drive and, in short, the...
-
Since I am currently using my i5-3550 setup, I thought I would do some testing on my backup computer, which is a... AMD Athlon X2 3600+ (socket 939) dual-core CPU overclocked from 2.0GHz to 2.3GHz (which is pretty much mid-to-late 2000's tech (I had the basic board in March 2006) as it's a high end board in it's day... ASUS A8N32-SLI Deluxe) imaging a 250GB SATA HDD (Clonezilla shows it as 16GB of data, which is my Linux Mint v20.3-Xfce installation) to a 80GB IDE hard drive and, in short, the new...
-
Since I am currently using my i5-3550 setup, I thought I would do some testing on my backup computer, which is a... AMD Athlon X2 3600+ (socket 939) dual-core CPU overclocked from 2.0GHz to 2.3GHz (which is pretty much mid-to-late 2000's tech as it's a high end board in it's day... ASUS A8N32-SLI Deluxe) imaging a 250GB SATA HDD (Clonezilla shows it as 16GB of data, which is my Linux Mint v20.3-Xfce installation) to a 80GB IDE hard drive and, in short, the new version is a bit faster as you can see...
-
Since I am currently using my i5-3550 setup, I thought I would do some testing on my backup computer, which is a... AMD Athlon X2 3600+ (socket 939) dual-core CPU overclocked from 2.0GHz to 2.3GHz (which is pretty much mid-to-late 2000's tech as it was on a high end board in it's day... ASUS A8N32-SLI Deluxe) imaging a 250GB SATA HDD (Clonezilla shows it as 16GB of data, which is my Linux Mint v20.3-Xfce installation) to a 80GB IDE hard drive and, in short, the new version is a bit faster as you...
-
Since I am currently using my i5-3550 setup, I thought I would do some testing on my backup computer, which is a... AMD Athlon X2 3600+ (socket 939) dual-core CPU overclocked from 2.0GHz to 2.3GHz (which is pretty much mid-to-late 2000's tech as it was on a high end board in it's day... ASUS A8N32-SLI Deluxe) imaging a 250GB SATA HDD (Clonezilla shows it as 16GB of data, which is my Linux Mint v20.3-Xfce installation) to a 80GB IDE hard drive and, in short, the new version is a bit faster as you...
-
Since I am currently using my i5-3550 setup, I thought I would do some testing on my backup computer, which is a... AMD Athlon X2 3600+ (socket 939) dual-core CPU @ 2.3GHz (which is pretty much mid-to-late 2000's tech as it was on a high end board in it's day... ASUS A8N32-SLI Deluxe) imaging a 250GB SATA HDD (Clonezilla shows it as 16GB of data, which is my Linux Mint v20.3-Xfce installation) to a 80GB IDE hard drive and, in short, the new version is a bit faster as you can see results below......
-
I also noticed issues as it takes a lot longer to finish... -clonezilla-live-3.0.0-26-amd64.iso = about 1.60GB/min (which is slow as previous "clonezilla-live-2.8.1-12-amd64.iso" worked as expected, which is in the general 7.00GB/min range give or take) -clonezilla-live-20220522-jammy-amd64.iso = about 7.00GB/min (which is expected) which ads a lot of time to imaging. but it appears the next version should fix this issue given what's said above. p.s. I use a i5-3550 CPU and basically a 2TB Hitachi...
-
I also noticed issues as it takes a lot longer to finish... -clonezilla-live-3.0.0-26-amd64.iso = about 1.60GB/min (which is way to slow as previous "clonezilla-live-2.8.1-12-amd64.iso" worked as expected, which is in the general 7.00GB/min range give or take) -clonezilla-live-20220522-jammy-amd64.iso = about 7.00GB/min (which is expected) which ads a lot of time to imaging. but it appears the next version should fix this issue given what's said above. p.s. I use a i5-3550 CPU and basically a 2TB...
-
I also noticed issues as it takes a lot longer to finish... -clonezilla-live-3.0.0-26-amd64.iso = about 1.60GB/min (which is way to slow as previous "clonezilla-live-2.8.1-12-amd64.iso" worked as expected, which is in the general 7.00GB/min range give or take) -clonezilla-live-20220522-jammy-amd64.iso = about 7.00GB/min (which is expected) which ads a lot of time to imaging. but it appears the next version should fix this issue given what's said above. p.s. I use a i5-3550 CPU and basically a 2TB...
-
I am using Linux Mint v20.2-Cinnamon along with "passwordsafe-linuxmint20-1.14-amd64.deb". It would seem like behavior would be different, especially when the 'tray icon' is active. because by default, which has no 'system tray' icon, I can sort of see why things behave like they do (which behavior seems to be mostly okay (although only way to close out of the locked Password Safe program is to right click the password safe icon in the taskbar and select 'close' (which seems a bit odd, since that's...
-
I don't really get your point about needing to drag text from the browser into the Password Safe program since you generally go from Password Safe to the browser. because any passwords I use, I always generate from Password Safe itself and then go into the browser. even on the occasion ill store text from the browser into the Password Safe program, one can just copy the text from the browser and paste it into the Password Safe program wherever you want to. I always use the copy/paste (i.e. copy from...
-
Yeah, I was playing with it a bit in virtual machine and seems to use your gpg verification (like "C887 6BE6 9A8E C641 4C8C 8729 B131 423D 7F2F 1BB9") to verify when installing, so that helps it a bit. but I get what your saying in that it appears legit now, but since that person is not tied to the official Password Safe project, theres no guarantee that person would not do something shady down the road etc even though chances are it will be okay, but you just can't be too sure since instead of coming...
-
Just some thoughts in relation to services like Dropbox... personally I am not a fan of uploading sensitive files like Password Safe's database file online, since it just increases the risk of being compromised a bit, especially if your master password is not plenty secure. I suggest something like Diceware (i.e. https://www.eff.org/files/2016/07/18/eff_large_wordlist.txt ; with that you basically need five dice and for each roll of those five dice, reading from left to right (or right to left) as...
-
Just some thoughts in relation to services like Dropbox... personally I am not a fan of uploading sensitive files like Password Safe's database file online, since it just increases the risk of being compromised a bit, especially if your master password is not plenty secure. I suggest something like Diceware (i.e. https://www.eff.org/files/2016/07/18/eff_large_wordlist.txt ; with that you basically need five dice and for each roll of those five dice, reading from left to right (or right to left) as...
-
I am not sure about Ubuntu, but I do know that on Linux Mint to use a YubiKey in general in your web browser I had to use the following link to get it working as it does not work by default... https://www.yubico.com/authentication-standards/fido-u2f/#toggle-id-9 once I did that, the standard/basic blue YubiKey works (NOTE: the standard YubiKey won't work on Password Safe) through web browsers to login to Google account etc.
-
Assuming your phone has a MicroSD memory card slot I would just connect a MicroSD card to the PC and transfer the "PasswordSafe-Database.psafe3" (or whatever yours is named) to the MicroSD card then put that into your Samsung s7 and copy over the database file to your phone and run PWSafe on your phone and guide it to that file somehow. that should be the gist of it I would imagine. but I am not a fan of doing anything important on a smart phone in general as I would imagine they are generally less...
-
I realize I am a bit late. but in regards to your (Krishnamurthy) question... the YubiKey is not locked to any specific PC. in other words... if you got a YubiKey associated with Password Safe database file and your PC completely dies you are still good assuming you still got access to the Password Safe database file (which everyone should take measures to backup that database file to prevent any chance of losing access to your data stored in the Password Safe database file. it's very unwise not...
-
Exactly. that's what I always do (I have been using Password Safe since roughly mid-to-late 2000's) as it should not be much of a problem once things stable out for you as it's not like you will need to make changes to the PWSafe database file much after a while once you get your accounts setup with secure passwords as you don't need to change them unless you think one was compromised. I am sure you get the gist of it ;)
-
So your saying one device works? ; if so, why can't you just exit the PWSafe program on the device that works, copy it(the database file) to a USB flash drive, plug that into the second device, then copy that database file to the location where PWSafe uses the database file and when you load up PWSafe on that device, it should be able to open that databse file like usual. if not, you should be able to manually select it once you load up PWSafe. because regardless of whether your second device creates...
-
So your saying one device works? ; if so, why can't you just exit the PWSafe program on the dvice that works, copy it(the database file) to a USB flash drive, plug that into the second device, then copy that database file to the location where PWSafe uses the database file and when you load up PWSafe on that device, it should be able to open that databse file like usual. if not, you should be able to manually select it once you load up PWSafe. because regardless of whether your second device creates...
-
You should be able to just load the database file into password safe like usual and enter password and have access to the database. like after the password safe loads up, you should be able to select the location/file from there and then enter password like usual.
-
Yeah, I was playing with it a bit in virtual machine and seems to use your gpg verification (like "C887 6BE6 9A8E C641 4C8C 8729 B131 423D 7F2F 1BB9") to verify when installing, so that helps it a bit. but I get what your saying in that it appears legit now, but since that person is not tied to the official Password Safe project, theres no guarantee that person would not do something shady down the road etc even though chances are it will be okay, but you just can't be too sure since instead of coming...
-
If a person is using Manjaro Linux, is the following safe to use? https://aur.archlinux.org/packages/passwordsafe because from what I can tell, it's not from official sources.
-
Says... Error: Conflicts with the installed package 'passwordsafe-common' but after removing the Passwordsafe v1.08.2 BETA (which is what I was using as it was in the Mint v20 repositories), trying to install from your file (which I verified the signature to be safe), it still gave that error. but after doing a 'sudo apt-get remove passwordsafe-common' and then reinstalling from the ubuntu20 v1.11 deb file you linked to (which I checked gpg and it was good) it worked and I can load the program and...
-
Says... Error: Conflicts with the installed package 'passwordsafe-common' but after removing the Passwordsafe v1.08.2 BETA (which is what I was using as it was in the Mint v20 repositories), trying to install from your file (which I verified the signature to be safe), it still gave that error. but after doing a 'sudo apt-get remove passwordsafe-common' and then reinstalling from the ubuntu20 v1.11 deb file you linked to (which I checked gpg and it was good) it worked and I can load the program and...
-
Says... Error: Conflicts with the installed package 'passwordsafe-common' but after removing the Passwordsafe v1.08.2 BETA (which is what I was using as it was in the Mint v20 repositories), trying to install from your file (which I verified the signature to be safe), it still gave that error. but after doing a 'sudo apt-get remove passwordsafe-common' and then reinstalling from the ubuntu20 v1.11 deb file you linked to (which I checked gpg and it was good) it worked and I can load the program and...
-
Says... Error: Conflicts with the installed package 'passwordsafe-common' but after removing the Passwordsafe v1.08.2 BETA (which is what I was using as it was in the Mint v20 repositories), trying to install from your file (which I verified the signature to be safe), it still gave that error. but after doing a 'sudo apt-get remove passwordsafe-common' and then reinstalling from the ubuntu20 v1.11 deb file you linked to (which I checked gpg and it was good) it worked and I can load the program and...
-
Says... Error: Conflicts with the installed package 'passwordsafe-common' but after removing the Passwordsafe v1.08.2 BETA (which is what I was using as it was in the Mint v20 repositories), trying to install from your file (which I verified the signature to be safe), it still gave that error. but after doing a 'sudo apt-get remove passwordsafe-common' and then reinstalling from the ubuntu20 v1.11 deb file you linked to (which I checked gpg and it was good) it worked and I can load the program and...
-
Well apparently the official Linux Mint v20 ISO's are online and when attempting to install the v1.11 from Mint v19, it won't install as it complains about dependencies etc. I did not attempt the one for Ubuntu20. so any chance we can get a update for Mint v20 soon? p.s. the one in the repositories is v1.08.2 which is the one just before the official v1.09 release.
-
I just installed v1.11 on Linux Mint v19.3 and all seems to be okay as things are ordered properly once again. but one quick question... will you be releasing a Password Safe version for Linux Mint v20? ; because it's probably going to be officially released by the end of this month or so. or will the version for MInt v19 etc work okay on Mint v20? ; I am not in a huge rush as I might wait a while before upgrading (or clean installing) to Mint v20. but I just need to make sure Password Safe works...
-
I just installed v1.11 on Linux Mint v19.3 and all seems to be okay as things are ordered properly once again. but one quick question... will you be releasing a version for Linux Mint v20? ; because it's probably going to be officially released by the end of this month. or will the version for MInt v19 work okay etc?
-
It took me a while to spot it but I think I found what you are talking about... Find the entry one wants to move... right click entry, select 'Edit Entry...' then on 'Basic' tab find where it says 'Group' (and to the right of that) one can select which group they want to move it[the entry] to from the drop down menu then select OK. I never noticed that even though it's always been there. but thanks for the reply and bug fix.
-
It took me a while to spot it but I think I found what you are talking about... Find the entry one wants to move... right click entry, select 'Edit Entry...' then on 'Basic' tab find where it says 'Group' (and to the right of that) one can select which group they want to move it to from the drop down menu. I never noticed that even though it's always been there. but thanks for the reply.
-
@Mick Mickle you said, "However, the safe data file will still be locked until you click on the icon and enter the password." Yeah, that's part of the standard use stuff you mentioned as once it's locked in the tray (which, if I recall correctly, it does this by default after 5 minutes of inactivity), which is a GREEN icon, one just left clicks it and it will ask for the master password like usual to regain access to the stored passwords in Password Safe's database file.
-
@Mick Mickle [quote]However, the safe data file will still be locked until you click on the icon and enter the password.[/quote] Yeah, that's part of the standard use stuff you mentioned as once it's locked in the tray (which, if I recall correctly, it does this by default after 5 minutes of inactivity), which is a GREEN icon, one just left clicks it and it will ask for the master password like usual to regain access to the stored passwords in Password Safe's database file.
-
@Thomas Arter So your saying everything is working well and you no longer have any problems?
-
I spotted your issue. the icon your clicking on is the program icon running in the taskbar which we do not want to do. you need to click on 'tray icon' which should be not much to the left of the time display in the bottom right corner area of your screen. it's possible the icon might be semi-hidden (since if I recall correctly Windows 10 hides some of those icons by default instead of showing them all), but this should give you enough info on where to look. because everything I was saying in my...
-
I spotted your issue. the icon your clicking on is the program icon running in the taskbar which we do not want to do. you need to click on 'tray icon' which should be not much to the left of the time display in the bottom right corner area of your screen. it's possible the icon might be semi-hidden (since if I recall correctly Windows 10 hides some of those icons by default instead of showing them all), but this should give you enough info on where to look. because everything I was saying in my...
-
I think I pretty much spotted your issue. the icon your clicking on is the program running in the taskbar which we do not want to do. you need to click on tray icon which should be not much to the left of the time display in the bottom right corner area of your screen. it's possible the icon might be semi-hidden, but this should give you enough info on where to look. because everything I was saying was referring to the 'tray icon' NOT the icon your clicking on which is just a standard icon of current...
-
I think I pretty much spotted your issue. the icon your clicking on is the program running in the taskbar which we do not want to do. you need to click on tray icon which should be not much to the left of the time display in the bottom right corner area of your screen. it's possible the icon might be semi-hidden, but this should give you enough info on where to look. because everything I was saying was referring to the 'tray icon' NOT the icon your clicking on which is just a standard icon of current...
-
You don't want to run the main installer file again as that's what it sounds like your doing since you mentioned the 'run as administrator' thing. but assuming you started up the program like normal and entered your password like usual and can access the stored passwords, the icon is RED in the taskbar that means the program is still open in a unlocked state. right clicking the icon you should have a option like 'lock safe' and if you click that, the RED icon should now be GREEN, which now the Password...
-
If I am understanding that correctly it appears you are overlooking that the program itself automatically locks after I think it's 5 minutes of inactivity and the green icon is when the program is locked on the taskbar and red means it's still open to where you can access it. when it's green just left click the icon in the taskbar (or the like) and it will ask you for the master password and it should re-open and you can resume use like usual. you should not have to kill the process through task...
-
If I am understanding that correctly it appears you are overlooking that the program itself automatically locks after I think it's 5 minutes of inactivity and the green icon is when the program is locked on the taskbar and red means it's still open to where you can access it. when it's green just left click the icon in the taskbar (or the like) and it will ask you for the master password and it should re-open and you can resume use like usual. you should not have to kill the process through task...
-
Basically the way the password safe GROUP entries listed in v1.09 is alphabetical, which is normal/expected. but in v1.10 they are not ordered properly. I even removed v1.10, reinstalled v1.09 and opened the password safe and it's shown as expected. but when I upgrade to v1.10, the group entries are not listed alphabetically like they should be. but when looking at each group, the individual entries there are listed as expected in alphabetical order. so it appears it's just the group entries that...
-
Basically the way the password safe GROUP entries listed in v1.09 is alphabetical, which is normal/expected. but in v1.10 they are not ordered properly. I even removed v1.10, reinstalled v1.09 and opened the password safe and it's shown as expected. but when I upgrade to v1.10, the group entries are not listed alphabetically like they should be. but when looking at each group, the individual entries there are listed as expected in alphabetical order. so it appears it's just the group entries that...
-
I just wanted to say thanks to Steven Shiau for that link as it works well and I am using the newest Clonezilla v2.6.4-10. but since I am using older Wireless G router, the wireless is much slower and slows down the cloning process quite a bit, as it takes about 22min to finish on wireless vs a wired connection which takes less than 6 minutes with Clonezilla on same laptop/Clonezilla settings with only changing from WiFi to wired connection being the only difference. NOTE: I imaged Linux Mint v19.3-Xfce...
-
Those "-k1" and "-icds" options worked for restoring a Windows 7 image I made of a 250GB HDD (only about 17.7GB in use) to a Intel 545s 128GB SSD a moment ago (I just got a hold of that SSD recently for only $31.99). the actual data to be restored was 17.7GB according to the Clonezilla screen. it does show "device size: 250.0 GB" during the restore process but it finished and upon a reboot everything seems to be okay as I ran a error check within Windows 7 and all turned out fine and I checked to...
-
Like mentioned above by Art M, Clonezilla won't delete anything but you have to be careful and select the appropriate option which is generally the 'disc to image' one. if you want to save a bit of storage space I would go to the expert mode in Clonezilla and select the option so it does not backup the swap file etc as that will shrink the image file further. also, I generally use the 'pzstd' compression option in the expert settings to since it compresses well and does it fairly quickly as it's...
-
Yeah, I just sent that info to the YUMI devs and hopefully they sort it out because it's got to be some issue that YUMI does not like with file naming because I can get it to act consistently by naming it that way before adding the ISO to the USB stick using YUMI v2.0.5.3. You could try to rename the iso to "clonezilla-live-2.5.5-28-amd64 - Feb 18th 2018-BETA.iso" to see if that matters. I could, as it might narrow it down a bit further, but I think given the info I posted, which is basically what...
-
Well whatever happened everything seems okay now from the USB drive using YUMI. I wonder if file naming could cause YUMI to act up? ; because I named the Clonezilla ISO in the same way as I did on the test build from Jan 19th 2018 that worked as everything seems to work as expected now. basically they appear in the menu like this (which is how I have the ISO files named)... clonezilla-live-2.5.5-23-amd64 - Test 1-19-18.iso clonezilla-live-2.5.5-28-amd64 - Test 2-18-18.iso where as before with the...
-
Well whatever happened everything seems okay now from the USB drive using YUMI. I wonder if file naming could cause YUMI to act up? ; because I named the Clonezilla ISO in the same way as I did on the test build from Jan 19th 2018 that worked as everything seems to work as expected now. basically they appear in the menu like this (which is how I have the ISO files named)... clonezilla-live-2.5.5-23-amd64 - Test 1-19-18.iso clonezilla-live-2.5.5-28-amd64 - Test 2-18-18.iso where as before with the...
-
I just noticed that "clonezilla-live-2.5.5-23-amd64.iso" boots up and works as intended. but the newest version, which is "clonezilla-live-2.5.5-28-amd64.iso", does not boot as it shows this error message... http://i66.tinypic.com/35jarsl.jpg I tried this on my main computer (which has a i3-2120 CPU) and my 10 year old laptop (which has a AMD Turion CPU) and both get the exact same error message. but v2.5.5-23 works fine on both of them. so something must have got out of whack either in either v2.5.5-27...
-
Well whatever happened everything seems okay now from the USB drive using YUMI. I wonder if file naming could cause YUMI to act up? ; because I named the Clonezilla ISO in the same way as I did on the test build from Jan 19th 2018 that worked as everything seems to work as expected now. basically they appear in the menu like this (which is how I have the ISO files named)... clonezilla-live-2.5.5-23-amd64 - Test 1-19-18.iso clonezilla-live-2.5.5-28-amd64 - Test 2-18-18.iso where as before with the...
-
Well whatever happened everything seems okay now from the USB drive using YUMI. I wonder if file naming could cause YUMI to act up? ; because I named the Clonezilla ISO in the same way as I did on the test build from Jan 19th 2018 that worked as everything seems to work as expected now. basically they appear in the menu like this (which is how I have the ISO files named)... clonezilla-live-2.5.5-23-amd64 - Test 1-19-18.iso clonezilla-live-2.5.5-28-amd64 - Test 2-18-18.iso where as before with the...
-
Well whatever happened everything seems okay now from the USB drive using YUMI. I wonder if file naming could cause YUMI to act up? ; because I named the Clonezilla ISO in the same way as I did on the test build from Jan 19th 2018 that worked as everything seems to work as expected now. basically they appear in the menu like this (which is how I have the ISO files named)... clonezilla-live-2.5.5-23-amd64 - Test 1-19-18 clonezilla-live-2.5.5-28-amd64 - Test 2-18-18 where as before with the v2.5.5-28,...
-
Well after trying 'clonezilla-live-2.5.5-28-amd64.iso' from a bootable CD-RW disc it apparently works as that error is no longer there and boots to the menu as expected. so maybe it's some weird glitch with YUMI(?).
-
Well after trying 'clonezilla-live-2.5.5-28-amd64.iso' from a bootable CD-RW disc it apparently works as that error is no longer there and boots to the menu as expected. so maybe it's some weird glitch with YUMI(?). EDIT: well whatever happened it seems okay now even from the USB drive. I wonder if file naming could cause YUMI to act up? ; because I named the Clonezilla ISO in the same way as I did on the test build from Jan 19th 2018 that worked. basically they appear in the menu like this (which...
-
Well after trying 'clonezilla-live-2.5.5-28-amd64.iso' from a bootable CD-RW disc it apparently works as that error is no longer there and boots to the menu as expected. so maybe it's some weird glitch with YUMI(?). EDIT: well whatever happened it seems okay now even from the USB drive. I wonder if file naming could cause YUMI to act up? ; because I named the Clonezilla ISO in the same way as I did on the test build from Jan 19th 2018 that worked. basically they appear in the menu like this... clonezilla-live-2.5.5-23-amd64...
-
Well after trying 'clonezilla-live-2.5.5-28-amd64.iso' from a bootable CD-RW disc it apparently works as that error is no longer there and boots to the menu as expected. so maybe it's some weird glitch with YUMI(?). EDIT: well whatever happened it seems okay now even from the USB drive. I wonder if a file naming could cause YUMI to act up? ; because I named it the same as I did on the test build from Jan 19th 2018 that worked and put it on there with YUMI and now it appears to be perfectly fine....
-
Well after trying 'clonezilla-live-2.5.5-28-amd64.iso' from a bootable CD-RW disc it apparently works as that error is no longer there and boots to the menu as expected. so maybe it's some weird glitch with YUMI(?). [b]EDIT:[/b] well whatever happened it seems okay now even from the USB drive. I wonder if a file naming could cause YUMI to act up? ; because I named it the same as I did on the test build from Jan 19th 2018 that worked and put it on there with YUMI and now it appears to be perfectly...
-
Well after trying 'clonezilla-live-2.5.5-28-amd64.iso' from a bootable CD-RW disc it apparently works as that error is no longer there and boots to the menu as expected. so maybe it's some weird glitch with YUMI(?).
-
Does that allow booting from multiple ISO files from same USB stick or not? because that's what I need so I can have Windows 10/Clonezilla etc all booting from the same bootable USB drive instead of having to boot only one thing at a time. like YUMI boots to a initial menu and from there you can select what you want to boot be it Windows 10 ISO or Clonezilla ISO and whatever other bootable ISO's one wants to add and can use it like a standard USB drive to to store basic files. thanks for the rep...
-
I would say it's unlikely it's the stick because a few hours or so ago, using YUMI along with the same exact USB stick (Sandisk 64GB), Clonezilla from Jan 19th 2018 works perfectly fine but not the newest build like I mentioned in the topic (both are on the stick at the same time as I just select which one I want to boot from YUMI's main boot menu once booted from the USB stick initially). so unless it's some weird conflict with YUMI somehow, it would seem something has changed in Clonezilla. but...
-
I would say it's unlikely it's the stick because a few hours or so ago, using YUMI along with the same exact USB stick (Sandisk 64GB), Clonezilla from Jan 19th 2018 works perfectly fine but not the newest build like I mentioned in the topic (both are on the stick at the same time as I just select which one I want to boot from YUMI's main boot menu once booted from the USB stick initially). so unless it's some weird conflict with YUMI somehow, it would seem something has changed in Clonezilla. but...
-
I would say it's unlikely it's the stick because a few hours or so ago, using YUMI along with the same exact USB stick (Sandisk 64GB), Clonezilla from Jan 19th 2018 works perfectly fine but not the newest build like I mentioned in the topic. so unless it's some weird conflict with YUMI somehow, it would seem something has changed in Clonezilla. but what I might do is try booting it from a bootable CD-RW disc just to see if that reacts any differently. but even if that works it's odd that previous...
-
Does that allow booting from multiple ISO files or not? because that's what I need so I can have Windows 10/Clonezilla etc all booting from the same bootable USB drive instead of having to boot only one thing at a time. like YUMI boots to a initial menu and from there you can select what you want to boot be it Windows 10 ISO or Clonezilla ISO and whatever other bootable ISO's one wants to add and can use it like a standard USB drive to to store basic files. thanks for the reply.
-
I just noticed that "clonezilla-live-2.5.5-23-amd64.iso" boots up and works as intended. but the newest version, which is "clonezilla-live-2.5.5-28-amd64.iso", does not boot as it shows this error message... http://i66.tinypic.com/35jarsl.jpg I tried this on my main computer (which has a i3-2120 CPU) and my 10 year old laptop (which has a AMD Turion CPU) and both get the exact same error message. but v2.5.5-23 works fine on both of them. so something must have got out of whack either in either v2.5.5-27...
-
Did you ever consider waiting a few minutes or so to see if it does anything? because I know one of my old computers does not even let me navigate the initial main menu (on I think it was the i386 builds) and just automatically starts loading the CloneZilla program from that main initial boot screen. but assuming what I said above does not work eventually... you can try using a different version of CloneZilla. like if your using the 'stable' version try the 'alt stable' or vice versa. or try the...
-
For making images? I just make clones, takes less time overall. Yeah, I usually make images. but, come to think of it, like you say, clones are a bit quicker since it's just copying data basically instead of compressing it to a image and then uncompressing it back onto another drive. but on the flip side it requires you make the other one your cloning to bootable etc which I would rather avoid if you want to use the other drive for general storage space and will use more storage space on the drive...
-
I wish I could answer that one for you but I am not sure. I always skip checking/repairing source file system when I use CloneZilla on my Windows 10 computers. chances are you will be fine as I would imagine your Crucial SSD issue will probably not happen to you in the future. plus, if I recall correctly I think your Crucial SSD's have capacitors in them so when the power suddenly drops from a power outage it gives it a very brief moment to finish any writing it was doing etc, which supposedly helps...
-
I wish I could answer that one for you but I am not sure. I always skip checking/repairing source file system when I use CloneZilla on my Windows 10 computers. chances are you will be fine as I would imagine your Crucial SSD issue will probably not happen to you in the future. plus, if I recall correctly I think your Crucial SSD's have capacitors in them so when the power suddenly drops from a power outage it gives it that very brief moment to finish any writing it was doing etc. my Samsung 850 EVO...
-
I wish I could answer that one for you but I am not sure. I always skip checking/repairing source file system when I use CloneZilla on my Windows 10 computers. chances are you will be fine as I would imagine your Crucial SSD issue will probably not happen to you in the future. plus, if I recall correctly I think your Crucial SSD's have capacitors in them so when the power suddenly drops from a power outage it gives it that very breif moment to finish any writing it was doing etc. my Samsung 850 EVO...
-
So Crucial support fixed the issue. congrats and thanks for the info as that might benefit others in the future. It took 12 minutes to clone 115GB. QUESTION #2 OF 2: Would making an image be faster than 12 minutes? Well depending on your CPU and compression options choosen it can speed things up or give you better compression so the image takes up less space on your drive. personally I would use the 'pzstd' option in the newest test build(s) of CloneZilla v2.5.5-23 (from Jan 19th 2018) (NOTE: zstd/pzstd...
-
So Crucial support fixed the issue. congrats and thanks for the info as that might benefit others in the future. It took 12 minutes to clone 115GB. QUESTION #2 OF 2: Would making an image be faster than 12 minutes? Well depending on your CPU and compression options choosen it can speed things up or give you better compression so the image takes up less space on your drive. personally I would use the 'pzstd' option in the newest test build(s) of CloneZilla v2.5.5-23 (from Jan 19th 2018) (NOTE: zstd/pzstd...
-
So Crucial support fixed the issue. congrats and thanks for the info as that might benefit others in the future. It took 12 minutes to clone 115GB. QUESTION #2 OF 2: Would making an image be faster than 12 minutes? Well depending on your CPU and compression options choosen it can speed things up or give you better compression so the image takes up less space on your drive. personally I would use the 'pzstd' option in the newest test build(s) of CloneZilla v2.5.5-23 (from Jan 19th 2018) (NOTE: zstd/pzstd...
-
So Crucial support fixed the issue. congrats and thanks for the info as that might benefit others in the future. It took 12 minutes to clone 115GB. QUESTION #2 OF 2: Would making an image be faster than 12 minutes? Well depending on your CPU and compression options choosen it can speed things up or give you better compression so the image takes up less space on your drive. personally I would use the 'pzstd' option in the newest test build(s) of CloneZilla v2.5.5-23 (from Jan 19th 2018) (NOTE: zstd/pzstd...
-
So Crucial support fixed the issue. congrats and thanks for the info as that might benefit others in the future. It took 12 minutes to clone 115GB. QUESTION #2 OF 2: Would making an image be faster than 12 minutes? Well depending on your CPU and compression options choosen it can speed things up or give you better compression so the image takes up less space on your drive. personally I would use the 'pzstd' option in the newest test build(s) of CloneZilla v2.5.5-23 (from Jan 19th 2018) (NOTE: zstd/pzstd...
-
So Crucial support fixed the issue. congrats and thanks for the info as that might benefit others in the future. It took 12 minutes to clone 115GB. QUESTION #2 OF 2: Would making an image be faster than 12 minutes? Well depending on your CPU and compression options choosen it can speed things up or give you better compression so the image takes up less space on your drive. personally I would use the 'pzstd' option in the newest test build(s) of CloneZilla v2.5.5-23 (from Jan 19th 2018) (NOTE: zstd/pzstd...
-
So Crucial support fixed the issue. congrats and thanks for the info as that might benefit others in the future. It took 12 minutes to clone 115GB. QUESTION #2 OF 2: Would making an image be faster than 12 minutes? Well depending on your CPU and compression options choosen it can speed things up or give you better compression so the image takes up less space on your drive. personally I would use the 'pzstd' option in the newest test build(s) of CloneZilla v2.5.5-23 (from Jan 19th 2018) (NOTE: zstd/psztd...
-
That does seem odd because given those screen shots it don't seem like there is anything obviously wrong as your general drive health seems good. hell, you don't even have that many power on hours @ 266hours (a little over 11 days) with 707 power cycles. my Samsung 850 EVO 250GB SSD has 102 power cycle count and 23608 hours (about 2.7 years) with about 9.7TB of data written(it's rated for 75TB of writes). but I do leave my PC on pretty much all of the time. I had it since May 2015 so ill get many...
-
You are booting CloneZilla from a CD/DVD or USB thumb drive correct? ; use the ISO file and NOT the ZIP. see if that helps. so on your links change the 'file type' from ZIP to ISO. for extra insurance... ensure the checksum hashes (say SHA-1 or SHA-256 (7-zip(which is free) has a built in hash checker for this)) match as this gaurantees your download is 100% working and not faulty. both 'stable' and 'alt-stable' ISO's (i use the 'AMD64' builds since my CPU is 64bit and so is yours) work fine on my...
-
You are booting CloneZilla from a CD/DVD or USB thumb drive correct? ; use the ISO file and NOT the ZIP. see if that helps. so on your links change the 'file type' from ZIP to ISO. for extra insurance... ensure the checksum hashes (say SHA-1 or SHA-256 (7-zip(which is free) has a built in hash checker for this)) match as this gaurantees your download is 100% working and not faulty. both 'stable' and 'alt-stable' ISO's (i use the 'AMD64' builds since my CPU is 64bit and so is yours) work fine on my...
-
You are booting CloneZilla from a CD/DVD or USB thumb drive correct? ; use the ISO file and NOT the ZIP. see if that helps. so on your links change the 'file type' from ZIP to ISO. for extra insurance... ensure the checksum hashes (say SHA-1 or SHA-256 (7-zip(which is free) has a built in hash checker for this)) match as this gaurantees your download is 100% working and not faulty. both 'stable' and 'alt-stable' ISO's (i use the 'AMD64' builds since my CPU is 64bit and so is yours) work fine on my...
-
You are booting CloneZilla from a CD/DVD or USB thumb drive correct? ; use the ISO file and NOT the ZIP. see if that helps. so on your links change the 'file type' from ZIP to ISO. for extra insurance... ensure the checksum hashes (say SHA-1 or SHA-256 (7-zip(which is free) has a built in hash checker for this)) match as this gaurantees your download is 100% working and not faulty. both 'stable' and 'alt-stable' ISO's (i use the 'AMD64' builds since my CPU is 64bit and so is yours) work fine on my...
-
You are booting CloneZilla from a CD/DVD or USB thumb drive correct? ; use the ISO file and NOT the ZIP. see if that helps. so on your links change the 'file type' from ZIP to ISO. for extra insurance... ensure the checksum hashes (say SHA-1 or SHA-256 (7-zip(which is free) has a built in hash checker for this)) match as this gaurantees your download is 100% working and not faulty. both 'stable' and 'alt-stable' ISO's (i use the 'AMD64' builds since my CPU is 64bit and so is yours) work fine on my...
-
You are booting CloneZilla from a CD/DVD or USB thumb drive correct? ; use the ISO file and NOT the ZIP. see if that helps. so on your links change the 'file type' from ZIP to ISO. both 'stable' and 'alt-stable' ISO's (i use the 'AMD64' builds since my CPU is 64bit and so is yours) work fine on my main computer (which has a i3-2120 CPU) and my 10 year old laptop (I generally use the stable(Debian based) since it's a smaller download) and I am also using 16299.192 on my main computer (16299.194 on...
-
You are booting CloneZilla from a CD/DVD or USB thumb drive correct? ; use the ISO file and NOT the ZIP. see if that helps. so on your links change the file type from ZIP to ISO. both 'stable' and 'alt-stable' ISO's (i use the 'AMD64' builds since my CPU is 64bit and so is yours) work fine on my main computer (which has a i3-2120 CPU) and my 10 year old laptop (I generally use the stable(Debian based) since it's a smaller download) and I am also using 16299.192 on my main computer (16299.194 on my...
-
You are booting CloneZilla from a CD/DVD or USB thumb drive correct? ; use the ISO file and NOT the ZIP. see if that helps. so on your links change the file type from ZIP to ISO. both 'stable' and 'alt-stable' ISO's (i use the 'AMD64' builds since my CPU is 64bit and so is yours) work fine on my main computer (which has a i3-2120 CPU) and my 10 year old laptop (I generally use the stable(Debian based) since it's a smaller download) and I am also using 16299.192 on my main computer (16299.194 on my...
-
You are booting CloneZilla from a CD/DVD or USB thumb drive correct? ; use the ISO file and NOT the ZIP. see if that helps. so on your links change the file type from ZIP to ISO. both 'stable' and 'alt-stable' ISO's (i use the 'AMD64' builds since my CPU is 64bit and so is yours) work fine on my main computer (which has a i3-2120 CPU) and my 10 year old laptop (I generally use the stable(Debian based) since it's a smaller download) and I am also using 16299.192 on my main computer (16299.194 on my...
1 >