In the far distant age of win 95 I remeber very interesting program named qemm for windows. It Had fast reboot function.What is it: my pc has many SCSI and SATA devices wich are tested every time before OS booting for a very long time. With this program when you restarted windows the booting process SKIPED Bios device testing and windows booted directly. This method saved much time which usually spends for this needless Bios testing. SO this test happened only once when I powered my PC on and never when reboot. Can this future be realized in HAIKU in a low level ir as independent utility?
err, that is NOT a disk test. Its the spin up time.
Skipping that can and will eventually destroy your disk. That time is required to bring SCSI/SATA disks up to the correct speed and ensure they’re spinning correctly before engaging the heads.
Skfyr wrote:
In the far distant age of win 95 I remeber very interesting program named qemm for windows. It Had fast reboot function.What is it: my pc has many SCSI and SATA devices wich are tested every time before OS booting for a very long time. With this program when you restarted windows the booting process SKIPED Bios device testing and windows booted directly. This method saved much time which usually spends for this needless Bios testing. SO this test happened only once when I powered my PC on and never when reboot. Can this future be realized in HAIKU in a low level ir as independent utility?
No.
Unless you write your own hardware firmware (nothing at all to do with Hauku), and create custom built build of Haiku, doing no hardware test, and not searching for drivers, rather simply assuming driver x is to be used.
In a way it’s how windows ce works on pocket / embedded pcs. (except for usb / pcmcia add ons).
MYOB wrote:
err, that is NOT a disk test. Its the spin up time.Skipping that can and will eventually destroy your disk. That time is required to bring SCSI/SATA disks up to the correct speed and ensure they’re spinning correctly before engaging the heads.
I understood,but this is not only spin up. My SCSI controller has 30 channels and only 1 device on it, so 29 channels are free. Every booting it tryes to find new devices on each channel! And testing every channel takes 0.5 of second. And I cant explain this stuped mashine that when I reboot windows it doesn’t mean that I plug any new device in my controller. You know, when try make windows (MustDie) work and must reboot it up to 20 times, this senseless attempts to find 29 new devices make my fill frenzy 
Can you disable the check in your bios (or your SCSI controller’s bios)?
I have shaved a couple of seconds off boot by setting by hard disks to “manual” rather than auto, and setting the channels without any drives to “none”. Also I moved up the HDD to #1 in the boot order and now the bios is only visible for 2 or 3 seconds before bootman appears.
unfortunealy it is impossible. But this is another question. Main question of this this topic is: is there any utility like quemm for windows but for beOs or Haiku?
No there isn’t. However BeOS/Haiku don’t need full reboots very often - you can usually just restart whatever server/app that was causing problems.
Skfyr wrote:
unfortunealy it is impossible. But this is another question. Main question of this this topic is: is there any utility like quemm for windows but for beOs or Haiku?
Almost every SCSI bios i’ve seen allows the disable of scan on a per ID basis – I’ve always been able to disable SCSI id scanning for all but the devices that are actually connected…
I always thought QEMM was a memory manager similar to EMM386 (predecessor in fact) – i’m pretty sure that anything that allowed a “fast-boot” like you’re talking about was mostly a hack and probably wouldn’t work properly on any of todays hardware, or in conjunction with today’s hardware-intensive operating systems… Nowadays, most operating systems expect to have full control over the hardware…