From: robertapengelly@gmail.com   
      
   On Monday, 20 November 2023 at 01:07:23 UTC, wolfgang kern wrote:   
   > On 19/11/2023 18:54, Robert Pengelly wrote:    
   > > On Sunday, 19 November 2023 at 14:29:27 UTC, wolfgang kern wrote:    
   > >> On 19/11/2023 13:25, Robert Pengelly wrote:    
   > >> ...    
   > >>> I commented out the stuff related to A9 and mouse still doesn't work.   
   I'm a little confused cause the int 15h stuff was PS/2 mouse so how did that   
   work but the IRQ doesn't?    
   > >>    
   > >>> What exactly does "KEYBD lines are stuck" mean?    
   > >> it mean that it's disabled or there is nothing connected to the port.    
   > >>    
   > >> what OS runs on your laptop ?    
   > >> if it's not DOS or a very OLD windoze then it will ignore your code.    
   > >> IRQ pointers and handling in Protected Mode is totally different to Real    
   > >> Mode code. Virtual Mode may work with 16 bit code, but protect IRQs.    
   > >>    
   > >> what type os connector is on your mouse ?    
   > >> if it's not a round one then it is an USB-mouse.    
   > >>    
   > >> PS/2 emulation for USB mice is possible on some machines but need to be    
   > >> told to do so in the motherboard's chips-set.    
   > >>    
   > >> sorry for I haven't asked all this earlier.   
   > > I'm still a little confused as to how int 15h works but the IRQ stuff is   
   returning 0x9C (I've checked an it's happening earlier than the 0xA9 stuff as   
   well). As for the OS I'm dual booting Windows 8.1 and Ubuntu but I'm not using   
   it inside either of    
   them as I'm writing an OS's so it's booting from a USB. As for the connector   
   I've tried the touchpad and a USB mouse and neither seen to work (again with   
   int 15h they both work).   
   > windoze 8.1 ?    
   >    
   > OK if your own 16-bit OS booted from USB.    
   > I'm just curious for which tool you used to put it there ?    
   >    
   > INT15h is a BIOS function and the BIOS knows its hardware well.    
   > Your laptop have neither keyboard nor mouse as PS/2 implemented,    
   > both will be USB devices.    
   > __    
   > wolfgang   
   I used dd on Linux to write an image to the USB.  I know that INT 15h is a   
   BIOS function but the 0xC2xx calls are for a PS/2 mouse aren't they?  As I'm   
   only focused on a 16-bit (real mode) OS at the moment would it be better if I   
   just go back to INT 15h?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)