Re: [Freedos-user] A tool for CPU-load measurement

2012-03-28 Thread TJ Edmister
On Wed, 28 Mar 2012 18:33:42 -0400, Zbigniew wrote: > > This time I would compare, how much CPU time will my "toy program" > need on different machines. I would to make it show, how many percent > of CPU time was needed, if this can be possible. > > Why? Because I'm not going to make it "as fas

Re: [Freedos-user] Catch-all Repository for legacy DOS software

2012-03-28 Thread Jeffrey
On 03/28/2012 11:22 AM, Jim Hall wrote: I would be happy to have an open, editable directory of legacy DOS software, including screenshots & descriptions. I think that part is a great idea. But we would be unable to host or distribute any files, nor link to sites that have them unless they are

Re: [Freedos-user] A tool for CPU-load measurement

2012-03-28 Thread Bernd Blaauw
Op 29-3-2012 1:38, Michael Robinson schreef: > WARNING, you can't write a program that takes another arbitrary > program as input and tells you whether or not it halts. This is > called the halting problem. As far as loop troubleshooting, you may > want to use another OS and a debugger to write

Re: [Freedos-user] A tool for CPU-load measurement

2012-03-28 Thread Michael Robinson
On Wed, 2012-03-28 at 23:27 +, Zbigniew wrote: > You know: graphics is one thing - this is just actual "fun project" - > but being able to detect instantly the weak place in program, which is > causing unnecessarily high CPU load (say: looping for a key without > any "pause 10 ms"), is the othe

Re: [Freedos-user] DOS and timing...

2012-03-28 Thread Zbigniew
2012/3/28, Bernd Blaauw : > In-app profiling, or using a debugger maybe, could help. > Otherwise, run DOS and your program inside an emulator > (QEMU/Bochs/DosEMU) and get detailed output (timestamped logfiles) from > that. But of course using debugger I can check this in its every detail. But ha

Re: [Freedos-user] A tool for CPU-load measurement

2012-03-28 Thread Zbigniew
You know: graphics is one thing - this is just actual "fun project" - but being able to detect instantly the weak place in program, which is causing unnecessarily high CPU load (say: looping for a key without any "pause 10 ms"), is the other useful thing. Then actually I'm looking for something of

Re: [Freedos-user] DOS and timing...

2012-03-28 Thread Bernd Blaauw
Op 29-3-2012 1:20, Zbigniew schreef: > Ability to detect heavy CPU load can be important information for me, > that e.g. I did something wrong (for example, some loop has to be done > differently). In-app profiling, or using a debugger maybe, could help. Otherwise, run DOS and your program inside

Re: [Freedos-user] DOS and timing...

2012-03-28 Thread Zbigniew
2012/3/28, Michael Robinson : > Since DOS environments typically don't multitask, there's no need to > time applications as they consume CPU resources and preempt them to let > other applications run. [..] Ability to detect heavy CPU load can be important information for me, that e.g. I did

[Freedos-user] DOS and timing...

2012-03-28 Thread Michael Robinson
Since DOS environments typically don't multitask, there's no need to time applications as they consume CPU resources and preempt them to let other applications run. Modern multi core processors can do real multitasking and don't have to simulate process concurrency. In DOS environments, t

Re: [Freedos-user] A tool for CPU-load measurement

2012-03-28 Thread Eric Auer
Hi Z, > This time I would compare, how much CPU time will my "toy program" > need on different machines. I would to make it show, how many percent > of CPU time was needed, if this can be possible. For total runtime, you could do RUNTIME YOURPROGRAM at the prompt... > > Why? Because I'm not goi

Re: [Freedos-user] A tool for CPU-load measurement

2012-03-28 Thread Zbigniew
2012/3/28, Eric Auer : > You do not have to explicitly program anything for this: > Just run FDAPM APMDOS at some time, e.g. in your autoexec > and then run FDAPM STATS to see how much of the time the > CPU was idle - to be exact, which percentage of the time > slices contained any idle time, so "

Re: [Freedos-user] A tool for CPU-load measurement

2012-03-28 Thread Zbigniew
2012/3/28, dmccunney : > While it *can* be done, I'm not sure why you want to. > > On a multi-tasking OS like Windows or Linux, I'll use Process Explorer > (Win) or top (Linux), to get an idea of which programs are hitting the > CPU. This time I would compare, how much CPU time will my "toy progr

Re: [Freedos-user] A tool for CPU-load measurement

2012-03-28 Thread Eric Auer
Hi Zbigniew, >> Actually you can use FDAPM for that: While the APMDOS >> function is active, FDAPM keeps MSDOS POWER compatible >> statistics of which percentage of the timer tick... You do not have to explicitly program anything for this: Just run FDAPM APMDOS at some time, e.g. in your autoexe

Re: [Freedos-user] A tool for CPU-load measurement

2012-03-28 Thread dmccunney
On Wed, Mar 28, 2012 at 5:21 PM, Zbigniew wrote: > There are various tools for Windows/Linux, which can display actual > CPU workload. Since DOS doesn't do multitasking, my guess is, that > here "external" utility won't be of any use. But DOS-program could > have it built-in. Could someone tell me

Re: [Freedos-user] A tool for CPU-load measurement

2012-03-28 Thread Zbigniew
2012/3/28, Eric Auer : > Actually you can use FDAPM for that: While the APMDOS > function is active, FDAPM keeps MSDOS POWER compatible > statistics of which percentage of the timer tick "time > slices" contains signs of DOS and the apps being idle. > In such situations, the cpu is halted with HLT

Re: [Freedos-user] A tool for CPU-load measurement

2012-03-28 Thread Eric Auer
Hi Zbigniew, > There are various tools for Windows/Linux, which can display actual > CPU workload. Since DOS doesn't do multitasking, my guess is, that > here "external" utility won't be of any use. But DOS-program... Actually you can use FDAPM for that: While the APMDOS function is active, FDAP

[Freedos-user] A tool for CPU-load measurement

2012-03-28 Thread Zbigniew
There are various tools for Windows/Linux, which can display actual CPU workload. Since DOS doesn't do multitasking, my guess is, that here "external" utility won't be of any use. But DOS-program could have it built-in. Could someone tell me the basic algorithm, which could be used in DOS applicati

Re: [Freedos-user] Catch-all Repository for legacy DOS software

2012-03-28 Thread Jim Hall
I would be happy to have an open, editable directory of legacy DOS software, including screenshots & descriptions. I think that part is a great idea. But we would be unable to host or distribute any files, nor link to sites that have them unless they are original shareware or other distributable so

Re: [Freedos-user] Catch-all Repository for legacy DOS software

2012-03-28 Thread mateusz
Hello, As Jim pointed out, the problem is about copyright of all these oldish DOS applications. Such site as you describe *could* exist, but it should be limited to a list of software (possibly categorized and subcategorized) + one or two screeshots of the application + a description of what the p

Re: [Freedos-user] Catch-all Repository for legacy DOS software

2012-03-28 Thread Jim Hall
Hi. You hit on the sticking point: copyright. It is illegal in many countries (including the US, where FreeDOS is hosted) to distribute non-free, proprietary software in the way you propose. And much of the legacy software you refer to is proprietary. Even hosting copies of these proprietary files

[Freedos-user] Catch-all Repository for legacy DOS software

2012-03-28 Thread Alex
Hi, I have an idea which may prove fruitful for many FreeDOS users: creating a catch-all shared pool of old (or even new) DOS programs. I know, there are already websites with legacy software collections, but what I have in mind would be something better, and more organized, and above all managed