Re: [Freedos-user] pre 1.0 version
Hi all, Thanks for the suggestions. I tried copying the old (0.9) KERNEL.SYS and COMMAND.COM onto the drive, but no luck, the same error on trying to compile. I had downloaded FreeDOS1.0 from freedos.org, but it only had the 2036 kernel. I'm reluctant to do a full install, as it will knock out my grub dual boot to Linux and I'll have to redo that. I'm running Borland C++ version 2.0 as the compiler. I'll keep plugging away and let you all know if anything happens. Jim -- Increase Visibility of Your 3D Game App Earn a Chance To Win $500! Tap into the largest installed PC base get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] pre 1.0 version
Hi again, On 11/25/10, Jim Lemon j...@bitwrit.com.au wrote: Thanks for the suggestions. I tried copying the old (0.9) KERNEL.SYS and COMMAND.COM onto the drive, but no luck, the same error on trying to compile. So it may not actually be a regression in the kernel itself then. I had downloaded FreeDOS1.0 from freedos.org, but it only had the 2036 kernel. I'm reluctant to do a full install, as it will knock out my grub dual boot to Linux and I'll have to redo that. You can get various kernels separately and replace it manually (if you think that'll help). Note that it's just a simple copy and rename, there is no install necessary since you already have an active FAT partition and boot sector. 2036: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/pkgs/sysx.zip 2037: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.0/pkgs/unstablx.zip 2038: http://sourceforge.net/projects/freedos/files/Kernel/2038/kernel2038-fat32-binary.zip/download 2039: http://sourceforge.net/projects/freedos/files/Kernel/2039/ke2039_86f32.zip/download I'm running Borland C++ version 2.0 as the compiler. I'll keep plugging away and let you all know if anything happens. Well, I don't know what to tell you honestly. You'll just have to keep trying unless somebody somewhere also has BC++ 2.0 and is willing to test. Since it's not freeware nor sold any longer plus few volunteers, that might complicate things. Sad but true. :-( P.S. Turns out that it was Turbo C++ 2.0 that never existed, but Wikipedia does indeed list a Borland C++ 2.0 (1991). Annoying and confusing. EDIT: It's been a while (months) since I last used any Turbo C/C++ compiler to build anything. Mostly that's because of hardware issues (laptop dying, etc) and lack of need. But IIRC, they use a .CFG file to store paths to compiler. So perhaps your config file was correct for one computer but wrong for another (different paths). You might want to double-check that. And/or you should use a tool like KGB to trace exactly what files it's trying to use, so you can see exactly what it's expecting and where. http://www.resoo.org/docs/dos/free_software/system.htm#functrace -- Increase Visibility of Your 3D Game App Earn a Chance To Win $500! Tap into the largest installed PC base get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] pre 1.0 version
On 11/20/2010 12:14 AM, Rugxulo wrote: ... What year and model and cpu? Just curious. And what exactly doesn't work, it won't turn on?? DELL Latitude XP 475D Plugged it in, hit the switch and nothing. No lights, no sound, nothing. It has been going for years and I only kept it for the last year or two to compile C programs under FreeDOS. ... Hmmm, I know I read your recent message, but you were kinda vague. What exactly doesn't work? What error message does it give? What version of Borland C? And most importantly, what kernel are you using? (try ver /r) It's most likely an issue on your end since I haven't heard of any Borland tools having issues except maybe Turbo C 3.0, but I think they fixed that in later kernels. So you should definitely try kernel 2038 (instead of 2036 from FD 1.0) or even unstable 2039. ver -r (or -R, despite the help info) gives FreeCom version 0.84 pre2 XMS_Swap [Aug 28 2006 00:29:00] I'm pretty sure that it's the version because I had been compiling various C programs in the Borland C IDE for years and as soon as I upgraded, it stopped compiling. I just tried it again with a program that I know would compile and got: Undefined symbol _EGA_VGA_driver in module STRZ2.C When it first happened, the undefined symbol would be whatever library or object file was to be linked in first. I checked the paths, checked that the libraries and object files were there, tried to manually compile and link, tried stupid things like copying the object files into the code directory, etc. It was then that I copied a minimal Borland C setup to the old DELL that still had the previous FreeDOS version and ... it worked! As I had to get the program compiled and was able to, I didn't complain and thought that I would eventually be able to fix the problem. EDIT: Does this link help? But I'd rather you didn't use this and instead told us more specifically what's wrong. Most FreeDOS users don't use Borland tools except (freeware) TC++ 1.0.1 or TC 2.01 or TP 5.5. http://ftp.usf.edu/pub/freedos/files/distributions/official.old/0.9sr2.BETA/ Thanks, I'm downloading it now. P.S. Worst case scenario, you could always use OpenWatcom, right? It's far better than Borland anyways (and official compiler for FD, natch). My choices appear to be three: Downgrade to pre 1.0 FreeDOS and hope that I can once again do the development work on this PC. This is the best option, as I don't do a lot of this anymore, and I wouldn't have to change anything. Move from Borland C to Watcom. I agree with your opinion about Watcom, but I have an awful lot of code that depends upon Borland graphics drivers (and probably a few other Borland things), and I don't want to rewrite it. So it would be a worst case scenario. I would rather port the whole thing to Linux and run it under Real Time Linux. Fix whatever is going wrong with the present setup. The error messages, as explained above, are those awful sort that say X isn't there and when you look, X is there. My guess is that there was some subtle change in a DOS or BIOS filesystem call between 0.9 and 1.0 and it broke the ability of the Borland system to find objects to be linked. Anyway, I'll try the first option now and let you know how I go. Thanks for your interest, and of course the link to the old distribution. Jim -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] pre 1.0 version
Hi, On 11/20/10, Jim Lemon j...@bitwrit.com.au wrote: On 11/20/2010 12:14 AM, Rugxulo wrote: ... What year and model and cpu? Just curious. And what exactly doesn't work, it won't turn on?? DELL Latitude XP 475D Plugged it in, hit the switch and nothing. No lights, no sound, nothing. It has been going for years and I only kept it for the last year or two to compile C programs under FreeDOS. http://support.dell.com/support/edocs/dta/elektra/ At least yours lasted quite a while. My brother and I both had laptops overheat / die, and they were fairly new, circa 2007! ver -r (or -R, despite the help info) gives FreeCom version 0.84 pre2 XMS_Swap [Aug 28 2006 00:29:00] That doesn't tell the kernel, so I'm blindly guessing you have to type (exactly): ver /r. It should say kernel 2036 or whatever somewhere. It basically calls this: http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=General_Information/557 You can also get the version STRING with function int 21, AX=33ff, returns segment, offset in DX, AX. Be sure to test with 2038 kernel instead, and see if that helps: http://sourceforge.net/projects/freedos/files/Kernel/2038/kernel2038-fat32-binary.zip/download http://sourceforge.net/projects/freedos/files/Kernel/2038/kernel2038-source.zip/download I'm pretty sure that it's the version because I had been compiling various C programs in the Borland C IDE for years and as soon as I upgraded, it stopped compiling. I just tried it again with a program that I know would compile and got: Undefined symbol _EGA_VGA_driver in module STRZ2.C When it first happened, the undefined symbol would be whatever library or object file was to be linked in first. I checked the paths, checked that the libraries and object files were there, tried to manually compile and link, tried stupid things like copying the object files into the code directory, etc. It was then that I copied a minimal Borland C setup to the old DELL that still had the previous FreeDOS version and ... it worked! As I had to get the program compiled and was able to, I didn't complain and thought that I would eventually be able to fix the problem. Still don't know what Borland version you're using. I know that J. Hoffman uses BC31 without issues. But yours is a worrisome report, though. I can't verify it here since I don't have whatever compiler you're using. (FreeDOS really officially recommends OpenWatcom, but some of the utils still somewhat rely on [not really freeware anymore] Borland tools.) My choices appear to be three: Downgrade to pre 1.0 FreeDOS and hope that I can once again do the development work on this PC. This is the best option, as I don't do a lot of this anymore, and I wouldn't have to change anything. If that's best for you, that's fine. But I would *love* to know what exact kernel and what exact compiler you're using first. ;-) Move from Borland C to Watcom. I agree with your opinion about Watcom, but I have an awful lot of code that depends upon Borland graphics drivers (and probably a few other Borland things), and I don't want to rewrite it. So it would be a worst case scenario. I would rather port the whole thing to Linux and run it under Real Time Linux. Haven't heard from Blair in a long time, but he did whip this up (untested by me), so it might help: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/devel/libs/tcc2wat/ But I agree, having to migrate code is a pain (even if unavoidable sometimes). Fix whatever is going wrong with the present setup. The error messages, as explained above, are those awful sort that say X isn't there and when you look, X is there. My guess is that there was some subtle change in a DOS or BIOS filesystem call between 0.9 and 1.0 and it broke the ability of the Borland system to find objects to be linked. I've never had any similar problems with the (hardly) freeware tools, and I don't use pre-1.0 either. So it's possible that it's something specific to your setup (hopefully), but I don't ignore the chance it's a true bug. Anyway, I'll try the first option now and let you know how I go. Thanks for your interest, and of course the link to the old distribution. Hope we can sort this out so that others don't run into any unnecessary bugs. -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] pre 1.0 version
Hi all, Well, it's finally happened. The ancient DELL laptop that has been my only development machine has carked it and I am going to have to try to downgrade this PC to a pre-1.0 version to keep compiling. My Borland C compiler has not worked on this machine since I upgraded to 1.0 and despite several messages to the list, I've found no way to fix it. I looked in the archive, but there does not seem to be any pre-1.0 versions available. Anyone know where I can get one? Jim -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] pre 1.0 version
Hi, On 11/19/10, Jim Lemon j...@bitwrit.com.au wrote: Well, it's finally happened. The ancient DELL laptop that has been my only development machine has carked it What year and model and cpu? Just curious. And what exactly doesn't work, it won't turn on?? and I am going to have to try to downgrade this PC to a pre-1.0 version to keep compiling. My Borland C compiler has not worked on this machine since I upgraded to 1.0 and despite several messages to the list, I've found no way to fix it. Hmmm, I know I read your recent message, but you were kinda vague. What exactly doesn't work? What error message does it give? What version of Borland C? And most importantly, what kernel are you using? (try ver /r) It's most likely an issue on your end since I haven't heard of any Borland tools having issues except maybe Turbo C 3.0, but I think they fixed that in later kernels. So you should definitely try kernel 2038 (instead of 2036 from FD 1.0) or even unstable 2039. I looked in the archive, but there does not seem to be any pre-1.0 versions available. Anyone know where I can get one? Not offhand. Jim removed all the old ones because people kept getting confused and getting the older versions. I'm sure there's a mirror online somewhere, but I don't know offhand. EDIT: Does this link help? But I'd rather you didn't use this and instead told us more specifically what's wrong. Most FreeDOS users don't use Borland tools except (freeware) TC++ 1.0.1 or TC 2.01 or TP 5.5. http://ftp.usf.edu/pub/freedos/files/distributions/official.old/0.9sr2.BETA/ P.S. Worst case scenario, you could always use OpenWatcom, right? It's far better than Borland anyways (and official compiler for FD, natch). -- Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
