Re: [Freedos-user] fdupdate
Hi, On Mon, Jun 25, 2012 at 4:53 PM, Mateusz Viste mate...@viste-family.net wrote: I do agree with Rugxulo. Just adding my 2cts regarding FDUpdate (I'm the one responsible for creating the monster). BTW, I knew you'd read this, so no disrespect intended (obviously), your work is always appreciated, but it's just a tough situation to handle properly. :-( The idea of FDUpdate was to provide some kind of semi-graphical manager that would allow the average joe to add/update whatever packages in its system. FDUpdate is, however, just a nifty frontend. In the background it calls wget or htget (the downloader backend is configurable) to download the *.zip files into a temp directory, and then it calls FDPKG to install these zip files. I quite quickly lost hope, as the whole packaging work was way more than what I could ever handle on my free time... and without packages, a packager is, well, useless. In other words - don't put any hope into using FDUPDATE for any serious update of your FreeDOS system. FDUPDATE will probably never be useable - unless suddenly there is an army of volunteers that starts massively populating the FDUPDATE repository (which is highly unlikely to ever happen anyway). If only it were even that simple (and no, we don't have a lot of relevant volunteers, sadly). Sometimes an upgrade changes, breaks, or worsens things, whether unintentionally or otherwise. Sometimes files get renamed or split into separate utils. What to do about config files? Probably have to edit those manually anyways. And you'd of course not want to change hardware or software requirements for the worse, at least not without huge warnings. And then you need backups (.EXEs only or whole .ZIPs?). And all of that is IF (doubtful) you have a working packet driver and IF (doubtful) the repo is updated with recent stuff. DJGPP also has (had?) an experimental updater too (pakke), but again, I've never tried it. I always end up manually installing and handling things. Sure, it's more work, but there is no quick fix. Usually I want latest and greatest too (for vanity??), but that's not always appropriate, esp. with compilers or similar tools, so I keep lots of .ZIP archives around in order to re-install or temporarily install for a quick use or whatever. Half my HD usage is probably .ZIP backups (original downloads, I mean, not manual installs compressed). And sometimes I do have several different versions of something installed with various names, e.g. NASM, CWSDPMI. Sometimes I customize them to use a wrapper BLAH.BAT and rename the original .EXE to _blah.exe . You just have to be kinda paranoid and very careful as sometimes things break without realizing why, so you have to eliminate any possible room for error. It's often said that if something works, don't change it! because you're not guaranteed the same stability. In other words, for example, don't upgrade WinXP to Win7 unless you know what you're doing!! :-) These days, I do have write access to the FD iBiblio mirror, and I have tried to keep a lot of little things updated, so it should be okay, but of course I'm easily distracted, and there is always plenty more that could (potentially) be done. Some things change so fast anyways that it's almost pointless to upgrade for every minor point release. But hey, I'm open to suggestions. Perhaps a repo for BASE only would be a good compromise (though most of it is frozen / stable). That's the core stuff that we really need. Maybe UTIL too, but that's less critical. Though how would you handle 3rd-party patches? I was wondering recently whether we need a good place for things like that. But it's easy for things to get lost in the shuffle, so I often want to put things online somewhere so they don't disappear forever. Not always easy. :-/ -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdupdate
Hi, On Mon, Jun 25, 2012 at 11:46 PM, Marco Achury marcoach...@gmail.com wrote: I think official freedos release must be just 2 or 3 floppies, as MSDOS was Boot system + basic drivers and tools (and both, cdrom and floppy image are required). Well, depends on how simplistic you want to make it. I personally would rather have a liveCD than install only, but then again, it's a lot more work, much much more. Just deciding what to put on the floppies is half the job, then deciding how the heck to cram it on in is the other half! And it's hard to update and regenerate everything. I guess Linux distros have things more streamlined, they can generate and rebuild on the fly. We don't have any fancy build servers or scripts (that I know of, anyways). No package manager needed for this base system Assuming someone keeps it updated, which may not always happen! Aditional to this, the community or any interested user can release cdroms with software collections. Such collections may include a package manager or a centralized install menu but is not required. Right, but it's always a lot of work, a lot to keep track of. Simpler to understand and mantain. Any person will install only the apps really need, and the install or update of base system is simple and quick I guess the desire is low due to real gurus already doing it manually. Others probably can't be bothered with the tedium, arcane knowledge, lots of testing, etc. P.S. I'm not saying it's a bad idea, just tedious, somewhat complicated, exhausting without some more volunteers, hard to decide what to put where and how. Plus, honestly, you'll get no sympathy for floppies anymore. That alone is probably the weakest idea (though I'm not totally opposed). And hardware changes so fast, sometimes I wonder if it's worth it. Bah. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdupdate
just about the floppy diskette thing, floppydisk.com sells usb 2.0 diskette drives that plug-and-play auto-recognize and auto-mount, even under my windows 7 64-bit ultimate system. they're advertised as used, but mine that they sent were new. and naturally they sell floppy diskettes for a pretty good price. there's substantial support commercially for using floppies, you just have to find it. eufdp...@yahoo.com eufdp...@yahoo.com eufdp...@yahoo.com eufdp...@yahoo.com eufdp...@yahoo.com From: Rugxulo rugx...@gmail.com To: freedos-user@lists.sourceforge.net Sent: Thursday, June 28, 2012 12:31 PM Subject: Re: [Freedos-user] fdupdate Hi, On Mon, Jun 25, 2012 at 11:46 PM, Marco Achury marcoach...@gmail.com wrote: I think official freedos release must be just 2 or 3 floppies, as MSDOS was Boot system + basic drivers and tools (and both, cdrom and floppy image are required). Well, depends on how simplistic you want to make it. I personally would rather have a liveCD than install only, but then again, it's a lot more work, much much more. Just deciding what to put on the floppies is half the job, then deciding how the heck to cram it on in is the other half! And it's hard to update and regenerate everything. I guess Linux distros have things more streamlined, they can generate and rebuild on the fly. We don't have any fancy build servers or scripts (that I know of, anyways). No package manager needed for this base system Assuming someone keeps it updated, which may not always happen! Aditional to this, the community or any interested user can release cdroms with software collections. Such collections may include a package manager or a centralized install menu but is not required. Right, but it's always a lot of work, a lot to keep track of. Simpler to understand and mantain. Any person will install only the apps really need, and the install or update of base system is simple and quick I guess the desire is low due to real gurus already doing it manually. Others probably can't be bothered with the tedium, arcane knowledge, lots of testing, etc. P.S. I'm not saying it's a bad idea, just tedious, somewhat complicated, exhausting without some more volunteers, hard to decide what to put where and how. Plus, honestly, you'll get no sympathy for floppies anymore. That alone is probably the weakest idea (though I'm not totally opposed). And hardware changes so fast, sometimes I wonder if it's worth it. Bah. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdupdate
I have been blissfully unaware of the packaging requirements for FreeDOS. I update mTCP a few times a year, and I know that is a lot of work to get right. Is there a FAQ or notes on how FreeDOS manages packages? If I can make the mTCP updates easier I will. Mike -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdupdate
Hello, I do agree with Rugxulo. Just adding my 2cts regarding FDUpdate (I'm the one responsible for creating the monster). Since I too often don't have networking in native DOS, I've never relied on FDupdate. Presumably it can (or could) do so, but I don't know the specifics. I don't know if it updates your install or (presumably) only the .ZIP files themselves. The idea of FDUpdate was to provide some kind of semi-graphical manager that would allow the average joe to add/update whatever packages in its system. To do so, FDUpdate downloads a list of available pakages from the FreeDOS repository (the URL of the repository is configurable via a configuration file), then it presents the list in a pseudo graphical menu with some descriptions about every package, and let the user to choose packages to install. FDUpdate is, however, just a nifty frontend. In the background it calls wget or htget (the downloader backend is configurable) to download the *.zip files into a temp directory, and then it calls FDPKG to install these zip files. All this would be great, but - as Rugxulo already noted - there is far too few packages online to make FDUPDATE actually useable in real life. There are also some minor (mostly cosmetic) bugs here and there, which I didn't ever cared to fix, as I quite quickly lost hope, as the whole packaging work was way more than what I could ever handle on my free time... and without packages, a packager is, well, useless. Yes, you pretty much have to install or update things manually. I hate to say it, but FDupdate seems like a failed experiment. Indeed. 'Failed experiment' is a term that describes FDUpdate quite accurately. Altough I prefer to think about it as a 'proof of concept' work ;) In other words - don't put any hope into using FDUPDATE for any serious update of your FreeDOS system. FDUPDATE will probably never be useable - unless suddenly there is an army of volunteers that starts massively populating the FDUPDATE repository (which is highly unlikely to ever happen anyway). Ciao, Mateusz -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdupdate
I think official freedos release must be just 2 or 3 floppies, as MSDOS was Boot system + basic drivers and tools (and both, cdrom and floppy image are required). No package manager needed for this base system Aditional to this, the community or any interested user can release cdroms with software collections. Such collections may include a package manager or a centralized install menu but is not required. Simpler to understand and mantain. Any person will install only the apps really need, and the install or update of base system is simple and quick -- -- +-+-+-+-+-+-+-+ Marco A. Achury Tel: +58-(212)-6158777 Cel: +58-(414)-3142282 Skype: marcoachury http://www.achury.com.ve El 25/06/2012 05:23 p.m., Mateusz Viste escribió: Hello, I do agree with Rugxulo. Just adding my 2cts regarding FDUpdate (I'm the one responsible for creating the monster). Since I too often don't have networking in native DOS, I've never relied on FDupdate. Presumably it can (or could) do so, but I don't know the specifics. I don't know if it updates your install or (presumably) only the .ZIP files themselves. The idea of FDUpdate was to provide some kind of semi-graphical manager that would allow the average joe to add/update whatever packages in its system. To do so, FDUpdate downloads a list of available pakages from the FreeDOS repository (the URL of the repository is configurable via a configuration file), then it presents the list in a pseudo graphical menu with some descriptions about every package, and let the user to choose packages to install. FDUpdate is, however, just a nifty frontend. In the background it calls wget or htget (the downloader backend is configurable) to download the *.zip files into a temp directory, and then it calls FDPKG to install these zip files. All this would be great, but - as Rugxulo already noted - there is far too few packages online to make FDUPDATE actually useable in real life. There are also some minor (mostly cosmetic) bugs here and there, which I didn't ever cared to fix, as I quite quickly lost hope, as the whole packaging work was way more than what I could ever handle on my free time... and without packages, a packager is, well, useless. Yes, you pretty much have to install or update things manually. I hate to say it, but FDupdate seems like a failed experiment. Indeed. 'Failed experiment' is a term that describes FDUpdate quite accurately. Altough I prefer to think about it as a 'proof of concept' work ;) In other words - don't put any hope into using FDUPDATE for any serious update of your FreeDOS system. FDUPDATE will probably never be useable - unless suddenly there is an army of volunteers that starts massively populating the FDUPDATE repository (which is highly unlikely to ever happen anyway). Ciao, Mateusz -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] fdupdate
Hi, let's continue where I stopped a year ago. ;) I tried fdupdate to update my 1.1 installation. But, the DOS PC is still offline. I don't have a spare network cable. Is there any way to tell fdupdate/fdpkg where to find the files locally? I believe there are a lot of packages that are not yet in the 1.1 format? Do I have to install them manually? to, mh... maintain the installed software, ie add, remove? fdpkg? how does it know here to fetch the packages from? thanks, Jan -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDUPDATE and the 486...
On Sat, 2009-04-25 at 16:35 +0200, Eric Auer wrote: Hi, Has anyone gotten fdupdate to work with a 486? I lost the link to fdupdate v0.55 and the instructions on how to use it in fdupdate v0.54. If using a 486 is the problem because of a bug in the math coprocessor or something similar, that would be nice to know. I've noticed that I get a C prompt back after the crash if I say 387=no in autoexec.bat. I haven't confirmed this, I should test with and without it to confirm. It seems to be true though. Please check if this is the case. Another thing is that you can put em387.dxe or wemu387.dxe or emu387.dxe or so...? The file seems to be emu387.dxe in djdev203.zip ... Somebody in the freebasic forum said: Anyways, in pure DOS (not Windows) I think you can disable the FPU detection for DJGPP by doing set 387=n and set EMU387=c:\mydir\wmemu387.dxe. It should work. I guess other options are putting the dxe in your PATH or in the current directory or the directory where FDUPDATE is etc. Eric I fried all my 486 processors and it makes more sense to fix a Pentium III up then it does to try and cobble together another 486. I'm getting out of the 486 business, so I may never find out if fdupdate will work on one. -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDUPDATE and the 486...
Hi, Has anyone gotten fdupdate to work with a 486? I lost the link to fdupdate v0.55 and the instructions on how to use it in fdupdate v0.54. If using a 486 is the problem because of a bug in the math coprocessor or something similar, that would be nice to know. I've noticed that I get a C prompt back after the crash if I say 387=no in autoexec.bat. I haven't confirmed this, I should test with and without it to confirm. It seems to be true though. Please check if this is the case. Another thing is that you can put em387.dxe or wemu387.dxe or emu387.dxe or so...? The file seems to be emu387.dxe in djdev203.zip ... Somebody in the freebasic forum said: Anyways, in pure DOS (not Windows) I think you can disable the FPU detection for DJGPP by doing set 387=n and set EMU387=c:\mydir\wmemu387.dxe. It should work. I guess other options are putting the dxe in your PATH or in the current directory or the directory where FDUPDATE is etc. Eric -- Crystal Reports #45; New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty#45;free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] FDUPDATE and the 486...
On Monday 20 April 2009 00:08 (CEST), Michael Robinson wrote: Has anyone gotten fdupdate to work with a 486? I lost the link to fdupdate v0.55 and the instructions on how to use it Hi, You didn't lose it, it simply never existed :) I sent you a beta FDUPDATE version with support for the HTGET downloader (that would finally confirm wheter it is a problem with launching third-party downloaders or not) several days ago. I have resent it to you right now. If using a 486 is the problem because of a bug in the math coprocessor or something similar, that would be nice to know. Personally, I don't really believe in that, 'cause you said that it crashes when you try to apply the first update. That means that FDUPDATE has already worked correctly for a long time (relatively), as it 1) launched itself 2) launched an instance of the downloader 3) the downloader downloaded the index file of the repository 4) FDUPDATE compared the repo index with the local LSM database. Of course, I could be plainly wrong :-) Regards, Mateusz Viste -- You'll find my public OpenPGP key at http://www.viste-family.net/mateusz/pub_key signature.asc Description: This is a digitally signed message part. -- 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
[Freedos-user] FDUPDATE and the 486...
Has anyone gotten fdupdate to work with a 486? I lost the link to fdupdate v0.55 and the instructions on how to use it in fdupdate v0.54. If using a 486 is the problem because of a bug in the math coprocessor or something similar, that would be nice to know. I've noticed that I get a C prompt back after the crash if I say 387=no in autoexec.bat. I haven't confirmed this, I should test with and without it to confirm. It seems to be true though. -- 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
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
[Freedos-user] fdupdate won't work on my 486...
I have a DTK 486 with a very simple AMI bios and on it a Dlink DE220PT nic on IRQ 12 IO 0x240. Arachne works fine, but fdupdate crashes. It crashes regardless of whether or not I choose to update a package. I'm using the crynwr packet collection ne2000 driver. I get an error about 2 near fnodes sometimes if that helps at all. The beta driver from Intel for their e100 works with fdupdate on my Pentium 4 system where I am using the 0.54 version of fdupdate on both my 486 and my Pentium 4. I have tried loading freedos on my 486 without drivers, that didn't help. This 486 has four serial ports, 2 parallel ports, and a sound blaster value card. Short of pulling cards out, I'm not sure how to isolate this problem. I was wondering if anyone else has had problems using the crynwr ne2000 driver with fdupdate? It would help a lot if freedos update were smart enough to exit with a meaningful error message that tells me what is actually wrong. Obviously it crashes after the do you want to update question is answered, so what is it doing at that point? I wish there was a debugger for freedos update that would show me the actual instruction that fails. Maybe there is some caching scheme that requires a special exception, but how would I find out? -- Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdupdate
I could get it to work under vmware with wget believe it or not, but I haven't gotten it to work on real hardware even with curl. Another problem I've noticed is that fdupdate doesn't seem to record the new version of a package that it has updated. My 486 is passing memtest with flying colors. It crashes every time I try to apply or skip an update. What is the fallback address? It doesn't seem to be right. Michael Robinson - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdupdate
On Fri, 2008-02-15 at 21:00 +0100, Mateusz Viste wrote: On Friday 15 February 2008, robinson-west user wrote: I could get it to work under vmware with wget believe it or not, but I haven't gotten it to work on real hardware even with curl. Do your real hardware can run anything more than the bare FreeDOS kernel? I mean games, and more advanced software (DPMI / protected mode, etc...). Maybe the problem is outside FDUPDATE / wget / curl... Bad memory, incorrect EMM386 settings, etc... Do you tried using the tested wget binary? (http://mateusz.viste.free.fr/fdupdate/wgetx.zip) Why wouldn't the copy of wget packaged with freedos 1.0 work? It does on the emulated installation of freedos that I got fdupdate to work with. Yes my real hardware can run more than the bare freedos kernel. I've played ultima underworld and shadowcaster no problem on this machine. I'm not using EMM386, I'm using Jemm5.70 on the 486. The fact that fdupdate doesn't want to work on my 486, but other programs which use extended memory do, is quite odd. No, FDUDPATE doesn't keep track of installed / updated software. That's the job for the application's LSM file. If the application have a LSM with an incorrect version record, FDUPDATE will be fooled. What problem do you exactly encounter with versionning? Well, on the emulated system where fdupdate works it didn't realize what it had updated the second time I ran it. What do you mean by with flying colors? If you have a bad mem, wget, curl, fdupdate, and any other DPMI application may have big problems, as it is using memory 1 MB... Unless the memory bank itself is damaged somehow, this doesn't appear to be a memory problem. Memtest has been run multiple times and every time the memory has come up good. I wonder what the difference is between a vmware environment and real hardware? If I could figure that out, I might determine why my 486 crashes. Michael C. Robinson - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdupdate
Hi Michael, Do you tried using the tested wget binary? (http://mateusz.viste.free.fr/fdupdate/wgetx.zip) Why wouldn't the copy of wget packaged with freedos 1.0 work? It is just a piece of the puzzle: If using another version of wget solves the problem, we know more. machine. I'm not using EMM386, I'm using Jemm5.70 on the 486. Ironically, Jemm is less tested than emm386 on such old hardware. fact that fdupdate doesn't want to work on my 486, but other programs which use extended memory do, is quite odd. The most common cause of crashes with emm386 or jemm386 is probably not related to EMS or XMS but to UMB. Background is that the area between 640k and 1 MB can be used for lots of different things, and any emm386 variant can have some problems finding out which parts of the area can be used by DOS and which cannot. If you could test FDUPDATE with only himem but not emm386 / jemm386 loaded and if you find that this solves the problem, we know more. Well, on the emulated system where fdupdate works it didn't realize what it had updated the second time I ran it. For some packages or for all of them? Sounds like a bug... I wonder what the difference is between a vmware environment and real hardware? If I could figure that out, I might determine why my 486 crashes. The difference is in the hardware ;-). You use different network drivers and different areas of memory are useable (or rather not) for UMBs, for example. You might also be running other drivers, like mouse or sound drivers, and of course the BIOS. I know one example where some BIOS- supported onboard sound VIA/SB16 DOS compatibility mode made the 3com DOS network driver unstable, but I do not know why exactly it happened. Probably IRQ / DMA issues. Solution was to disable the SB16 mode in BIOS setup, as there was no need to have SB16 sound in DOS on that PC. Eric - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdupdate
Hi! FDUPDATE v0.53 is out! What's new in v0.53 [14 Feb 2008]: - Added configuration for the download command (was hardcoded to wget), - FDUPDATE doesn't switches to the %TEMP% directory anymore, - Changed the configuration file format, - Added german translation. http://mateusz.viste.free.fr/dos/en/download.php?plik=fdupdate bye, Mateusz Viste - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] fdupdate
ulimit(fdupdate.tab) EIO error input/output error... My freedos update locks up and I've noticed something similar to the above error. Is there supposed to be a ulimit executable? Is there supposed to be an installation of djgpp for wget to work? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdupdate
On Wednesday 13 February 2008, robinson-west user wrote: ulimit(fdupdate.tab) EIO error input/output error... Wow, that's an error I've never seen... My freedos update locks up and I've noticed something similar to the above error. Is there supposed to be a ulimit executable? No, there's no ulimit executable, as ulimit is (as far as I know) only found in Linux systems... Is there supposed to be an installation of djgpp for wget to work? No, you don't need DJGPP to get wget working, as it is already compiled. You only need CWSDPMI (or any other DPMI environment). When exactly do you get the error? Is the bug manifesting each time you run FDUPDATE? What are your startup files (autoexec config)? Where do you got your wget copy from? Mateusz Viste - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdupdate
I'm on a 486 DX2 66 EISA bus, no VLB. 20 megs of SIMM ram, 30 pin. Is there a copy of memtest86+ for freedos, it would be silly if this turned out to be a bad memory problem. autoexec.bat: --- @echo off if not %config% == 4 SET CTCM=C:\CTCM if not %config% == 4 C:\CTCM\CTCU /S SET dosdir=C:\FDOS REM C:\FDOS\BIN\BANNER2 REM C:\FDOS\BIN\BLACKOUT set PATH=%dosdir%\bin;c:\commwp\wp60 set NLSPATH=%dosdir%\NLS set HELPPATH=%dosdir%\HELP set temp=%dosdir%\temp set tmp=%dosdir%\temp SET BLASTER=A220 I2 D1 H5 P330 REM if not %config%==4 c:\fdos\bin\shsucdx.com /D:fdcd0001 REM if not %config%==4 LH VIAUDIO REM if not %config%==4 LH VIAFMTSR REM if not %config%==4 LH FDAPM APMDOS if %config%==2 LH SHARE SET autofile=C:\autoexec.bat alias reboot=fdapm warmboot alias halt=fdapm poweroff SET CFGFILE=C:\fdconfig.sys echo type HELP to get support on commands and navigation echo. echo Welcome to FreeDOS echo. if not %config%==4 mouse if not %config%==4 C:\FDOS\drivers\net\crynwr\ne2000 0x60 12 0x280 SET WATTCP.CFG=%DOSDIR%\BIN lh doslfn set PATH=%PATH%;%DOSDIR%\emacs set PATH=%PATH%;%DOSDIR%\SETEDIT SET VIM=C:\FDOS\VIM SET PATH=%PATH%;%DOSDIR%\vim\vim70 SET PATH=%PATH%;%DOSDIR%\fbc call %DOSDIR%\watcom\setvars.bat SET PATH=%PATH%;%DOSDIR%\PACIFIC\BIN REM if not %config%==4 @SET SCSI_DRIVER = C:\IOMEGA REM if not %config%==4 @SET SCSI_UTILITY = C:\IOMEGA SET PATH=%PATH%;d:\iomega REM BLACKOUT REM MODE CO80 - fdconfig.sys: - !COUNTRY=001,437,C:\FDOS\BIN\COUNTRY.SYS !SET lang=EN !LASTDRIVE=F !BUFFERS=40 !FILES=100 !DOS=HIGH,UMB !DOSDATA=UMB !set dircmd=/ogn /4 !MENUCOLOR=7,5 MENUDEFAULT=2,5 MENU 1 - Load FreeDOS with EMM386, no EMS (most UMBs), max RAM free MENU 2 - Load FreeDOS with JEMM386+EMS and SHARE MENU 3 - Load FreeDOS including HIMEM XMS-memory driver MENU 4 - Load FreeDOS without drivers DOS=HIGH,UMB REM 123?DEVICE=C:\FDOS\BIN\XCDROM.SYS /D:fdcd0001 123?DEVICE=C:\FDOS\HIMEMX.EXE 1?DEVICE=C:\FDOS\BIN\EMM386.EXE NOEMS X=TEST 2?DEVICE=C:\FDOS\JEMM386.EXE 123?DEVICE=C:\CTCM\CTCM.EXE REM 123?DEVICEHIGH=C:\FDOS\bin\xdma.sys REM 123?INSTALL=C:\FDOS\BIN\BLACKOUT.EXE REM 123?INSTALL=C:\FDOS\BIN\BANNER1.COM 123?DEVICEHIGH=C:\FDOS\BIN\MORESYS.SYS SHELLHIGH=C:\FDOS\bin\command.com C:\FDOS\bin /E:1024 /P=C:\autoexec.bat 4? - The exact error message for utime is: utime(fdupdate.tab): Input or output error (EIO) At this point a window pops up asking me to update debug. If I press y, the computer crashes. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] fdupdate 0.51 hangs computer
On Friday 28 December 2007, someone wrote: I am running freedos on a DTK 486 DX2-66 board with AMI bios. It crashes when I type y to apply any update. gs: sel=00bf base= limit=0010 ss: sel=0033 invalid App stack: [000f06c8..000706cc] Exceptn stack: [000705f8..0006e6b8] Sorry for the late answer... There is very little chances that the bug comes from FDUPDATE, as there is no potentially dangerous code in it. I cannot really help there, as I'm not an expert on such low level stuff. Maybe Eric or Japheth would know what those hex numbers are about... (?) FDUPDATE 0.51 is using WGET to download data from internet, and I think that the bug is sourcing from WGET or your DPMI environement. Do WGET as a stand-alone application works for you? Are you using the latest EMM / JEMM driver? Optionally, you should install CURL and try the FDUPDATE v0.52 (you can configure it to use CURL instead of WGET). Regards, Mateusz Viste - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] fdupdate 0.51 hangs computer
I am running freedos on a DTK 486 DX2-66 board with AMI bios. It crashes when I type y to apply any update. gs: sel=00bf base= limit=0010 ss: sel=0033 invalid App stack: [000f06c8..000706cc] Exceptn stack: [000705f8..0006e6b8] Call frame traceback EIPS: 0xad0f 0x0001ce94 0x0001feb3 0x00018392 0xdf7d 0xef26 0x6650 0x33e5 0x4fd3 0xcf34 General Protection Fault in RMCB at eip=14df; flags=3002 eax=02150001 ebx=1246 ecx= edx=000706ff esi=1b3a edi=03cc ebp= esp=03b8 cs=2b ds=3b es=a7 fs=33 gs=0 ss=a7 error=00ac c:\ PANIC: more than two near fnodes requested at the same time! System halted This message was sent using IMP, the Internet Messaging Program. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
