Re: [Freedos-devel] Improved RBIL

The Crux Linux distro solved this with their port system [0]. It’s a build from source distro. Each package (port) has one or more sources. Those sources then get processed by a build function into a destination directory. One (pre)step could be to process patch files. The files in the

Re: [Freedos-devel] FreeDOS on Pocket386

Instead of investing in PS2, I’m building one or more of these. https://docs.pikvm.org/pico_hid_bridge/ On Wed, May 29, 2024 at 12:15 AM Jerome Shidel via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > > > On May 28, 2024, at 6:12 PM, Jim Hall via Freedos-devel < >

Re: [Freedos-devel] FETCH4FD

On Sat, Mar 23, 2024 at 4:24 AM Danilo Pecher via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > > In that case it is more than helpful to have the most pertinent > parameters at a glance right after login. It’s also a good way to make screen shots more exciting than “C:\>” or

Re: [Freedos-devel] Problem booting FreeDOS on Book8088 PC-XT laptop

I’m oso2k on bttr. I don’t have bocke’s issue with booting my Book8088 v2 with FreeDOS. I don’t know if they are having hardware issues. I booted FD1.3 Floppy Edition on a Dell 316SX (386 16MHz) and have formatted a 256MB CF and a 512MB CF. Both cards boot on my Dell 316SX and Book8088. I

Re: [Freedos-devel] FreeDOS on Book8088

ke this. I'll update the > bug with your info. > > > > Mind if I copy your photo into the bug report to show that it's working? > > > > On Tue, Jan 30, 2024, 1:44 PM Louis Santillan > wrote: > >> > >> I have a Book8088 v2. I did some testing. I im

Re: [Freedos-devel] FreeDOS on Book8088

Louis Santillan 11:44 AM (5 minutes ago) to Technical, Jim I have a Book8088 v2. I did some testing. I imaged the FD13BOOT.IMG from FD 1.3 Floppy Edition[0] to my a slot on my Gotek formatted USB stick. I then used a Dell 316SX (a 386) with a Gotek FDD emulator & XT-IDE r625 to boot FD

Re: [Freedos-devel] Interim Build Delayed

Trixter has an 8088 version of LZ4 which is typically faster PKZIP, zlib/gzip, and bzip2. http://www.oldskool.org/pc/lz4_8088 On Fri, Sep 1, 2023 at 11:58 AM Ralf Quint via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > On 9/1/2023 7:49 AM, Jerome Shidel via Freedos-devel

Re: [Freedos-devel] dir issues

On Sun, Jul 23, 2023 at 8:52 AM Steve Nickolas via Freedos-devel < freedos-devel@lists.sourceforge.net> wrote: > On Sun, 23 Jul 2023, tom ehlert via Freedos-devel wrote: > > > > >> ISTM that all the other graphical shells in FreeDOS are even less > >> useful than GEM, and it would be no loss to

Re: [Freedos-devel] format \s

A couple tips. If you only need 100MB or so, you can mount and work on the USB image like (https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.3/official/FD13-FullUSB.zip) like so. ``` # sudo mount -tvfat -o loop,offset=32256 FD13FULL.img /mnt/target/ ``` There used to be a

Re: [Freedos-devel] I want my 10K

This is pretty good and matches pretty well with what MDGX/axcel216 has been able to achieve. MS-DOS 6.22 (https://www.mdgx.com/mem6.htm#M6) ``` Modules using memory below 1 MB: Name Total = Conventional + Upper Memory

Re: [Freedos-devel] I wish I had a boot.log file

 PM Louis Santillan wrote: > > I forget which one and which version, but it had the ability to > redirect the blacked out screen to a file. Been a long while since I > looked at them. > > On Thu, Mar 23, 2023 at 4:14 PM wrote: > > > > Hi Louis, > > >

Re: [Freedos-devel] I wish I had a boot.log file

I forget which one and which version, but it had the ability to redirect the blacked out screen to a file. Been a long while since I looked at them. On Thu, Mar 23, 2023 at 4:14 PM wrote: > > Hi Louis, > > > On Mar 23, 2023, at 5:32 PM, Louis Santillan wrote: > &g

Re: [Freedos-devel] I wish I had a boot.log file

Don’t blackout and bootsplash do something like this? https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/boot/blackout/ https://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/boot/bootsplash/ On Thu, Mar 23, 2023 at 5:52 AM wrote: > Hi All, > > I decided I needed to take a

Re: [Freedos-devel] Open Watcom v2 DOS installer is abysmally slow in FreeDOS

That depends. Besides poorly optimized system caches, is the installer doing things that blow the cache and increase the miss rate? You noted a significantly increased download zip. Is everything actually necessary? Did you download a debug build that will have additional binary code or is the

Re: [Freedos-devel] Open Watcom v2 DOS installer is abysmally slow in FreeDOS

(16MB) cache. https://sourceforge.net/p/freedos/mailman/message/37727725/ https://sourceforge.net/p/freedos/mailman/freedos-devel/thread/Dog.2N9f.5Ml4lqeFp6Q.1ZND6x%40seznam.cz/#msg37727725 On Tue, Mar 7, 2023 at 8:35 PM Louis Santillan wrote: > > You haven't detailed anything about

Re: [Freedos-devel] More on Packages

On Tue, Feb 21, 2023 at 1:37 AM wrote: > On Feb 20, 2023, at 4:17 PM, Louis Santillan wrote: > > [..] > GW-BASIC - MIT License, Microsoft’s original 1983 version > https://github.com/microsoft/GW-BASIC > > > tkchia has a better branch that should be easier to compile and

Re: [Freedos-devel] More on Packages

On Mon, Feb 20, 2023 at 11:37 AM wrote: [SNIP] > Other possible new packages to consider for inclusion (or at least watch): [SNIP] > > GW-BASIC - MIT License, Microsoft’s original 1983 version > https://github.com/microsoft/GW-BASIC tkchia has a better branch that should be easier to compile and

Re: [Freedos-devel] Proposal: remove Graphical Desktops from next FreeDOS

I would suggest that OpenGEM get moved to Extras. On Wed, Feb 15, 2023 at 2:07 PM Jim Hall wrote: > > As I mentioned in my other email, I don't think we need to have > Graphical Desktops included in FreeDOS. I propose that we remove > Graphical Desktops from the next FreeDOS, starting with the

Re: [Freedos-devel] UEFI, virtual BIOS and virtual hardware - was: Goo gle Summer of Code?

This would be ideal if coreboot supported more machines ( https://coreboot.org/status/board-status.html). I believe you did some work some years back to prove out cooreboot+SeaBIOS+FreeDOS. I’m not sure a typical user or even experienced FreeDOS users would be keen to swapping out their board’s

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

On Sat, Jan 21, 2023 at 4:08 PM Jim Hall wrote: > So let's discuss: > > What core programs or components should we put into the application - > if we apply and can get accepted? For 386+ machines, what about an installer based on Linux that doesn’t need to reboot multiple times to install to

Re: [Freedos-devel] UEFI, virtual BIOS and virtual hardware - was: Google Summer of Code?

Over the last couple years, DOSBox and DOSBoxPure in RetroPie and RetroArch have become quite popular. https://m.youtube.com/watch?v=LRy8brZ7DVc https://m.youtube.com/watch?v=-mD2DnMVoLE Consider standardizing on that. RPis will have access via RetroPie. There’s a version of DOSBox in the

Re: [Freedos-devel] Linking asm with C

OpenWatcom uses ``, `union REGS` type, and `int86()` when using a DOS Real Mode Memory Model. See: Page 405 - https://web.archive.org/web/20220507185907/http://ftp.openwatcom.org/manuals/current/clib.pdf

Re: [Freedos-devel] Linking asm with C

The tools you are using do matter. Which C Compiler, which Assembler, which Linker? On Thu, Jan 12, 2023 at 3:39 PM Ralf Quint wrote: > > On 1/12/2023 11:43 AM, Knedlik wrote: > > Hello, > > I’m currently trying to make a function in a separate assembly file, but > > I’m having problems

Re: [Freedos-devel] Where to start and continue?

One reference, HelpPC might also be useful (https://stanislavs.org/helppc/). On Tue, Jan 10, 2023 at 1:32 AM Carsten Strotmann via Freedos-devel wrote: > > Hi, > > On 10 Jan 2023, at 10:13, Knedlik wrote: > > > Hello all again, > > thanks for all the responses. Definitely useful stuff. I’d just

[Freedos-devel] Incompatible "copy /b" operation

Over at vogons, Dave Dunfield (https://dunfield.themindfactory.com/dnld.htm) has been working on updating his DDLINK package to be able to bootstrap file transfer between machines via COM, LPT or NIC. This is a small package much like LapLink and other tools of yesteryear. LapLink could famously

Re: [Freedos-devel] Where to start and continue?

Depends on where you want to start. Do you want to learn an API/library like Allegro or DOjS and start "extending system" sooner? Or would you rather learn how to write against the VGA or VESA standards or other hardware standards? If the latter, then PCGPE would be helpful

Re: [Freedos-devel] Where to start and continue?

Otherwise, Allegro and DOjS likely your best bets today. On Mon, Jan 9, 2023 at 11:25 AM Louis Santillan wrote: > > You'll want to look at > > Allegro 4.4.3 for DOS > (https://liballeg.org/stabledocs/en/readme.html), a complete game C > library for DOS and djgpp. > > Mic

Re: [Freedos-devel] Where to start and continue?

You'll want to look at Allegro 4.4.3 for DOS (https://liballeg.org/stabledocs/en/readme.html), a complete game C library for DOS and djgpp. Microwindows for DOS (https://github.com/ghaerr/microwindows), a Windowing system with Win32 and X11 like APIs available, also for djgpp. DOjS

Re: [Freedos-devel] Bonus/Devel CD

On Tue, Oct 25, 2022 at 8:34 AM Bret Johnson wrote: > > RHV is based on oVirt which is based on KVM plus qemu & libvirt & > > lots of other bits. It'll run DOS but you might have jump through > > hoops (learn virsh and other tools) to get it installed. > > > > BHyve, at least as in TrueNAS Core

Re: [Freedos-devel] Bonus/Devel CD

RHV is based on oVirt which is based on KVM plus qemu & libvirt & lots of other bits. It’ll run DOS but you might have jump through hoops (learn virsh and other tools) to get it installed. BHyve, at least as in TrueNAS Core and OSX/Mac OS before M1 will also run DOS. I think it’s at least worth

Re: [Freedos-devel] no sys/socket.h ... need dj_watcp package

You know you know you can get a precompiled copy of WatTCP and other djgpp zips at delorie.com or a mirror near you? http://www.delorie.com/pub/djgpp/current/ http://www.delorie.com/pub/djgpp/current/v2tk/wat3211b.zip On Sat, Sep 3, 2022 at 10:00 PM Paul Dufresne via Freedos-devel <

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

IANAL but I am seeing references where Copyright Notice is dubiously referred to as being extraneous (since it is automatic at time of creation) and "All rights reserved" is touted as having no legal effect anymore. If it is true, TIL. https://lists.debian.org/debian-legal/2007/06/msg00252.html

Re: [Freedos-devel] Thinking about FreeDOS test releases

Any thoughts about the ability to build (more than kernel, FreeCOM, ISO) from source? On Mon, May 16, 2022 at 3:11 AM Jerome Shidel wrote: > Hi, > > Based on the discussion during the online get-together and the tool-chain > and release processes used to maintain packages and deploy release

Re: [Freedos-devel] Thank you Jerome

Yes! Thanks to Jerome especially and to everyone who has made an update or bug fix or language fix or document fix since 1.2! On Wed, Dec 29, 2021 at 4:12 PM Wilhelm Spiegl wrote: > Hi to all, > > I think it is time to say THANK YOU very very much to Jerome at this point. > > As I see it now,

Re: [Freedos-devel] dir /od

On Wed, Dec 29, 2021 at 2:03 PM Jim Hall wrote: [SNIP] > But don't forget that FreeDOS 1.3 RC5 also sets a DIRCMD environment > variable, so you need to consider that too: > > C:\>echo %DIRCMD% > /P /O:GN /Y > About this...this default %DIRCMD% "slowed" me down while I've been playing with FD

Re: [Freedos-devel] RC4 Videos (was Testing FreeDOS 1.3 RC5)

Agreed. It was all mostly good feedback and notes about quirks in FD vs. other DOSes. On Fri, Dec 24, 2021 at 2:10 AM Jerome Shidel wrote: > Hi Louis, > > On Dec 24, 2021, at 4:36 AM, Louis Santillan wrote: > > > An interesting (and series of very very long) "hot tak

Re: [Freedos-devel] Testing FreeDOS 1.3 RC5 (Games)

An interesting (and series of very very long) "hot takes" of FD 1.3RC4 from the "Temporarily Offline Retro Tech" youtube channel. FreeDOS Install and Bundled Apps - Part 1 https://youtu.be/j6s50qGZzO4 FDOS! What's in the FDOS folder? - FreeDOS Part 2 https://youtu.be/v-_RqLP_Bgs More FDOS! = The

Re: [Freedos-devel] [Freedos-user] FDNET missing from FreeDOS 1.3-RC4

For other historical concerns and if necessary, one could possibly also use Archive.org to support evidence of a timeline of events. On Thu, Oct 14, 2021 at 1:45 PM Jim Hall wrote: > Eric emailed me off-list, but I am replying back to the list to keep > the conversation together: > > On Thu,

Re: [Freedos-devel] USB Image Capacity

I always really appreciate the Raspberry Pi foundation's auto-resize capability for Raspbian/Raspberry Pi OS. On boot, during kernel boot up, it auto grows the filesystem to match the SD card. So maybe ship the small image and then make the resize batch file a menu item? On Fri, May 14, 2021 at

Re: [Freedos-devel] Slack space

Jim, Maybe add a link to the auto-added signature that gets tagged to each mailinglist email? On Thu, Nov 26, 2020 at 4:46 AM Jerome Shidel wrote: > > Hi All, > > No I’m not talking about those bytes that go unused in the file system. > > I’m just referring to the Slack group for FreeDOS. It’s

[Freedos-devel] OSS ExFAT Implementation

I saw a post on HN the other day that of a light weight OSS FAT12/16/32 implementation intended for Microcontrollers (including 8-bit MCU!) [0][1]. Perusing the author's website, I find that it is a subset of another FAT implementation for MCUs that includes an exFAT [2]. To me it is an

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

Are there docs on how to setup `config.h` and `config.mak` for `gcc-ia16`? On Sun, Dec 29, 2019 at 1:01 PM Bart Oldeman wrote: > > Hi, > > better late than never and just within the 2010's here is finally > another prerelease. There have been mostly bug fixes, most importantly > the stack

Re: [Freedos-devel] Inexplicable ambiguous name flags error from TurboC

Shouldn't the `z_header.flags` value just be copied to a `zword` var and then passed to `SET_WORD( a, v)` to avoid the ambiguity? Instead of ``` int i; SET_BYTE(H_CONFIG, z_header.config); SET_WORD(H_FLAGS, z_header.flags); ``` do ``` int i; zword zwflags = z_header.flags; SET_BYTE(H_CONFIG,

Re: [Freedos-devel] default (lack of) buffering in Turbo C 2.01 (e.g. Cheap Sed)

Rugxulo, It wasn't clear what is not buffered. Is TurboC 2.0.1 itself (the compiler, linker, make, etc.)? Or TurboC 2.0.1's runtime? On Fri, Mar 29, 2019 at 11:06 AM Rugxulo wrote: > Hi, Tom, > > I thought you might find this interesting since you're always raving > about old C compilers for

Re: [Freedos-devel] FreeDOS 1.3-RC1

Jerome, Do you mean something like the SHSU* Image/ISO to RAMDrive utils [0][1][2] when you said, " If we had a driver that could directly use CD/DVD media like a hard drive and cache changes to RAM, then things could be different and possibly even better"? [0]

Re: [Freedos-devel] FreeDOS floppy is working as a part of coreboot SeaBIOS opensource BIOS image

Does this mean that using coreboot, computers with UEFI can boot FreeDOS? On Wed, Jan 9, 2019 at 9:52 AM Ivan Ivanov wrote: > If you've a Q about putting FreeDOS inside opensource coreboot BIOS, > or any other coreboot-related questions, please let me know :) > And btw there is a coreboot

Re: [Freedos-devel] VGA frame rates and mouse

; David E. McMackins II > Supporting Member, Electronic Frontier Foundation (#2296972) > Associate Member, Free Software Foundation (#12889) > > www.mcmackins.org www.delwink.com > www.eff.org www.gnu.org www.fsf.org > > On 2018-07-19 09:48, Louis Santillan wrote: > > What hardwa

Re: [Freedos-devel] VGA frame rates and mouse

What hardware are you doing this on? Have you seen Allegro? [0][1] [0] http://liballeg.org/stabledocs/en/index.html [1] https://github.com/liballeg/allegro5/releases/download/v4-2-3-1/all4231.zip On Thu, Jul 19, 2018 at 5:42 AM David McMackins wrote: > > Your definition of "force full redraw"

Re: [Freedos-devel] Starting FreeDOS 1.3

Are there any thought as to how TK Chia's gcc-i16 port [0] and Bart Oldeman's patches [1][2] might fit into 1.3+ plans? [0] https://github.com/tkchia/gcc-ia16 [1] https://github.com/PerditionC/fdkernel/pull/25 [2] https://github.com/PerditionC/fdkernel/pull/26 On Thu, Jul 12, 2018 at 8:51 AM

Re: [Freedos-devel] Good BASIC interpreter?

There's a real minimal, hacky version of BASIC in David Dunfield's DOS tools, with source [0][1][2][3]. Maybe refer to that if you need inspiration. [0] http://www.classiccmp.org/dunfield/dos/index.htm [1] http://www.classiccmp.org/dunfield/dos/sample.txt [2]

Re: [Freedos-devel] Compiling with gcc

On Sun, Oct 29, 2017 at 9:20 PM, Steve Nickolas wrote: > On Sun, 29 Oct 2017, Jim Hall wrote: > >> That said, I'd love to see other tools become part of FreeDOS. If >> there was a DOS-native GCC that could generate 16-bit binaries in the >> different memory models, I'm all for

Re: [Freedos-devel] announcing DOSUTIL - LS

Not to pooh-pooh what you've done, but maybe you'd want to explore something like suckless sbase [0][1], ubase [2][3], or toybox [4] or beastiebox [5]? With OpenWatcom and/or DJGPP, it shouldn't be as hard to port them. [0] http://core.suckless.org/sbase [1] http://git.suckless.org/sbase/tree/

Re: [Freedos-devel] Booting other O/Ses from FreeDOS

IIRC, BasicLinux [0] and other UMSDOS Linuxes would not boot/load with EMM386 as they would put the CPU into V86 mode. After such, loadlin, et. al., could not recapture control of the CPU and reload the GDT [1]. [0] http://distro.ibiblio.org/baslinux/ [1] http://wiki.osdev.org/GDT_Tutorial On

Re: [Freedos-devel] Working on a video review and found some issues

On Sat, Dec 3, 2016 at 6:45 PM, Philip Hoefer wrote: > Hello! > > Excited about the new version and have begun working on a YouTube review for > version 1.2. I focus on games, so that's what I test. > > Trying out a few games I found the following: > > - The supplied

Re: [Freedos-devel] VirtualBox and RC1 Networking

Any idea how VirtualBox was configured for the user reporting the issue? NAT, Internal Network, Bridged, Host-only? This could answer the firewall question. On Wed, Nov 2, 2016 at 4:35 AM, Jerome E. Shidel Jr. wrote: > Hello All, > > The latest release of VirtualBox seems to

Re: [Freedos-devel] FreeDOS 1.2 Auto NET Config

A couple weeks late. Apologies. I like this goal. The current FD 1.2pre 22 doesn't seem to have any networking subsystem packages installed. For me, this affects our direction. Michael Brutman has additional applicable analysis about DOS networking here [0]. WatTCP/Watt-32: Lots of apps.

Re: [Freedos-devel] Graphics APIs

If you're doing C, there's djgpp[0] (gcc, other GNU stuff, and more) and Allegro[1], GRX [2] which has a BGI-like interface, Microwindows/Nano-X[3] which has TinyGL (OpenGL-like), Win32-like & X11/xlib-like interfaces. Georg Potthast has a FreeDOS distro, XFDOS[4], which integrates Nano-X & FLTK

Re: [Freedos-devel] Problems on website?

No issues noticed. EC2 [0][1] instances are the lowest level (or basis/basic level) technologies in the AWS stack. High Availability/Disaster Recovery/Fail Over (HA/DR/FO) is not something you buy in AWS; it's something that is configured (relatively easily). Something like Cloud Formation [2],

Re: [Freedos-devel] Fwd: I'd like an absolute minimal version of FreeDOS.

Blackout[0] or bootsplash[1] could solve the screen blanking. [0] http://www.freedos.org/software/?prog=blackout [1] http://www.freedos.org/software/?prog=bootsplash On Wed, Jun 15, 2016 at 3:58 PM, Jayden Charbonneau wrote: > With some sort of process that can run

Re: [Freedos-devel] FDI remaining issue

fdisk can provide more info in this situation I think. I think it can actually map (print) all the BIOS drives and their BIOS port number. Running `fdisk /dump` [0] should do it. [0] http://help.fdos.org/en/hhstndrd/base/fdisk.htm On Tue, Feb 23, 2016 at 10:18 AM, Jerome E. Shidel Jr.

Re: [Freedos-devel] FDI remaining issue

I'm recanting my original vote. Option 3. On Sat, Feb 20, 2016 at 10:23 PM, Louis Santillan <lpsan...@gmail.com> wrote: > I think the we need to emulate MS-DOS in this respect. Or take option 5. > > On Sat, Feb 20, 2016 at 4:24 PM, Jerome Shidel <jer...

Re: [Freedos-devel] FDI remaining issue

I think the we need to emulate MS-DOS in this respect. Or take option 5. On Sat, Feb 20, 2016 at 4:24 PM, Jerome Shidel wrote: > There is an additional option. > 5) just do something similar FreeDOS 1.1. Make a backup of old MBR, then > just blast new MBR. > > On Feb 20,

Re: [Freedos-devel] An idea???

Forgot to mention NewDeal [0] and some other pre-Y2K GUIs [1]. [0] http://toastytech.com/guis/nd32.html [1] http://toastytech.com/guis/index.html On Wed, Feb 17, 2016 at 3:38 PM, Louis Santillan <lpsan...@gmail.com> wrote: > Maarten, > > You should familiarize yourself with what

Re: [Freedos-devel] An idea???

Maarten, You should familiarize yourself with what's already been done. OPENGEM/GEM [0], SEAL[1], DOSStart [2], others [3][4][5]. [0] http://www.freedos.org/software/?prog=opengem [1] http://sealsystem.sourceforge.net/ [2]

Re: [Freedos-devel] freedos and fsf

Not all parts of FreeDOS meet the FSF's requirements[0]. One, it's not a "GNU/Linux" system. Two, there are few tools in BASE [1] which are open source but not necessarily 4 freedoms OSS [2]. Jack Ellis' work and SHSUCDX being prime examples. [0]

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

I wouldn't think the LBA aware type would have kept your system from booting. I thought that only affected Win9x and IFS driver. Glad you got it working anyways. On Tue, Feb 2, 2016 at 9:20 PM, Paul Dufresne wrote: > >What exact partition i.d. is your FAT? Perhaps it

Re: [Freedos-devel] FDI USB stick

Eric, In general, I agree with you. 1) Doing the (possibly) surprising thing would be wrong: if an MBR exists, overwriting it without mentioning it to the user would be wrong. However, changing the partitioning (as I did) and not having a booting system was also very surprising (and wrong IMO).

Re: [Freedos-devel] FDI USB stick

I used the default, minimal install. No updates to autoexec.bat/config.sys. That's a Jerome question. On Thu, Jan 28, 2016 at 4:03 PM, Rugxulo <rugx...@gmail.com> wrote: > Hi, > > On Thu, Jan 28, 2016 at 12:52 AM, Louis Santillan <lpsan...@gmail.com> > wrote: > &g

Re: [Freedos-devel] FDI USB stick

(no support for USB flash drive boot; tried several BIOSes). [0] https://sites.google.com/site/lpsantil/fdi12-msi-wind On Tue, Jan 26, 2016 at 11:22 PM, Louis Santillan <lpsan...@gmail.com> wrote: > Is there an ISO yet of FDI/FD 1.2preX? Forgot that M6805 has a broken > BIOS wrt

Re: [Freedos-devel] FDI USB stick

Is there an ISO yet of FDI/FD 1.2preX? Forgot that M6805 has a broken BIOS wrt to USB boot. On Tue, Jan 26, 2016 at 8:07 PM, Rugxulo wrote: > Hi, > > On Tue, Jan 26, 2016 at 5:58 PM, Jerome Shidel wrote: > > Hello Eric and all, > > > > A little more

Re: [Freedos-devel] FDI, updated

I'd like to make a minor suggestion here. When packaging up USB image to a zip file, leave off directory path to the image. Thanks, On Fri, Jan 22, 2016 at 12:47 PM, Jerome E. Shidel Jr. wrote: > I forgot something in the old (10 minute ago release). > So, i just put up

Re: [Freedos-devel] FDI and FreeDOS 1.2

Since DOS 1.0, (IBM/ROM-)BASIC[0] & DEBUG[1] were the default programming facilities. [0] https://en.wikipedia.org/wiki/IBM_BASIC [1] https://en.wikipedia.org/wiki/Debug_(command) On Tue, Jan 26, 2016 at 11:54 AM, Maarten Vermeulen wrote: > Hi, > > I should leave BWBASIC

Re: [Freedos-devel] FDI USB stick

I downloaded it last night. I have an MSI Wind U100 (Atom N2700, 2GB DDR2, 120GB SATA) [0] and an eMachines M6805 (AMD Athlon 64 3000+ DTR, 512MB PC2700, 4GB IDE) [1] I can test with when I get home tonight. [0] https://en.wikipedia.org/wiki/MSI_Wind_Netbook [1]

Re: [Freedos-devel] FDI and FreeDOS 1.2

On Fri, Jan 22, 2016 at 3:59 PM, Rugxulo wrote: > Hi, > > On Fri, Jan 22, 2016 at 5:36 PM, Eric Auer wrote: > > > > Hi Rugxulo et al, > > > > indeed xgrep and grep both have their uses... Regarding BWBASIC, > > current FreeBASIC is extremely cool while

Re: [Freedos-devel] FreeDOS 1.2

On Fri, Jan 22, 2016 at 11:56 PM, Thomas Mueller wrote: > > Excerpt from Rugxulo: > > > > Well maybe it would also be nice to have some BASH, such > > > as the DJGPP one - both shell and script language... :-) > > > Nah. Their Bash is ancient (2.05b), not well-supported by

Re: [Freedos-devel] FDISK issue

You'll likely need MASM or TASM to assemble. WASM/JWASM may work in compatibility mode. On Mon, Jan 4, 2016 at 1:09 PM, Antony Gordon wrote: > Hi, > > I’m using NASM. It seems to work well with all the other labels. > > In my digging, I have found that default may be a

Re: [Freedos-devel] FDINST

I would post an issue to Richard Geldreich's miniz project site [0]. Though he's focused on lzham these days, he's usually pretty good about responding to bug reports. Rich also intended for tinfl to be RFC compliant, so if there is an issue, he may want to address it. [0]

Re: [Freedos-devel] FDNPKG16 port!

Ummm...FreeDOS Software List for WatTCP[0] points to the FTP site [1]. [0] http://www.freedos.org/software/?prog=wattcp [1] http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/net/wattcp/ On Fri, Oct 9, 2015 at 8:45 AM, sparky4 wrote: > link me a 16 bit version of wattcp >

Re: [Freedos-devel] exfat support from android linux for freedos sdxc support and more?

On Sunday, September 27, 2015, Antony Gordon wrote: > Hi, > > Unfortunately, Linux doesn’t have a 16-bit C compiler (that I am aware > of). GCC has some fundamental differences in C dialect from OpenWatcom and > Borland which would require conditional defines (especially

Re: [Freedos-devel] FreeDOS 1.2 Installer Project

On Fri, Sep 11, 2015 at 9:40 AM, Jerome E. Shidel Jr. wrote: > > However, that being said. The BASE is the BASE and should not be removed > by a package manager. It should always be there. :) Except when you want or need to update BASE (like in upgrading from FD 1.1 to 1.2

Re: [Freedos-devel] FreeDOS 1.2 Installer Project

To make the Base install viable (usefully execute fdnpkg), will networking (wattcp and/or mtcp) & shsufdrv become a part of Base? -L On Thursday, September 10, 2015, Jim Hall wrote: [SNIP] > > 1. Do you want to install all the extra software, or just the programs > that

Re: [Freedos-devel] mTCP/IP stack by M Brutman is now closed source

Sadly, it would mean that specific version of mTCP could not be included in FD. On Mon, Sep 7, 2015 at 8:31 PM, Mercury Thirteen wrote: > > > On 9/7/2015 6:37 PM, Michael Brutman wrote: > > ... > I think that whether it is open source or not it is still a great solution

Re: [Freedos-devel] FreeDOS install

If you need to find out what your BIOS provides, check rayer's tool [0]. [0] http://rayer.g6.cz/programm/programe.htm On Wed, Jun 3, 2015 at 2:37 PM, Louis Santillan lpsan...@gmail.com wrote: I don't believe FD1.1 supports what you're looking for. You need your BIOS to support special USB HDD

Re: [Freedos-devel] FreeDOS Developer Studio

On Wed, Jun 3, 2015 at 12:55 PM, Rugxulo rugx...@gmail.com wrote: Hi, [SNIP] On Wed, Jun 3, 2015 at 1:12 PM, Eric Auer e.a...@jpberlin.de wrote: I think SETEDIT comes with some programmer support and there is some DJGPP IDE (RHIDE?) and maybe others. Neither has been maintained (for

Re: [Freedos-devel] FreeDOS Developer Studio

Which is? Are you speaking of User Experience, User Friendliness or something else? On Wed, Jun 3, 2015 at 5:14 PM, Chelson Aitcheson chelson.aitche...@gmail.com wrote: Out of box experience On 04/06/2015 10:07 am, Louis Santillan lpsan...@gmail.com wrote: What is oobe? On Wed, Jun 3

Re: [Freedos-devel] FreeDOS install

I don't believe FD1.1 supports what you're looking for. You need your BIOS to support special USB HDD as DOS drive emulation or maybe you can read up on this FreeDOS USB technote [0]. Some vintage BIOSes only had EDD 1.1 [1]. If you were lucky you had EDD 3.0 [2]. Apparently, there was even a

Re: [Freedos-devel] FreeDOS Developer Studio

Rhide and setedit's output capture is what is being asked for. On Wednesday, June 3, 2015, Rugxulo rugx...@gmail.com wrote: Hi, On Jun 3, 2015 4:13 PM, Antony Gordon cuzint...@gmail.com javascript:_e(%7B%7D,'cvml','cuzint...@gmail.com'); wrote: Is there an IDE that’s included with

Re: [Freedos-devel] FreeDOS Developer Studio

What is oobe? On Wed, Jun 3, 2015 at 4:48 PM, Chelson Aitcheson chelson.aitche...@gmail.com wrote: Oobe should be be a part of the fd distro to ever be considered serious. Whether it be for dev or new users. And stop comparing it to Linux because Linux developers made the forward choices to

Re: [Freedos-devel] FreeDOS 1.2 package compilation

* I don't know if the permissions were set by you or the original zip files, but they're messed up in several place, at least with respect to *nix. Some are set to 555. Not sure why execute bit is even set anywhere at all. * It's large (1.1GB decompressed). * Lots of files/folders are not in 8.3

Re: [Freedos-devel] FreeDOS 1.2 package compilation

I'm not of this effort, but, Ralf, what are you using to scan for viruses? On Tue, Jun 2, 2015 at 5:39 PM, Ralf Quint freedos...@gmail.com wrote: On 6/2/2015 5:09 PM, Mercury Thirteen wrote: Everyone take a look at this ZIP http://mercurycoding.com/FreeDOS/FreeDOS-1.2.zip and let me know

Re: [Freedos-devel] Hello!

On Sat, May 16, 2015 at 7:44 PM, JK Benedict xenfomat...@outlook.com wrote: [SNIP] - Base resources, such as file system options/changes - Connectivity tools * Modernized web browser (I am working on one now - a text based prototype) There's Georg Potthast's Dillo port (in XFDOS [0]),

Re: [Freedos-devel] Hello!

On Fri, May 15, 2015 at 2:47 PM, J.K. Benedict xenfomat...@outlook.com wrote: [SNIP] #1. Has anyone assembled a doc on creating the preferred developer's sandbox? I use many languages and want to ensure any software I offer meets Read here [0][1][2][3]. Short answer, reference C compiler is

Re: [Freedos-devel] Hello!

Forgot to mention (Open/Free)GEM [0] and Windows 3.1x, 95, 98 [1]. [0] http://www.freedos.org/software/?prog=opengem [1] http://en.wikipedia.org/wiki/Windows_3.1x On Fri, May 15, 2015 at 3:37 PM, Louis Santillan lpsan...@gmail.com wrote: On Fri, May 15, 2015 at 2:47 PM, J.K. Benedict xenfomat

Re: [Freedos-devel] System Configuration Editor

As an FYI, many terminal/text-based editors (taking gnu nano as an example here) simply perform a regex match on the text and prefix/postfix the text with VT100/ANSI color codes matching the 16 VT100/ANSI standard colors (which align to similar colors in the 16 color EGA/VGA palette). See

Re: [Freedos-devel] System Configuration Editor

I would look at setedit's code as SET implemented syntax color highlighting for TV (djgpp, however). See [0]. [0] http://setedit.cvs.sourceforge.net/viewvc/setedit/setedit/ On Mon, Apr 13, 2015 at 8:41 AM, Antony Gordon cuzint...@gmail.com wrote: Jayden, I don't know if you have used Windows

Re: [Freedos-devel] Instituting a vetting process for FreeDOS software

There's lots about this discussion that dismays me. But alas, I'll focus on making this better. I suggest we look to other open source projects for guidance and examples of successful processes. I'd throw Linux Kernel and Chromium as examples of modern collaborative workflows. Each assigns

Re: [Freedos-devel] FreeDOS 1.2 and 2.0 roadmap discussion

To maybe summarize and make the task list a bit more concrete. Goals for FD 1.2 * Update kernel (release 2042?) * Update apps * Update translations * Update installer * Update/Standardize on mTCP and FDNPKG * Live-CD with installer * Floppy-based installer Possible Goals for FD 2.0 * USB-drive

Re: [Freedos-devel] FreeDOS 1.2 and 2.0 roadmap discussion

Like others have said, anything (like the fictitious 64-bit DPMI) which has 1) little or no working code as of today (precedent/compatibility/feature parity with MS 3.3/6.22), 2) has a high a degree of complexity (achieveable), 3) requires a large dedication of man-hours to complete, 3) has little

Re: [Freedos-devel] Kickstarter project for FreeDOS 2.0

You can also buy a copy at MacMall for $2 [0]. [0] http://www.macmall.com/p/HP-Operating-Systems/product~dpno~13045035~pdp.igfhgha On Wed, Dec 31, 2014 at 8:52 PM, Michael Brutman mbbrut...@brutman.com wrote: Somebody should talk to HP and see what FreeDOS 2.0 includes. They are already

Re: [Freedos-devel] Working on FreeDOS 1.2

On Wed, Dec 31, 2014 at 8:54 AM, Matej Horvat matej.hor...@guest.arnes.si wrote: [SNIP] I agree that a better installer is needed (the one in 1.1 seemed to be slow and generated broken AUTOEXEC.BAT files for non-US(?) keyboard layouts). I think we should adapt FDNPKG so it can be compiled with

  1   2   >