• General Chat
  • Godot dropped all projects- will not import projects: edit its a windows issue

@jbskaggs said:
According to Ubuntu my experience is not rare and windows does have a history of wiping all linux partitions on drives it finds on updates.

Does it wipe all disks or just the system disk?

But it is clear that you need separate disks for each system... a bit expensive...

@Tomcat said:

@jbskaggs said: According to Ubuntu my experience is not rare and windows does have a history of wiping all linux partitions on drives it finds on updates. Does it wipe all disks or just the system disk?

But it is clear that you need separate disks for each system... a bit expensive...

Not all disks - partitions on drives the windows is on. This current linux I installed today I put it on an older HDD for now and didnt touch my windows ssd drive.

Yes, it's best if you use 2 separate drives for Windows and Linux and when installing, you have to unplug the other one so the boot records don't get messed up. It's pretty annoying, and Linux generally respects things, but Windows will do all kind of stuff you don't ask it (like overriding the boot record, or installing it on other hard drives other than the one you selected, etc.) which will corrupt the dual boot. At best, it means you can only enter Windows and not Linux, or at worse, your system won't boot at all.

@cybereality said:
…Windows will do all kind of stuff you don't ask it (like overriding the boot record, or installing it on other hard drives other than the one you selected, etc.) which will corrupt the dual boot.

I caught this problem when I installed the Win 10 beta for review purposes. The good thing is that I previously cloned the system partition to a spare disk and was able to restore everything easily.

Then a question for connoisseurs, how is Linux doing with NVMe booting, no big problems?

Linux is fine now with hardware support, at least on the motherboard side. I haven't had any problems for a long time. It can still be a little sketch with Wifi cards (especially on USB) and other stuff like that, but in terms of the main components, they all work now.

Hmm I am on day 2 of getting linux working on this 2013 desktop computer.

step 1. Ubuntu 20.04 LTS will not install will not run live usb longer than 2 or 3 mouse clicks. step 2. Puplinux fossa 9.5 cannot use as I have a hdmi monitor and cant see screen to make changes step 3. Sparky linux (my old standby based on Ubuntu except lighter weight with more compatibility drivers) same problem as ubuntu cant install and locks up after 1 or 2 mouse clicks- using Mate desktop Step 4. Garuda Linux(arch linux gamified for nvidia drivers) - installs and runs but sound is not working. Seems to be trying to use wrong sound card. Pipewire frozen. Uninstalled pipewire and installed pulseaudio. Pulseaudio runs but no sound and pulseaudio control locks at "connecting to pulseaudio server". So I cant use that to set the sound card channels. I am trying to figure out how to do that from terminal instead- so far no luck. Even though this seems to be a very common setup problem for many linux flavors.

This computer has 2 hdmi cards. on board AMD CPU with AMD integrated radeon graphics. This other is a Nvidia Geforce. Uses the Nvidia Geforce HDMI video fine - but audio is trying to use the integrated sound card.

Now I had a chance to install windows 7 on another computer system couple months back and had similar issues with hdmi sound and video. and it took me a while to fix it.

EDIT: its not using the radeon card either it is trying to use a Intel sound chip driver.

@newmodels said: I found this information about ubuntu live os Freezing. It might be related because of your multi graphics card setup. Can you turn off the radeon sound and radone gpu in the bios? https://askubuntu.com/questions/1245525/ubuntu-20-04-live-usb-freezes

No I cant disable in Bios.

Just stuck with Garuda (arch) linux dragon gamefied edition. https://garudalinux.org/downloads.html The reason I like this flavor is it runs more windows programs than any other flavor I have tried (I have ran over 40 flavors in the past 2 years) as it is prebundled with many compatibility drivers not readily findable in debian/ Ubuntu.

I fixed everything finally. I had to do it in a weird but typical linux way.

Uninstalled pipeware rebooted. Then installed pulesware. Then uninstalled pulseware. rebooted. Commented out the Nvidia rules file. reinstalled pipeware and KDE MIX rebooted and it now works.

so it is now fixed.

Long story short: I could have probably just commented out the Nvidia rules file originally and fixed the whole thing in 2 minutes. (/etc/udev/rules.d/90-nvidia-prime-powermanagement.rules)

Yeah, Linux has been good recently, but there is only so much you can do with old hardware. I also found Nvidia to be really bad and buggy, which is why I went all AMD on my latest rig, no problems. I mean, it was an upgrade, but not hugely so. My old computer was still good. I had an Nvidia RTX 2080 Ti before, and I just gave it to this guy I knew on another forum. Probably could have made some money, but the joy I got out of giving it to him was worth more than $1,000 to me.

A bit late now, but decrappifiying windows is pretty much the first thing anyone should do with a fresh install.

It's annoying that you'd have to, but no more so than the first weekend or so of tweaking [insert linux distro of choice].

I don't like those all-in-one scripts. I tried something like that awhile ago (I think on Windows 8) and it messed things up so badly that I had to reinstall. In any case, it only takes like 2 or 3 hours to do it manually, and you can be sure it's exactly what you want. Yeah, it sucks, but you spend 3 hours one time and you can get the settings perfect.

@Bimbam said: A bit late now, but decrappifiying windows is pretty much the first thing anyone should do with a fresh install.

It's annoying that you'd have to, but no more so than the first weekend or so of tweaking [insert linux distro of choice].

thats true- and like Cybersaid older components cause problems as well.

Well I've gotten pretty good on Ubuntu now. I setup my living room PC recently and it only took about 2 hours to install fresh and load my customizations.

@cybereality said: Well I've gotten pretty good on Ubuntu now. I setup my living room PC recently and it only took about 2 hours to install fresh and load my customizations.

Usually Can install a linux system in under 3 hours- but this machine I think is on its last legs. At worst Id have to run a AMD integrated video when Im in Linux.

I gave my nice AMD card to my son. And this Nvidia is nice but I think its sound chip is misfiring. I noticed earlier when I booted back into windows some of the same behavior of sound cutting in and out.

11 days later

I am supposed to have a usb3 to ide/sata converter delivered today. Hopefully I will be able to pull all my game data off those drives from the computer that died.

My usb to sata cord delivered and I copied over the data for my godot games and their art. Now to figure out why I am getting sudden end of file errors on the projects.

The project may have been corrupted. There are ways to rebuilt the project, I think there was a Github app that could do it, but I'm not sure when the last time it was updated. But one thing you can try is to create a new project, and then manually copy over the scene files (tscn) one by one. The images and sound should be no problem, so you can copy all the assets first. Then copy over the scripts, which are also fine. Then for the tscn files copy one by one and check them first in the new project. If they are working, copy the next one. I had to do this once and I was able to fix almost everything. One scene was totally corrupted, though, and I had to remake it.

It could also be the thing about the line endings I mentioned in the other thread. There are a couple ways the project can get corrupted.