OS/2, eCS & ArcaOS - Technical > Applications

OS/4 (technical details only)

<< < (2/60) > >>

David Graser:
Lenovo Thinkpad x220

Dual boot to either Windows 7 or ArcaOS 5.02

lSVN5094_unoff.zip

I really like this kernel.  The system is more responsive, less CPU trashing, and my CPU operates cooler.  My system even appears to operate in a more stable condition.  It even shows one how bad  Firefox is with all its jumbled code.  The CPU maxes out, but Firefox still remains responsive and the CPU continues to remain cool.

I have encountered a problem and it deals with RAM drives.  I use the ArcaOS ram drive in HPFS.  If I reboot, everything is fine.  However, when I power down and then power up to boot to ArcaOS, the RAM drive disappears and I cannot get it back.  Playing with the RAM drive settings does no good.  The only way to get it back is to install an archive.  I can reboot nothing changes.  Only when my computer is powered down and then turned back on that the RAM drive problem surfaces.  I like my RAM drive, however, if I have to, I can do without it to continue to use this kernel.

ivan:
Hi David,

What you are seeing with power down and the ramdisk is what you should expect.  What is on a ram drive is lost when the system is powered down - Ramdisks are only there as long as there is power to the ram and the refresh mechanism is working - no power, even for a very short time, results in no ramdrive.

David Graser:

--- Quote from: ivan on April 18, 2018, 01:05:04 am ---Hi David,

What you are seeing with power down and the ramdisk is what you should expect.  What is on a ram drive is lost when the system is powered down - Ramdisks are only there as long as there is power to the ram and the refresh mechanism is working - no power, even for a very short time, results in no ramdrive.

--- End quote ---

Hi Ivan

Yes, but should not the RAM disk be rebuilt when the system is booted back up.  The RAM drive is no longer there.  The driver is listed in the config.os4 file.  Now I can boot using the IBM loader and kernel and the RAM disk is there after power up and boot up. The IBM kernel had no problem with the disappearing RAM drive.  Once the RAM disk was selected in the RAM disk setting, it is always present whether one rebooted or powered down and powered  back up.  Yes, the information should be lost when powering down, but the whole RAM should not disappear when booted back up.

Valery Sedletski:
2David Graser: I don't understand you. The ram disk disappears when the system is powered down, because power is switched off, and RAM is not refreshed, as Ivan said. This is what happens. Or, do you mean that the .ZIP file does not unzip to ramdisk? BTW, do you use QSINIT, or OS/4 os2ldr? The ram disk works only with QSINIT (or Arca Noae os2ldr, which is a crippled version of QSINIT). OS/4 os2ldr does not create the ram disk, possibly, that's because you lose your ramdisk. So, did you tried QSINIT, and does it change something?

PS: Note that you should disable the OS/4 logo, by adding "NOLOGO" to kernel parameters, or QSINIT will cause system to hang on VESA mode detect. This is unsolved problem, yet.

PPS: The ram disk is in fact created by QSINIT. hd4disk.add only allows this disk to be mounted under OS/2. So, hd4disk.add without QSINIT will not work. Arca Noae loader should work too, instead of QSINIT, theoretically, if you'll boot OS/4 kernel with it. But AFAIK, it does not support choosing multiple kernels from the menu. So, you'd better install QSINIT, instead.

Valery Sedletski:
Also, I should note that I don't know, how does Arca Noae loader restores the ram disk. For QSINIT, it requires creating the qssetup.cmd file in the root directory, with the following lines:


--- Quote ---ramdisk z:
unzip /boot /q qsinit.ldi c:\

--- End quote ---

-- This will create the single FAT/FAT32 z: disk under OS/2 (drive letter c: under QSINIT) and unzip the qsinit.ldi file to the ramdisk.

To get it formatted with HPFS, you should use qssetup.cmd with the following contents:


--- Quote ---ramdisk z:
format c: /fs:hpfs
unzip /boot /q qsinit.ldi c:\

--- End quote ---

QSINIT supports multiple ramdisks with different FS-es, like this:


--- Quote ---ramdisk z: q: div=565
format c: /fs:exfat /a:1k /q /wipe
mount d: hd3 1
unzip /boot /q qsinit.ldi c:\

--- End quote ---

-- This will create disk z: (c: or 0: under QSINIT) formatted as exFAT and extract qsinit.ldi to it, and disk q: (d: or 1: under QSINIT), 565 MB in size, formatted with FAT16 (empty). For more details, refer to QSINIT documentation. exFAT ramdisk can be mounted via fat32.ifs.
You can use exFAT or FAT32, or FAT16, or HPFS for your ram disks the same way.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version