Re: [Freedos-devel] MS-DOS 4.0 source released as open source under MIT license

Hi Jim, >> D:\>nmake >> >> Microsoft (R) Program Maintenance Utility Version 1.00.05 >> Copyright (c) Microsoft Corp 1987, 1988. All rights reserved. >> >> NMAKE : fatal error U1051: usage : 'NMAKE' [-bcdeinpqrst -f makefile -x >> stderrfi >> le] [macrodefs] [targets] >> Stop. > > > But when

Re: [Freedos-devel] Needs testing: SJGPlay

Hi Rugxulo, >> I haven't checked the new sources (IIRC, it was said to be BASIC ... >> PowerBASIC??). Does it also include ACD kit (or whatever third-party >> lib)? > > This release does not include the sources to "ACDkit", only binary > files (libs, etc). Can this be fixed? Who wrote ACDkit? Whe

Re: [Freedos-devel] FreeDOS package issues

> 4) CDP, This is* not open source software*. It is Freeware without > sources. Should this be removed. Is there an decent open source alternative? CDP is a non-TSR CD player. Jim once used CDP to demonstrate FreeDOS package management at _opensource_ dot com: https://opensource.com/article/21/6/

Re: [Freedos-devel] UEFI, virtual BIOS and virtual hardware

Hi Aitor, > Both links give me a 404, maybe a problem with pasting? https://dosbox-x.com/wiki/Guide%3ADOS-Installation-in-DOSBox%E2%80%90X https://dosbox-x.com/wiki/Guide%3AManaging-image-files-in-DOSBox%E2%80%90X Cheers, Robert -- BTTR Software https://www.bttr-software.de/ DOS ain't dead h

Re: [Freedos-devel] Google Summer of Code?

Hi Liam, > "All" it needs is a memory manager that can start as a 32-bit process, > set up a few interrupts -- INT 11 for the hard disk, for instance -- INT 11? Hard disk is Int 13h. Cheers, Robert -- BTTR Software https://www.bttr-software.de/ DOS ain't dead https://www.bttr-software.de/for

Re: [Freedos-devel] Google Summer of Code?

Hi Ralf, >>> So let's discuss: >>> >>> What core programs or components should we put into the application - >>> if we apply and can get accepted? >> A mouse-driven GUI... >> >> SCNR :-D >> > No, PLEASE, NO! 😛 Was just kidding... Cheers, Robert -- BTTR Software https://www.bttr-software.de/ D

Re: [Freedos-devel] Google Summer of Code?

Hi Jim, > So let's discuss: > > What core programs or components should we put into the application - > if we apply and can get accepted? A mouse-driven GUI... SCNR :-D Cheers, Robert -- BTTR Software https://www.bttr-software.de/ DOS ain't dead https://www.bttr-software.de/forum/ __

Re: [Freedos-devel] Linking asm with C

Hi Knedlik, > I’m trying to learn graphics programming in DOS. It’s really hard to get > resources on this topic... Fixing a few broken links on my page , you get this: 256-Color VGA Programming in C http://www.brackeen.com/vga/ Graphics Programming

Re: [Freedos-devel] Toggling directories

Hi Bret, > In general, I find that toggling options are a bad idea. Things just > get too confusing, especially if you have multiple "sources" for the > options (like combinations of internal/compile-time default settings, > environment variables, options entered through a batch file, options > en

Re: [Freedos-devel] Bonus/Devel CD

Hi Liam, >> The one made by Microsoft? > > Two points of order: wrong name and wrong tense. > > VirtualPC was made by Connectix, and was acquired by Microsoft. Did Microsoft make Virtual PC 2004 and 2007 or was it Connectix? What does the sticker on the box say? Microsoft or Connectix? :-p > S

Re: [Freedos-devel] Bonus/Devel CD

Hi Bret, > 86Box > Bochs > DOSBox > DOSBox-X > DOSEmu / DOSEmu2 > Hyper-V > JPC > KVM > Parallels > PCem > QEMU > vDOS > VirtualBox > VirtualPC (Connectix) > VirtualPC (Microsoft) > VMWare Don't forget Hampa Hug's PCE - PC Emulator: http://www.hampa.ch/pce/pce-ibmp

Re: [Freedos-devel] Bonus/Devel CD

Hi Bret, >> VPC uses FreeDOS?? Not sure. > > Yes. What VPC are we talking about? VPC as in Virtual PC? The one made by Microsoft? I doubt, any version of VPC included FreeDOS, but feel free to prove me wrong. :-) Cheers, Robert -- BTTR Software https://www.bttr-software.de/ DOS ain't dead h

Re: [Freedos-devel] Detecting VMs

Hi Jerome, > Without going into great details, I have made a couple programs that > can do some (i think) neat visual tricks that require VGA support. One > such visual trick works on nearly all REAL hardware and in DOSBox. > However, it does not work in any other tested VM. Therefore testing for

Re: [Freedos-devel] FreeDOS Interim Build T2210

Hi Joseph, > On another note, I just corresponded with Sammy Mitchell of Semware. > The Semware Editor (TSE) has gone into Freeware, and, he tells me that > the DOS version will also eventually be freeware and open-source. Oh, that would be cool. > Whether the license is compatible remains to

Re: [Freedos-devel] No simple cpu identification program returning an error code as an answer?

Hi Jim, > The Creative Commons have identified a "CC-0" ("Creative Commons > Zero") that indicates "no rights reserved" that does the same thing. > https://creativecommons.org/share-your-work/public-domain/cc0/ May I apply CC0 to computer software? If so, is there a recommended implementation? ht

Re: [Freedos-devel] It's "crynwr.com", not "www.crynwr.com"!

Hi Paul, > There is a small mistake on the link for crynwr on: > > http://wiki.freedos.org/wiki/index.php/Networking_FreeDOS_-_Packet_driver_installation > section: Where to find them (the packet drivers) > > the crynwr link have www. at the beginning... it does not work because > of that. > The

Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?

Hi tom, > just remember that we had even the holy > https://en.wikipedia.org/wiki/Editor_war Sure, I know about the Emacs vs vi war. I tried Emacs more than vi, because I found Org mode very interesting for managing my notes and such stuff. It's only few years ago, but I can't remember any of Em

Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?

Hi tom, >> But there are many good (and free) >> text editors available for DOS that can edit large text. > > True enough. and people have had time enough (it's 2022) to select one Not everbody is with DOS since the 1980s. There are still DOS newbies around from time to time. > but none of them

Re: [Freedos-devel] Why there is no two versions of FreeDOS: 16 bits and 32 bits?

Hi Eric, > for example SETEDIT is 32-bit and can edit large files, > but maybe we should explicitly tell WHICH editors are > 32-bit. To be honest, I do not know for several others. At minimum these are 32-bit: BLOCEK EMACS FED MINED VIM Cheers, Robert -- BTTR Software https://www.bttr-softwa

Re: [Freedos-devel] edit and ospedit limited to 64k?

Hi Paul, > One of my reflex when going to Games\Vertigo was "edit vertigo.txt" to read > the file. > It say the file is too big for this version of edit. > "edlin vertigo.txt" worked... as "less vertigo.txt"... I think the file was > 79k... not sure at all... > but I am kind of surprised that ed

Re: [Freedos-devel] Could almost all packages use links?

Hi Paul, > I know some packages use "Links" to make executables in the > executable %PATH% to make them callable from any directory. You're probably talking about the BAT and COM files in C:\FreeDOS\LINKS. > The question I ask myslf, is why is is the exception rather than the norm? Because prob

Re: [Freedos-devel] Template for writing DOS Device Drivers in Open Watcom C

Hi Eduardo, > I needed to implement a DOS device driver for something I'm working on > related to vmsmount. While searching for information, all the examples I > found were developed in assembler. Although I have done things in > assembler before, I find it much more satisfying to program in C and

Re: [Freedos-devel] The 386MAX source code has been released :)

Hi Bob, > My problem is not with making the changes, it's with uploading the > changed files. Unfamiliar with Github as I am, the only way I saw to > upload files is through their "Add file/Upload files" method. This > limits me to 100 files and some small number of MBs per upload. > > This

Re: [Freedos-devel] How to access all drives on USB stick

Hi Richard, > I have a FreeDOS BOOT USB stick with 5 partitions (C:, D:, E:, F:, G:) > where the C: partition (512 MB) is the FreeDOS stuff and the other 4 > were created via Freedos as an option by me. > > So far, I can only see the first three in freeDOS - Windows 10 can see > all 5 partitions

Re: [Freedos-devel] Grafx2 port to FreeDOS (alpha release)

Hi Devin, > I have been working on a FreeDOS port of Grafx2 > (http://grafx2.chez.com/index.php). The source code resides at: > https://github.com/deverac/grafx2-dos. A FreeDOS package (with sources) > resides at ./dist/grafx2.zip. This is really cool you decided to do so! :-) Thanks! Cheers, Ro

Re: [Freedos-devel] standard directories

Hi Mark, > Does FreeDos have standard directories for development then production > libraries and headers? No. FreeDOS is not Linux. Cheers, Robert -- +++ BTTR Software +++ Home page: https://www.bttr-software.de/ DOS ain't dead: https://www.bttr-software.de/forum/

[Freedos-devel] KERNL86.SYS vs. KERNL86N.SYS

(repeating my question posted to freedos-user from 14 days ago, because I didn't get a reply) Hi, the differences seem to be: 1) Support for LFNs with KERNL86.SYS, because of kernel compatibility level 7.10 (vs. 6.22). 2) Support for FAT32 partitions with KERNL86.SYS. Anything else? Cheers, Rob

Re: [Freedos-devel] Thinking about FreeDOS 2.0

Hi Eric, > Hi! I agree that it is not really useful to use ClamAV in DOS. > By now, it has a list of millions of virus signatures of which > basically all will be for Windows viruses anyway. You need more > than 200 MB for a typical signature database for it and opening > it takes ages before you

Re: [Freedos-devel] Thinking about FreeDOS 2.0

Hi Wilhelm, > clamav seems not to work. if it should work i did not find out how. I see. I only tried once for short and also couldn't get it to work. > freedos av which is also available at ibiblio works with restrictions > and a very old 20 mb database from clamav, an actual one has in about >

Re: [Freedos-devel] Thinking about FreeDOS 2.0

Hi Wilhelm, > a) have a look at the bug list, e.g. xdel (reported by you), edit > (reported by me has several bugs), fdisk > (reported by me: sizes for a primary size > 1000 MB cannot be entered as > a value), fd antivirus (only works with a 10 years old virus definition What is FD Antivirus? Do

Re: [Freedos-devel] Thinking about FreeDOS 2.0

Hi Jim, > 1. Move to a "rolling release" > [...] A FreeDOS "rolling-release" distro already exists. Its name is SvarDOS and you can find it at . SvarDOS has been created and is maintained mainly by Mateusz Viste. It is based on his experiences with his former FreeDOS dis

Re: [Freedos-devel] freedos 1.3 at german magazine heise

Hi Eric, >>> https://www.heise.de/news/Betriebssystem-Oldtimer-FreeDOS-1-3-mit-neuen-Programmen-und-Features-6515775.html >>> >> >> Just had a quick read over that one and noticed one strange thing >> mentioned. Apparently the CPU detection in the installer would only >> recognize an 80186 ev

Re: [Freedos-devel] Documentation Formats

Hi Jim, > Why is PDF format needed? The kernel documentation is in plain text, > which is readable everywhere on every system. If you use ASCII only. Otherwise you might get into the trouble of codepages. ;-) But yes, plain text works for most documentation. Cheers, Robert -- ++

Re: [Freedos-devel] Documentation Formats

Hi Jim, > Python isn't really meant for DOS. But hey, we've had other things > ported to FreeDOS that weren't really "meant" for DOS. > > If you want to port Python to FreeDOS, I'm sure some folks would like > to use it. So, if you're looking for permission: go ahead and port > Python for DOS. T

Re: [Freedos-devel] Any package updates for FreeDOS 1.3?

Hi Jim, > Since the release of FreeDOS 1.3 RC5, I haven't seen any discussion > about outdated or broken packages in RC5. (To be clear, I've seen some > discussions about packages, but these seem to have been resolved as > either a missed step or a config issue. But more generally, I don't > recal

Re: [Freedos-devel] Contemplations, Considerations and some Conclusions

Hi Jim, > I suspect the term is regional :-) It's the same thing as a USB thumb > drive or USB flash drive. > > USB flash drive is the more common term. In Germany it's often called "USB stick". Cheers, Robert -- +++ BTTR Software +++ Home page: https://www.bttr-software.de/

Re: [Freedos-devel] REMember a bug

Hi Jerome, > As everyone knows and the docs clearly state, everything after a REM is > ignored. > > However, I recently noticed an issue with a batch file that had something > like: > > REM this thing [[x|4]] or later > > in one of its remarks. Every time the batch was executed, it displayed

Re: [Freedos-devel] dir /od

Hi Jim, > I think we should merge the kernel back into the new FreeDOS GitLab > repo, now that we have one. But that's a separate discussion I'll > start with Perdition. For me (!) it doesn't matter, if it's on GitLab or GitHub (or even Codeberg.org), as long as I know, how to find it. My primary

Re: [Freedos-devel] dir /od

Hi all, > How (also when) will this patch (and other patches) make it into the > official freecom repo? > (I'm still confused by all the different private, public, official, > semi-official repos. So no offense. I'm just curious.) > > https://gitlab.com/FreeDOS/base/kernel#still-actively-develope

Re: [Freedos-devel] dir /od

Hi Tom, > I reproduced the bug. > > I fixed the bug. > > in CMD\DIR.C, line 972+ change > > static int orderFunction(const void *p1, const void *p2) > { > ... > case ORDER_BY_NAME: > rv = strcmp(f1.ff_name,f2.ff_name); > break; > } >

Re: [Freedos-devel] Does FreeDOS (or something) sometime automatically break up an hard disk in 2GB sub-disks?

Hi Eric, > users will have FAR more than 60 GB disk size and you can > have only 24 drive letters from C: to Z: Up to 32 under some DOS/Windows versions: https://en.wikipedia.org/wiki/Drive_letter_assignment#Common_assignments Cheers, Robert -- +++ BTTR Software +++ Home page

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Solutions?

Hi Volkert, > Do you remember this thread from 2012? I see you participated in it as well: > > https://sourceforge.net/p/freedos/mailman/freedos-devel/thread/4F2097D2.5060500%40sudleyplace.com/#msg28740668 > > In point 4 of his opening post, Bob Smith (sudleyplace on GitHub) > mentioned that wit

Re: [Freedos-devel] JEMM can't completely replace EMM386 (yet). Soluti ons?

Hi Tom, > JUMPERS! anybody remembers JUMPERS (and associated problems) ? Yes, I remember jumpers, but I don't remember any problems. (Resource conflicts are caused by humans, but not jumpers.) Robert -- +++ BTTR Software +++ Home page: https://www.bttr-software.de/ DOS ain't

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

Hi Aitor, > I've noticed you Germans have your quirks with the spelling because > there was a change to standardise the ortography not long ago (when to > use ss and eszett amongs others :)). The last big reform was in 1996. But this reform has been reformed in 2004, 2006, 2011, 2017, and 2018.

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

Hi Mercury, > Yep, language names like German, French, Spanish, et. al are all > considered "proper nouns" and as such should be capitalized. :-) @Tom: "proper nouns" is what we translate to "Eigenname" in German. https://www.englishgrammar101.com/module-1/nouns/lesson-2/common-and-proper-nouns

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

Hi Tom, >>> attaches the german resources to fdisk.exe, and makes german the >>> default language for fdisk.exe. > >> Minor note: AFAIK, correct spelling of "german" in English is "German" >> with a capital "G". Same for all other language "names". > > really? Like in 'Could you provide the Germ

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

Hi tom, > attaches the german resources to fdisk.exe, and makes german the > default language for fdisk.exe. Minor note: AFAIK, correct spelling of "german" in English is "German" with a capital "G". Same for all other language "names". Cheers, Robert -- +++ BTTR Software +++

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

Hi Jim, > Good to see this update. I look forward to trying this out. > > One comment from reviewing the code - you use this comment at the top > of both kittenc.c and kitten.c: > >> /* >> This software is free software; free to use, >> modify, pass to others, whatever >> >> use it at your

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

Hi Ralf, >> If we would streamline the build process for most of the FreeDOS tools, >> creating per-language binaries will be a breeze. > It would be as simple as putting all files that do have translations for > a specific language in a designated folder for that language, replace > the text to

Re: [Freedos-devel] CHAR: echo ascii characters

Hi Jim, > So if you want to print out the degree symbol (ASCII decimal 248) you > would type: > > char 248 > > (ASCII codes not in 0-255 are printed as '?' instead.) Would ASCII codes "not in 0-255" still be ASCII codes? ;-) Original ASCII is only 128 chars, by the way. Cheers, Robert --

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

Hi Ralf, >> But for a modern DOS that needs to support different languages by >> different users in different countries, I think language catalogs (the >> "Kitten" method) provide the best solution. > > Well, the problem is that this can increase the size of a lot of > executables by a lot. And

Re: [Freedos-devel] Devel-Philosophy [was: blocking bugs/issues for FreeDOS 1.3]

Hi Jim, > I think using language catalogs is a very flexible way to provide > internationalization in a program. The tradeoff is a bit of > performance (reading the catalog) and some extra code to manage > everything. The benefit is you end up with *one* compiled program that > you use in every la

Re: [Freedos-devel] What are the blocking bugs/issues for FreeDOS 1.3?

Hi Jim, > What are the blocking issues or bugs in FreeDOS 1.3 RC4? (What remains > to be updated or fixed from RC4?) This COUNTRY.SYS issue is still not fixed after 1.5 years, although I provided a patch to the list (

Re: [Freedos-devel] MEM command curiosities

Hi tom, >> During some recent development work, I noticed that the FreeDOS MEM >> command reports the TSR I'm writing is using one less paragraph than >> its MS-DOS counterpart - it seems it does not account for space >> occupied by the MCB at the start of the TSR's heap, while the MS-DOS MEM >>

Re: [Freedos-devel] reporting FreeDOS bugs

Hi Jim, > Ah, I see what you meant. Yes, if I'm not logged in, I can see the > same message if I hover over the "Create ticket" link. > > I always thought SF only allowed logged-in users to create tickets. > But digging into this further, I found the setting that controls this. > Either I didn't

Re: [Freedos-devel] reporting FreeDOS bugs

Hi Tom, >> I don't see where the bug tracker on SourceForge requires anyone to be >> "authorized" by the project admin. Can you provide more detail here? > > I - as probably you too - are permanently logged in to SourceForge. > and then this doesn't happen. > > log out (or use a different browse

Re: [Freedos-devel] FreeDOS kernel and FreeCOM command.com updates

Hi Jeremy, > Unfortunately that is a side effect of git, it doesn't set time stamps. > I find it very annoying but haven't found a good solution. I have no > desire to manually set timestamps. If anyone has suggestions for how to > get git to set timestamps on files, I would be greatful. I cur

Re: [Freedos-devel] Problems on 1.3rc4 on VirtualBox

Hi Jim, >> Caused by un-initialized variables (immediate death) and >> bad speed caused by bad wait for retrace. Crashes at exit >> are caused by bad exit style depending on from where in >> the game you left it. All fixed in my patched version, >> see my mail to the list about that ;-) >> > > Di

Re: [Freedos-devel] Additional notes on Games

Hi Jim, > * Beyond the Titanic (text adventure game) says in the startup screen: > >>Please note that Beyond the Titanic is a SHAREWARE game. >> >>This game has been placed in the public domain for your enjoyment. > > ..and then it has some text about if you like the game, you should > contribut

Re: [Freedos-devel] Additional notes on Games

Hi Jim, > So I think we should drop Magenetic for the same reasons. Agree? Agreed. Cheers, Robert -- +++ BTTR Software +++ Home page: https://www.bttr-software.de/ DOS ain't dead: https://www.bttr-software.de/forum/ ___ Freedos-de

Re: [Freedos-devel] Any DJGPP RHIDE user to compile my NGE Nibbles patch?

> Anyway, I uploaded some Nibbles.exe for testing: > 1) Just modified to make it build with GXX 4.3.2: > https://www.bttr-software.de/tmp/nge_nibbles/Nibbles_exe.zip > 2) Eric's patch applied: > https://www.bttr-software.de/tmp/nge_nibbles/Nibbles_exe2.zip > 3) Rebuild of 2) with GXX 3.4.4: > https

Re: [Freedos-devel] Any DJGPP RHIDE user to compile my NGE Nibbles patch?

Hi all, > Does anybody use RHIDE already and would be > willing to make a new binary for me? Rugxulo? Current status of building a new NGE_Nibbles binary: 1) is crap for compiling on Windows XP, because

Re: [Freedos-devel] Any DJGPP RHIDE user to compile my NGE Nibbles patch?

Hi Eric, > I made a patch to fix the speed of NGE Nibbles, Nice. :-) > but it does not come with a makefile: Instead, > it comes with a RHIDE (DJGPP C/C++ IDE) config > file to compile it with the DJGPP C++ compiler, > also making assumptions about the source path. > > Does anybody use RHIDE al

Re: [Freedos-devel] FreeDOS 1.3 packages

Hi all, > And I'm fine with keeping both P7Zip and Zip/Unzip. Note that > Zip/Unzip are the standard Info-Zip archive tools, while P7Zip can > work with some other files. I'd like to keep Zip/Unzip for sure, but > P7Zip also works with other archive types. And there's a note on the > wiki's packag

Re: [Freedos-devel] Distro autoexec/config wishes for 1.3rc4 (CPULEVEL and CALLVER updates)

Hi Mercury, > A quick side-note; I sent Ralf a quick email a while back simply asking > if he was still accepting updates to the RBIL and he kindly affirmed he > was, although he did indicate slight surprise that anyone was working on > new DOS applications these days and would be interested in co

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Jeremy, > 2042 is kernel version 2.42, specifically the kernel build # is major * > 1000 + minor which currently equals 2000 + 43 = 2.43 for 0xFD kernels. > > Note that the kernel releases just have a version number to identify > them, whereas development builds should include cvs/svn/git (dep

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Mercury, >> > - Two digits for the major version >> >> There probably will be some software needing three digits. Firefox, >> although not available for (Free)DOS), is already at version 88.0. > > Right, but I was basing this on the majority of FreeDOS software which jumps > to mind. I don'

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Mercury, > I'd say we really /*do*/ need a set standard for versioning. The > frustration Eric mentioned in his email has hit me once or twice as well > when combing through archives to compare versions. > > The format I propose is: > - The date in ISO 8601 format ISO 8601 has various formats

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Eric, >> Could you please bottom-post on mailing lists? Top-posting as you are >> doing breaks threading. >> > > Threading should be based on subject etc. not on content. How it shows up, depends on the client software used... In general, threading should be based on the "In-Reply-To" and "

Re: [Freedos-devel] RC4

Hi Eric, > Why are PAINT2, LHA, UNRAR, ELTORITO, XMGR and RDISK on > none of the media? How about DRMIND, KILOBLAS, LINCRAWL > and PRSINVAD? Who managed to make a minesweeper 8 MB and > a tetris version 3 MB large? Why no TAIL and UPTIME, or > BLWCBC blowfish cbc? Most is explained here: http://w

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Jim, >> Maybe you would find some volunteers to assist you, *if* you ask. >> > > I think we first need to agree what the file and directory layout > should be, or we'll have a "bunch of cooks" each doing their own > thing, and we'll be in the same situation. Sure! :-) > Still trying to figur

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Jim, >> solution, 2.01, 2.02, 2.11, 2.20. if necessary 2.02.01 for minor updates or: >> 2-01, 2-02, 2-11, 2-20, 2-02-01. but of course this will run out of 8.3. >> compared with checking and changing thousands of htm help files renaming is >> a five minutes job. >> > > Using "2.02.01" is an i

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Jim, > That would provide clarity to what version you're looking at in a > single directory listing, but consider I'll have to rename EVERYTHING > on Ibiblio. That's a LOT of maintenance work. Sorting things into > directories like "2.0" and "2.1" seems easier. Maybe you would find some volunt

Re: [Freedos-devel] Missing help package from FreeDOS 1.2 distribution on ibiblio

Hi Jerome, >>> at >>> https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/latest/ >>> Also, there is a listing.txt file. It is tab separated. It doesn't >>> contain all the metadata and is much smaller than the csv. However, it >>> is probably a little easier to parse with scrip

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Jim, >> I would have hoped to find "files" named latests.zip and latestx.zip (or >> something like that), which always link to the latest version. > > If Ibiblio were still an ftp site, I would agree. But I believe this > is very confusing when the files are displayed via a web server. > Ibibl

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Eric, > indeed I have slowly moved to more "sorted directory listing > friendly" date formats, but it would not be a problem for me > if you decided to rename all files lbacache_-mm-dd.zip > style and put them all in ONE directory. Then one can see > at one glance what is available, without

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Jim, > So you can see at a glance in the top level directory what versions > came out when. And you can quickly navigate to the latest version > ("2008"). Correct. > Not every LBACACHE release used the same date format in the filename. > Sometimes it was "mmmdd" like "2008apr07" .. and so

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Eric, > Hi Jim, making the package versions number a part of the > directory structure seems like a marginal improvement to > me in most cases. For packages which have a stable style > of version numbering, it can even make the structure worse, > as people can no longer see which version came o

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Jim, > And inside each directory: > > > 2.0: > choice201.zip choice20.zip > 3.0: > choice30.zip > 3.1: > choice31.zip > 3.3: > choice33.zip > 3.5: > choice35a.zip choice35b.zip choice35.zip > 3.6: > choice36a.zip choice36c.zip choice36e.zip

Re: [Freedos-devel] Missing help package from FreeDOS 1.2 distribution on ibiblio

Hi Jerome, > I don’t know if this helps. But whenever packages have been updated on > the repo, the repository management software builds a new cdrom.iso late > that night which contains only the latest versions of all the packages > on the repo. It also updates a listing.csv that contains a list

Re: [Freedos-devel] Cleanup on FreeDOS Ibiblio

Hi Jim, > Just wanted to let you know that I did a little cleanup on the FreeDOS > files archive at Ibiblio. Okay. > Over the history of using the files archive on Ibiblio, I haven't really > done a great job at keeping things clean. For example, there was one > directory for FreeDOS Choice at /

Re: [Freedos-devel] lptlink lptransfer italian-english translation? updates? other laplink tools?

Hi Eric, > If we have a much better ALTERNATIVE tool somewhere and > LPTransfer is too minimalistic to care about anyway, it > might be better to just skip updating it, obviously ;-) I like Dunfield's DDLINK from , which seems to be "free", but closed source.

Re: [Freedos-devel] List of 16-bit compatible FreeDOS tools?

Hi, > Is there that indicates what FreeDOS tools are 16-bit compatible? I'd > like to leverage everything possible for use on vintage hardware for > which the DJGPP and 32-bit stuff won't work. Recently, Mateusz announced SvarDOS . The website states: "Care is taken so S

Re: [Freedos-devel] Additional debugging info for FDISK 1.3.3

Hi Jim, > If I shut down QEMU, and use Linux fdisk to examine the virtual drive > image, I see this: > > $ fdisk -l 4gb.img > Disk 4gb.img: 4 GiB, 4294967296 bytes, 8388608 sectors > Units: sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes >

Re: [Freedos-devel] freecom bugs and bugfixes in forks?

Hi David, >> Well, for a GitHub repository that I do not have write access to, what I >> normally do to propose patches is to >> >> (1) fork the repository (in GitHub) >> (2) submit an updated branch as a Pull Request (also in GitHub). >> >> GitLab also allows something similar. >> >> Obviously th

Re: [Freedos-devel] freecom bugs and bugfixes in forks?

Hi Eric, > PS: https://sourceforge.net/p/freedos/bugs/?limit=250 > throws 229 bugs on 1 big pile, not sorted in any way? > Distros, packages, maintainers - anything would help. This reminds me of my message on 23 November: "[Freedos-devel] FreeDOS tickets on SourceForge"

Re: [Freedos-devel] DOS runtime library format

Hi Tom, >>> Was there ever any "official" format for a shared runtime library under >>> MS-DOS? Windows has .DLL files, Linux has .KO files, and MS-DOS had... >>> what, exactly? In all my years DOSsing I've never heard of anything >>> official like this, so I'm pretty sure there was no such thing

Re: [Freedos-devel] DOS runtime library format

Hi Mercury, > Was there ever any "official" format for a shared runtime library under > MS-DOS? Windows has .DLL files, Linux has .KO files, and MS-DOS had... > what, exactly? In all my years DOSsing I've never heard of anything > official like this, so I'm pretty sure there was no such thing (unl

Re: [Freedos-devel] DOS runtime library format

Hi Mercury, > Was there ever any "official" format for a shared runtime library under > MS-DOS? Windows has .DLL files, Linux has .KO files, and MS-DOS had... > what, exactly? In all my years DOSsing I've never heard of anything > official like this, so I'm pretty sure there was no such thing (unl

Re: [Freedos-devel] Jordan Hargraphix SvgaBGI goes MIT license

Hi Danilo, > I still have legal copies of Turbo Pascal 3.0, 4.5, 6.0 and Borland > Pascal 7.0, so if there's interest, I'd be willing to take a look at > them to see if there's any insects to weed out. It might be interesting only, if some existing project already relies on these drivers. The, p

[Freedos-devel] Jordan Hargraphix SvgaBGI goes MIT license

(To whom it may concern.) In April 2020 I got in touch with Jordan Hargrave, who wrote SVGA BGI drivers for Turbo C/Turbo Pascal/Borland C++ until the mid-1990s: Jordan wrote on 19 December: # Hi Robert, If yo

Re: [Freedos-devel] Orphans

Hi Jerome, > Thanks for those. I’ve updated the links on ibiblio and moved those packages > out of the publicly visible groups. +1 > ( FYI, I think a couple of you ports need their packages update. ) Yes. Due to the lack of feedback regarding my ports/builds I don't feel very motivated so far

Re: [Freedos-devel] Orphans

Hi Jerome, > When browsing the online repo, it showed many of the links out to > project homes no longer worked. While many other links still resolved, Probably some links were never correct... archiver/lzip: (My) DOS port is at ; Home

Re: [Freedos-devel] Introduction and Help in OS dev, FreeDOS

Hi Aniket, > I am Aniket, I know C but I didn't make any meaningful project in it. As > I saw a video playlist from Jim Hall, based on C programming language, I > thought I will refresh my knowledge by watching it and then help or > contribute in FreeDOS development. In this way I can solidify my

Re: [Freedos-devel] New Old Timer reporting :-)

Hi Ralf, >>> Never heard about this one, so had only a brief look after downloading. >>> The biggest hurdle for a start is that both the docs and the comments in >>> the source code are in Japanese... >> See it as a big puzzle. ;-) > > Well,... > > That might all depend on what else is going on

Re: [Freedos-devel] FreeCOM 0.84-pre7 prerelease

Hi Bart, > I hope this is finally stable enough for me to remove the pre7 and > release this as 0.84. I only did minimal testing on an emulated XT-class PC () by creating a bootable flop

Re: [Freedos-devel] New Old Timer reporting :-)

Hi Ralf, >> For a while I tinkered around with the Japanese Cabezon Pascal compiler: >> https://wiki.bttr-software.de/Cabezon/HomePage >> >> Didn't get very far, because I lost interest a little. Still have some >> small examples on my disk only. >> >> I already have some ideas, but time flies...

Re: [Freedos-devel] New Old Timer reporting :-)

Hi Ralf, > OpenWatcom at least requires a 386 and additional RAM, I don't think it > is running on a 640KB 808x machine anymore. But there is for years an > Open Source 16bit C compiler, though a bit of a quirky one, which got > pretty much forgotten since Turbo C came out in the mid '80s. I st

[Freedos-devel] FreeDOS tickets on SourceForge

Hi! What about the feature requests or bug reports on or ? It seems nobody else cares about those tickets. So, it's a bit frustrating for me to ask reporters for details, provide workarounds or small fi

Re: [Freedos-devel] began to list problems I see with FD 1.3-rc3

Hi Paul, I had a look at some of your reports. > P121: I have chosen 'French' as language, French(alternative?) as > keyboard, install essential... when rebooting the system > I get 'Bienvenue au systemeParameter Error' followed by working C: > prompt (seems low priority) > https://sourceforge.ne

  1   2   3   >