You are not logged in.
Pages: 1
Sir, thanks for the great Distro and Windows Installer.
Can you please give another exe for the user, that has distro embedded in exe. So that we can install it in offline environment like PhoenixOS Android does.
Thanks
Offline
It's possible to use the current installer offline. You need to have the installer and image file "q4os-3.0-x64-loop.img.xz" downloaded, and subsequently run in Windows command prompt:
q4os-winsetup.exe --dimagepath=c:\full_path_to_the_image\q4os-3.0-x64-loop.img.xz
For more info about possible installer options please read https://github.com/hakuna-m/wubiuefi/wi … arameters-
Offline
It's possible to use the current installer offline. You need to have the installer and image file "q4os-3.0-x64-loop.img.xz" downloaded, and subsequently run in Windows command prompt:
q4os-winsetup.exe --dimagepath=c:\full_path_to_the_image\q4os-3.0-x64-loop.img.xzFor more info about possible installer options please read https://github.com/hakuna-m/wubiuefi/wi … parameters-
Oh, so all things explained at https://github.com/hakuna-m/wubiuefi/wiki/FAQ will also work with Q4OS too?
Like placing iso in the same folder or giving iso as parameter etc.,
Thanks
Last edited by HemanthJabalpuri (2021-02-19 08:31)
Offline
Oh, so all things explained at https://github.com/hakuna-m/wubiuefi/wiki/FAQ will also work with Q4OS too?
Like placing iso in the same folder or giving iso as parameter etc.,
No, not all of the parameters will work, however most of them do. For example you can install Q4OS from disk image, but not from iso image.
Offline
No, not all of the parameters will work, however most of them do. For example you can install Q4OS from disk image, but not from iso image.
Oh, then we definitely need the iso option since there is no disk image for latest Q4OS. Or release the disk image of the latest one.
If there is no iso option, then how it will install latest one??
Thanks
Last edited by HemanthJabalpuri (2021-02-19 10:46)
Offline
... there is no disk image for latest Q4OS...
The disk image is available, the file "q4os-3.0-x64-loop.img.xz", you can download it from the SourceForge repository, see above.
Offline
The disk image is available, the file "q4os-3.0-x64-loop.img.xz", you can download it from the SourceForge repository, see above.
Sorry if I am annoying. Since I am a new Linux user.
I found img at https://sourceforge.net/projects/q4os/files/stable/
Why it is versioned as 3.0 instead of 3.14?
Also q4os-3.0-x64-loop.img.xz is Trinity or Plasma?
Why I am asking these questions instead of trying myself is that, I have less Internet and cannot download again and again.
Thanks
Last edited by HemanthJabalpuri (2021-02-19 14:51)
Offline
The "q4os-3.0" means the complete line, you get 3.13 version as you install it. Once you update the system from repositories, you get the most recent 3.14 version.
Offline
The "q4os-3.0" means the complete line, you get 3.13 version as you install it. Once you update the system from repositories, you get the most recent 3.14 version.
Thanks for reply.
Please add iso support to windows installer, so that we can install normal releases like 3.14.
Also uninstalling is not removing GRUB.
Offline
Sorry about riding someone else's thread for this report, but I believe my post is on-topic.
(Before I start and for anyone interested, let me just state that, funnily enough with the quarantine and all, I haven't had much time to go on with my Q4OS experiments lately.)
I just did another quick run of 'q4os-winsetup.exe' from Windows (v10[.0.19041.388] this time) booted off a virtual disk, with the parameters in post #2.
It quickly failed -- log is at https://rentry.co/iab9m.
It looks like q4os-winsetup tried to run 'C:\Windows\sysnative\bcdedit.exe /enum' and gave up when it got back a negative.
I never changed anything related to 'bcedit.exe' so went looking for it: turns out it is still present in plenty locations (36, no less), with the most obvious being 'C:\Windows\System32\' (no 'sysnative' dir, though).
When I tried manually running 'bcdedit /enum' as admin just to see what would come out, I got another error:
The boot configuration data store could not be opened.
The requested system device cannot be found.
But this Windows has been working fairly well for a couple of months now, with no boot errors or any serious crashes.
For completeness, here's the output of Diskpart:
DISKPART> list volume
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 Z DVD-ROM 0 B No Media
Volume 1 D SSD-ADATA NTFS Partition 100 GB Healthy System
Volume 2 VTOYEFI FAT Partition 32 MB Healthy
Volume 3 E HDD-DATA NTFS Partition 465 GB Healthy
Volume 4 System Rese NTFS Partition 50 MB Healthy
Volume 5 C NTFS Partition 63 GB Healthy Boot
Note that "Volume 5" is in fact a VHD file residing in "Volume 1" -- a Mint Linux liveCD ISO (v20 64-bit) residing at the same location also boots perfectly. "Volume 3" is on a physical HDD and that's where I intended to place Q4OS.
Offline
@Midas
Thanks for the report we will take a look to check for possible bcdedit caveats.
Offline
Quick note for a real feature request, this time:
I understand it's beneficial from a branding POV to have your own Windows installer but wouldn't it make the developing burden easier if you just made the Windows installer be the vanilla Wubiuefi -- and just make instructions available for Q4OS to be used with it? Assuming there are no deep rooted technical reasons preventing this...
Wubiuefi already provides some information on setting up non-Ubuntu distros (cf. https://github.com/hakuna-m/wubiuefi/wi … sversions), but I wouldn't know which way to go if I wanted to try it on my own.
Offline
Pages: 1