From: "Al Amzeen (Alexandr Amzin)" Newsgroups: comp.os.msdos.djgpp Subject: Re: crazy question! Date: Thu, 11 May 2000 23:10:55 +0400 Organization: Fidolook Express page http://fidolook.da.ru Lines: 21 Message-ID: <8ff0qc$30ut$1@gavrilo.mtu.ru> References: NNTP-Posting-Host: ppp103-180.dialup.mtu-net.ru X-Trace: gavrilo.mtu.ru 958072461 99293 212.188.103.180 (11 May 2000 19:14:21 GMT) X-Complaints-To: usenet-abuse AT mtu DOT ru NNTP-Posting-Date: 11 May 2000 19:14:21 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Fidolook Express V1.51rus for MS OE 5.0 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Greetings, Prashant TR ! You wrote: > > What do you need this for? There might be a way of doing it, but it > > only works in some specially-set environments, so it is not clear > > whether it's good enough for what you have in mind. > > I tried something similar for a diagnostic that I was writing. It was > supposed to do the walking 0s and 1s test on the entire physical memory. > But it wasn't worth the all the pain. The DPMI lies about physical memory > size most of the time, so you need to do some extra work to find out the > memory size. Plus problems I mentioned in the other mail. > > Otherwise, I don't think anyone could do some useful by just reading > arbitrary portions of the memory. Well, we can use OS loader for protected mode and then multiprocess kernel on DJGPP for tasks-in-RAM execution. Dirty one example, but this one should work. :) ps. Terrible, isn't it? :^)