Re: [Freedos-user] FDUPDATE crash
Hello, 2009/4/9 Eric Auer e.a...@jpberlin.de: MS DOS 6.22 has a tool that graphically shows a representation of memory, I think it was called msd. Is there an equivalent for freedos? There are various tools for that, a nice one is Quarterdeck MFT Manifest which is now freeware. Unfortunately I cannot find any URL as Quarterdeck got bought by Symantec. FreeDOS replacement for MSD used to be COMPINFO, but I ignore the status of that project. Aitor -- Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDUPDATE crash
Oops, just sent an empty reply... and more than 2 near fnodes does not tell me what crashed. It might mean you use an old kernel which leaves file handles open when access is aborted due to an error... I do not think your RAM config is a problem. Maybe your copy of FDUPDATE or WGET is compiled for Pentium CPU? Loading HIMEM sounds useful yes. I would not load EMM386, though. Serial port IRQ should not be an issue, but you can try without CUTEMOUSE if you think it makes a difference. MS DOS 6.22 has a tool that graphically shows a representation of memory, I think it was called msd. Is there an equivalent for freedos? There are various tools for that, a nice one is Quarterdeck MFT Manifest which is now freeware. Unfortunately I cannot find any URL as Quarterdeck got bought by Symantec. My isa nic is a DE220PT in non pnp mode, has anyone had problems using these under freedos? I think ISA network cards are harder to get to run stable and harder to configure than PCI network cards in DOS... Please note that ssh2dos works. Nice :-) Every network application except for fdupdate seems to work okay. Sounds like FDUPDATE has a problem with old CPU, I wonder in which language it is written... What is an fnode? What does a message that more than 2 near fnodes are opened mean? F-Nodes store extra information about open files in FreeDOS. There is a cache for the two most recently used F-Nodes, so you get an error if you try to use three F-Nodes at exactly the same moment. Maybe you have a problem which left an F-Node dangling or you have some software which tries to access files in the background but fails to do so in compatible way for example while the int 21 kernel handler is busy. Please someone, try fdupdate v0.54 on a real 486 with 30 pin memory, maybe you'll run into the same problem that I am having. Rugxulo? :-) Eric -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDUPDATE crash
I was wrong about wget not crashing, it just took it a long time to crash running it on it's own. Is the kernel going to be reworked anytime soon to remove this fnode concept? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDUPDATE crash
On Fri, 2009-04-03 at 17:12 +0200, Mateusz Viste wrote: On Friday 03 April 2009 16:08, Michael Robinson wrote: When I run fdupdate, it crashes with a 2 near fnodes error. Hi, Please define the crash. When exactly is it happening? When FDUPDATE is starting itself, or when it run wget to retrieve the repository list? That's a verry important information, as it will tell us wheter it's really a FDUPDATE crash, or wget... Does wget itself works fine (can you retrieve any file with it)? As for FDUPDATE, it's a very simple program written in FreeBASIC, there is no Network handlers at all, just the gui + the wget sublauncher. Another test would consist of using the CURL handler instead of the wget's one. Obviously you will have to install CURL, and modify the FDUPDATE configuration file to tell it to use CURL instead of wget... I wish I knew exactly what is causing the crash. Please give us the informations I asked for, it will be a good start :) Best regards, Mateusz Viste I'm not certain about what is crashing. Changing to curl makes no difference at all. This works on my Pentium 4, so I suspect there is something specific to my 486 that is causing the problem. I wish the crash message was more descriptive. A dump of the processor's registers and more than 2 near fnodes does not tell me what crashed. Did command.com crash? Was there an invalid memory reference because I need to exclude a certain region and don't know about it? If someone else has a real DTK 486 DX2-66 that uses 30 pin memory, I'd appreciate an attempt by them to reproduce this problem. I have tried running only fdapm, ne2000, mouse, DOSLFN, command, and system. I still get kernel panic, system halted. I have 20 megs of ram, memtest says that the memory is fine. Could the order I have the chips plugged in in be a problem? Which bank needs to be 1 meg chips? -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDUPDATE crash
I'm not certain about what is crashing. Changing to curl makes no difference at all. This works on my Pentium 4, so I suspect there is something specific to my 486 that is causing the problem. I wish the crash message was more descriptive. A dump of the processor's registers and more than 2 near fnodes does not tell me what crashed. Did command.com crash? Was there an invalid memory reference because I need to exclude a certain region and don't know about it? If someone else has a real DTK 486 DX2-66 that uses 30 pin memory, I'd appreciate an attempt by them to reproduce this problem. I have tried running only fdapm, ne2000, mouse, DOSLFN, command, and system. I still get kernel panic, system halted. I have 20 megs of ram, memtest says that the memory is fine. Could the order I have the chips plugged in in be a problem? Which bank needs to be 1 meg chips? While fdupdate doesn't work, I am retrieving a file off of an ftp server using wget. I don't think wget is crashing. It is running awfully slow though, could be because I don't have himem loaded. One thing I'm wondering about, does freedos work when serial ports are overlapped? The standard thing to do for 4 serial ports is to do com1 and com3 on irq 4 with com2 and com4 on irq 3. More than 2 near fnodes, does that have something to do with overlapping serial ports? Please note that I've tried dos memtest and it isn't showing any memory errors. MS DOS 6.22 has a tool that graphically shows a representation of memory, I think it was called msd. Is there an equivalent for freedos? My isa nic is a DE220PT in non pnp mode, has anyone had problems using these under freedos? Please note that ssh2dos works. Every network application except for fdupdate seems to work okay. What is an fnode? What does a message that more than 2 near fnodes are opened mean? Please someone, try fdupdate v0.54 on a real 486 with 30 pin memory, maybe you'll run into the same problem that I am having. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
