1
General Discussion / Re: Do we still need a 64-bit version of OS/2? And a possible roadmap provided ...
« on: August 30, 2024, 09:07:26 pm »
If you want it or not does not matter: there will never be a 64-bit version of OS/2. Period.
OS2World.com Forum is back !!!
Remember to visit OS2World at:
http://www.os2world.com
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Here is another round-about way to make a JFS partition on an USB drive. With this method, I am using the whole drive for the JFS.
Open DFSee.
Select Scripts in the menu
Select Make Fat32 Data USB disk
Select the drive and make a fat32 data disk.
Follow the prompts.
Eject USB drive and reinsert.
Now I use FM/2
Open FM/2
Right click on the FAT32 USB drive
Select Miscellaneous
Select Format Disk
Select JFS
I do the quick format.
Done.
I bought around 10 packages of 3- 32 GB USB drives at Target last year for around $5.00 for each package. It was an after school clearance. Formatted them With DFsee to FAT32. Thus, it was easy for me to format JFS under FM/2 when I want. I had already made them FAT32 with DFSee. The drives were originally FAT32 when bought. However, for ArcaOS to use the drives, DFSee had to be used to reformat them Fat32. Being already done, it took little time to convert to JFS.
It would be nice for DFSee to have a script to make a JFS data disk.
Thanks Dave - it's working well here!
There is a long standing bug in Dooble on OS/2 where if you try to open an HTML file, it always says 'Your file couldn't be accessed' even though you just clicked on it. However, if that file is on your %UNIXROOT% drive (say C:), and you remove 'C:' from the address bar with that file name on it, the file is displayed. If it is not on the %UNIXROOT% drive, removing, say 'D:' does not help and can not be displayed.
The implication is the code is using a Linux standard to find the file (no drive letters) so it works this way only on the %UNIXROOT% drive. But the Windows version of Dooble does use drive letters and it does work, so it seems there must be a code path available to use drive letters when displaying files if needed.
Are you familiar with this? Has it been looked at in the past? The reason it is important to me is I would like to use Dooble to display e-mail messages from PMMail, but it doesn't work because PMMail is not on %UNIXROOT% so even removing the drive letter doesn't help in that case. Seems like there should be a straight forward solution to this, if the proper code was identified...
Regards,
I vaguely remember that Dmitry already had a fix in place that went into a test version of one of the Qt5 DLLs. I just cannot remember which one that was ...
Thanks for the tip.
There is: https://github.com/bitwiseworks/qtwebengine-chromium-os2/issues/50
&
https://github.com/bitwiseworks/qtwebengine-chromium-os2/commit/6d53f8735fc37460d217f6d641eae585960c1e53
This may have been applied by Dmitry after I created my diffs... I certainly don't have it in my branch...
Thanks Dave - it's working well here!
There is a long standing bug in Dooble on OS/2 where if you try to open an HTML file, it always says 'Your file couldn't be accessed' even though you just clicked on it. However, if that file is on your %UNIXROOT% drive (say C:), and you remove 'C:' from the address bar with that file name on it, the file is displayed. If it is not on the %UNIXROOT% drive, removing, say 'D:' does not help and can not be displayed.
The implication is the code is using a Linux standard to find the file (no drive letters) so it works this way only on the %UNIXROOT% drive. But the Windows version of Dooble does use drive letters and it does work, so it seems there must be a code path available to use drive letters when displaying files if needed.
Are you familiar with this? Has it been looked at in the past? The reason it is important to me is I would like to use Dooble to display e-mail messages from PMMail, but it doesn't work because PMMail is not on %UNIXROOT% so even removing the drive letter doesn't help in that case. Seems like there should be a straight forward solution to this, if the proper code was identified...
Regards,
The Windows host Virtualbox implementation contains the very same OS/2 addons as those provided by ArcaOS, including the file system driver to access files on the host from within the OS/2 guest.
Doesn't the OS/2 addons installed on Windows/Linux come with an old libc? I"d assume the ArcaOS addons don't install libc