At 10:03 PM 9/23/2004 +0200, Bernd Blaauw wrote:
Eric, other people,
the HTMLHELP problem I'm experiencing is the following:
HTMLHELP crashes if called twice and HIMEM is loaded.
steps to reproduce:
1) download http://fdos.org/ripcord/beta9-final/test/helpfile.img (1.44MB)
2) write to diskette (raw
At 12:41 PM 9/24/2004 +1200, Bart wrote:
Tom has of course every reason to be pissed -- and in the latest emm386 he
released there *is* an lsm file. The problem really stems from this I think:
Moral of the story:
1. please do not make updates to appear like full versions
2. do not change the .lsm
Bernd Blaauw wrote:
Eric, other people,
the HTMLHELP problem I'm experiencing is the following:
HTMLHELP crashes if called twice and HIMEM is loaded.
At least it loads for you, on my test computer, choosing
option one (with himem) locks my computer (have to press
the reset button or power off/on) s
tom ehlert escreveu:
seriously - would you use AnyDOS for your everyday work ?
I do. For devellopent. But my clints do it 24/7...
(machices are up to P4, graphics mode and database)
do you think anyone else does ?
Not very much ;-)
Alain
---
This
Tom has of course every reason to be pissed -- and in the latest emm386 he
released there *is* an lsm file. The problem really stems from this I think:
on www.freedos.org you can read:
Michael Devore wrote: Uploaded to ftp://ftp.devoresoftware.com/downloads
are the files emm386.zip and himem.zip
Hi!
23-Сен-2004 18:49 [EMAIL PROTECTED] (tom ehlert) wrote to Aitor Santamarэa
Merino <[EMAIL PROTECTED]>:
>> (3) XMS UMB functions are not supported. I just wonder if MS-HIMEM
>> implements them: now that HIMEM is quite machine specific, perhaps this
>> is the way Microsoft implement their "UMBP
Take a look at almost any linux package and it will
contain a man page. This works -- it is the done thing
in Linux. In contrast, we have a single, centralised
collection of html pages, and I can hardly blame
maintainers for not emailing me html files. I
apologise for being more harsh than is neces
Hi!
21-Сен-2004 21:02 [EMAIL PROTECTED] (Bernd Blaauw) wrote to
[EMAIL PROTECTED]:
BB> Michael, please look at the date of Arkady's email. The sourceforge
BB> server seems to have hold this email for 2.5 months!!!
BB> I received 3 emails which were hold.
Unfortunately, looks like it was los
Hi!
21-Сен-2004 13:41 [EMAIL PROTECTED] (Michael Devore) wrote to
[EMAIL PROTECTED]:
MD> At 07:03 PM 7/5/2004 +0400, Arkady V.Belousov wrote:
>> Michael, what about testing edition of EMM386 (which fills last para
>>of included area by specific values)?
MD> Maybe la
Hi,
tom ehlert escribió:
Hello Aitor,
Yes, but my question is how does kernel know where the device header
starts? "MZ" doesn't look like a correct pointer to the next device
driver inside the file...
'MZ' is only an envelope around 'the real thing', specifying e.g.
minimum space required,
Hi!
23-Сен-2004 12:26 [EMAIL PROTECTED] (Robert Platt) wrote to
[EMAIL PROTECTED]:
RP> What are the best free tools for developing C in FreeDOS?
OpenWatcom.
RP> For instance, I really need a C (rather than
RP> assembly) debugger for a large project like HTMLHelp.
Present (though, I n
Hi Tom!
> seriously - would you use AnyDOS for your everyday work ?
Well we both use DOS for some WORK. In my case it is real-time
data processing. DOS is not optimized for that but as it is
single-tasking, as long as you do not wait for the kernel, you
have 100% CPU. So you can place kernel cal
Hello Aitor,
> Yes, but my question is how does kernel know where the device header
> starts? "MZ" doesn't look like a correct pointer to the next device
> driver inside the file...
'MZ' is only an envelope around 'the real thing', specifying e.g.
minimum space required, START POINT, size of env
Hello Eric,
> That would be a pity. Tom can be very technical sometimes,
> like 'do not suggest a feature, write the code and I will
> tell you if it will become part of HIMEM...'. Sometimes he
> can even be harsh.
that's true - and I don't apologize ;)
> But there is also little visible interes
Hi,
tom ehlert escribió:
Hello Aitor,
(1) There is a /TEST option (not present in MS-HIMEM), and at the same
time, MS-HIMEM implements a /TESTMEM:ON|OFF option to do this (defaults
to ON). /TEST does a nice test by allocating, filling, testing,
resizing,. to determine the reliability of the
Eric, other people,
the HTMLHELP problem I'm experiencing is the following:
HTMLHELP crashes if called twice and HIMEM is loaded.
steps to reproduce:
1) download http://fdos.org/ripcord/beta9-final/test/helpfile.img (1.44MB)
2) write to diskette (rawrite, diskcopy, winimage, dd, etc.)
3) boot the d
Hi Tom, Robert, Bernd,
a collected reply to all mails in the thread so far...
> Tom wrote:
> > > Maintaining is more than just having your
> > > fun writing code.
> > well - I certainly know better then you.
> ...
> One less. I resign as maintainer of the help system.
That would be a pity. Tom c
I was suprised by how many people seemed sympathetic,
even private emails, so I shan't give up html help
completely.
I'll certainly hand over the maintaining of the
help.exe browser and source. As Bernd suggests, we'll
split this from the html files.
Now I still think someone else might be better
Hello Aitor,
> (1) There is a /TEST option (not present in MS-HIMEM), and at the same
> time, MS-HIMEM implements a /TESTMEM:ON|OFF option to do this (defaults
> to ON). /TEST does a nice test by allocating, filling, testing,
> resizing,. to determine the reliability of the extended memory.
>
Hi there,
I have been reading the HIMEM sources, and have these questions. I am
grateful to whoever can say something about these questions (which as
usual are plain questions with no critisizing):
(1) There is a /TEST option (not present in MS-HIMEM), and at the same
time, MS-HIMEM implements
Robert Platt schreef:
How many times have I asked on these lists for
assistance? Sure, most programs only need one
developer, but large projects like the kernel and
command.com have many developers. How many people work
on the help file system?
Hi Rob, sad to see you go, but thanks for all your
Hello Robert,
> Tom wrote:
>> > Maintaining is more than just having your
>> > fun writing code.
>> well - I certainly know better then you.
> What a sage comment. I don't work with people that
> make gutter comments like that.
> You say this about me, yet you know full well that I
> re-wrote th
×, 23 ××× 2004, 16:40, ×× ××× Aitor
SantamarÃa Merino:
> Eric Auer escribiÃ:
> >That would be a bug then. Turbo C is for DOS, so use it in DOSEmu,
> >not in Wine.
>
> According to the wine RPM description, Wine can do Win16 and DOS apps
> too. But I don't know much about their DO
Tom wrote:
> > Maintaining is more than just having your
> > fun writing code.
> well - I certainly know better then you.
What a sage comment. I don't work with people that
make gutter comments like that.
You say this about me, yet you know full well that I
re-wrote the entire help html files --
On Wed, 22 Sep 2004 15:00:37 -0300, you wrote:
Hi Alain,
>have a look at XXCOPY. (if you don find it I should have a copy) but it
>is shareware...
Try Tarmo Toikkanen's "Controlled Copy" (CC).
I've emailed him, now it's free to use but he's not releasing source
code.
>Spinrite did that in in o
Eric Auer escribió:
That would be a bug then. Turbo C is for DOS, so use it in DOSEmu,
not in Wine.
According to the wine RPM description, Wine can do Win16 and DOS apps
too. But I don't know much about their DOS virtualisation.
Aitor
---
This S
Hi Robert,
> Only problem is -- Turbo C++ 3.0 for DOS doesn't seem
> to work in FreeDOS or Wine.
That would be a bug then. Turbo C is for DOS, so use it in DOSEmu,
not in Wine. If it does not work in plain FreeDOS and does not work
in (properly configured - read the documentation) DOSEmu, then y
Hello Robert,
> Try writing the lsm files yourself. You're the
> maintainer -- or certainly the last person to make
> changes.
I wrote one myself - and published it.
and the current one on freedos.org/software is not the one I wrote.
and however changed copying liocense to 'open source(public)'
c
Try writing the lsm files yourself. You're the
maintainer -- or certainly the last person to make
changes.
NOW you tell people the LSM files are wrong. Why not
provide the LSM files yourself in the first place? Who
can guess the origin of YOUR code?
Rather than flame the list and make FreeDOS loo
After my hard drive busted a few months ago, I decided
to install Linux and leave off Windows altogether.
Only problem is -- Turbo C++ 3.0 for DOS doesn't seem
to work in FreeDOS or Wine.
What are the best free tools for developing C in
FreeDOS? For instance, I really need a C (rather than
assem
30 matches
Mail list logo
