Name | Modified | Size | Downloads / Week |
---|---|---|---|
CC386_VC_2022.zip | 2024-07-23 | 182.0 kB | |
readme.txt | 2021-07-08 | 1.0 kB | |
Tracer.zip | 2021-07-08 | 452.6 kB | |
DOS.zip | 2021-06-23 | 1.3 MB | |
LIB.zip | 2021-06-23 | 2.5 MB | |
LO.zip | 2021-06-23 | 2.3 MB | |
VINM.zip | 2021-06-23 | 4.0 MB | |
Num-02-08-2012.zip | 2021-06-23 | 3.3 MB | |
CPP.zip | 2021-06-23 | 509.7 kB | |
CC.zip | 2021-06-23 | 4.3 MB | |
AS.zip | 2021-06-23 | 3.9 MB | |
A-OS.zip | 2021-06-23 | 7.0 MB | |
Totals: 12 Items | 29.7 MB | 0 |
I've read the Linux kernel. Read some books of the operating system. I am very suspicios how they issue 1. kernel spinning round. :: spin_lock() spin_unlock() 2. ..._irq_save() , ...irq_restore() 3. wait4() Thus, it meant they did not understand how process or thread works; I didn't speak out since:: I need to, to prove something OR somthing error on Windows 9x,ME. when it have to run with VM86 DPMI device (int13) or DOS Box mode. Tool you need is a 1. thread CONTEXT ( call TSS in x86 CPU) 2. thread TABLE ( GDT in x86 CPU) Thread(0) = idle process Thread(1) = system maintanance gate Thread(2) = user -----thread(0)------ Task switches by jmp _task cal_task int_task ----------------------------------------- System User ----------------------------------------- Thread(0) Thread(2) / / / Thread(1) \ \ Thread(2) Thread(0) -------------- Thread(2) is terminated Enjoy................................