Re: [Freedos-devel] Hello!

Hi Jesse, Centralized documentation makes sense, but why would you put 100 packages in a centralized source code repository if 95 of them have not a single source code change in a whole year? And why do nightly builds of all 100 then? DOS heavily relies on classic software that simply is okay

Re: [Freedos-devel] freedos os

Hi Ty Amour, to answer both of your mails in one: development project for doing...just a thought: dos based version of PCBSD BSD and DOS are different operating systems. Your suggestion is like Let us make a Windows version of Linux or a Mac version of Windows. In other words, BSD is always

Re: [Freedos-devel] FreeDOS install

Hi! I've tried everything.I ran format /s,I ran Fdisk,I've made the harddrive bootable.But when I go to boot into the harddrive,my laptop just restarts. There are various pretty technical reasons that could cause this: BIOS and DOS disagreeing about geometry when you run SYS or FORMAT versus

Re: [Freedos-devel] FreeDOS Developer Studio

Hey :-) what Apple does with Xcode, they provide an IDE, LLVM (and GCC) and Swift along with sample code, an SDK and documentation. That mainly is because Apple is Apple ;-) In DOS, you get very far with a standard C library, good old OpenWatcom or DJGPP, in the latter case even similar

Re: [Freedos-devel] FreeDOS install

Hi! Just a quick remark, the last time that I had issues booting from USB stick (for some antivirus boot tool) it was because the boot stick generator tool had failed to put a bootable MBR on the stick and mark the partition as bootable. When you KNOW that that is the problem, it is easy to fix

Re: [Freedos-devel] FreeDOS Developer Studio

Hi :-) While I do not use IDE software for DOS, FLDEV, at least judging from the screenshots, seems nice. And graphical. Regards, Eric What does everyone think about adding this to the Dev package in the official 1.2 distro? Georg Potthast mail...@georgpotthast.de wrote: I ported a

Re: [Freedos-devel] FreeDOS 1.2 package compilation

Hi Mercury, That list doesn't contain version information; doing so will require more time. Please invest that time: Having version information will make it easier to know if you have the newest version for both installing packages and for updating the collection. Regards, Eric Fleshed out

Re: [Freedos-devel] FreeDOS Developer Studio

Hi! How about a FreeDOS Developer Studio? I think SETEDIT comes with some programmer support and there is some DJGPP IDE (RHIDE?) and maybe others. While I myself do not use free open source IDE for DOS, but do remember that the Turbo C / Turbo Pascal IDE was not bad, I suggest that there

Re: [Freedos-devel] 32-bit FreeDOS

Hi :-) 1. Start FreeDOS (16-bit mode) 2. Start FreeDOS-32 via a separate executable (it would only be installed if it detected a 32-bit capable processor), perhaps call it FD32. It would switch to protected mode and spawn a protected mode shell. http://freedos-32.sourceforge.net/ already

Re: [Freedos-devel] 32-bit FreeDOS

Hi Anthony, please explain in which way Windows WITHOUT a GUI would be something that we want to add to FreeDOS: There already are really good, free and open DPMI based DOS extenders for DOS. FreeDOS itself is not running in protected mode, but every EMM386 style software must use protected

Re: [Freedos-devel] 32-bit FreeDOS

Hi Antony, if the goal is only to use Windows driver, then writing a clone of Windows is a high price. Plus it already has been paid, by the ReactOS project. Note that DOS windows in Windows often do not gain from Windows drivers: For example if your soundcard comes with a Windows driver, your

Re: [Freedos-devel] Kernel.sys and fdos (dir)

Hoi Maarten, I guess between the lines you wanted to suggest to make kernel.sys and the fdos directory read-only or system or hidden or similar? As far as I remember, this was the case for kernel but NOT anything else in MS DOS, so you could also rename or delete the DOS directory and files like

Re: [Freedos-devel] FreeDOS (ODIN) and 8086 compatibility

Hi, because there seems to be a lot of guessing going on in this thread: * the freedos kernel already does contain a disk buffer cache * maybe freedos is too pessimistic about floppy changes and flushes this cache too often, to be on the safe side... * a lot of the freedos kernel and

Re: [Freedos-devel] FreeDOS 1.2

Hi Jerome, > EN\STAGE300.DEF for the welcome screen. > EN\STAGE400.DEF for partitioning screens. > EN\FDINS100.DEF If you ask me, this is too much pain for too little performance. Going through some text, even if it is a few kilobytes, should be zero problem for the performance of a command

Re: [Freedos-devel] FreeDOS 1.2

Hi Jerome, thanks for adding localization to VECHO, but: > vecho /t %FLANG% HELLO %TFH% "%OS_NAME% %OS_VERSION%" %TFF% > > At the point that line is invoked, > %FLANG% points to a file called A:\FDSETUP\SETUP\EN\STAGE300.DEF > %TFF% and %TFH% are color names Black and Red. You could read a

Re: [Freedos-devel] FreeDOS 1.2

Hi! > Actually, since the boot disk loads uses floppy caching, the FDI runs > reasonably well. As a user, you would not even notice any performance As said, floppy target audience includes more 16-bit people compared to the almost 100% cd/dvd target audience. So you should be able to safely

Re: [Freedos-devel] FreeDOS 1.2

Hi Mercury, > Personally I would rather see an executable installer also and save any > batch installers for a floppy distro, A batch would be perfect for a > setting where every byte counts. Actually no: Easiest would be a floppy with pre-installed DOS and the usual tools (fdisk, format, sys,

Re: [Freedos-devel] FreeDOS 1.2 - Roadmap

Hi Jayden, as far as I am concerned, the installer should NOT backup the entire drive - only the DOS directory which would get overwritten, plus any (config, kernel) files in the root directory that gets overwritten plus maybe the boot sector. As far as installing and updating individual

Re: [Freedos-devel] FreeDOS 1.2

Hi Jayden, (please use SPACES after punctuation - I added them below already...) > Question about the way our new kernel will handle floppy disks. I recently Probably not a kernel issue and also, which "new kernel" do you mean? > got my hands on a lot of unopened micro floppy disks, with a 1

Re: [Freedos-devel] FreeDOS 1.2

Hi Antony, > CONFIG.SYS entry > DEVICE=[drive:][path]DRIVER.SYS /D:0 /F:2 That would be for 720k A: drive hardware, I doubt that the user has such hardware. > may work > http://www.vfrazee.com/ms-dos/6.22/help/driver.sys.htm It will not work because driver.sys does not even exist in

Re: [Freedos-devel] FreeDOS on floppy for 8086 with EMS (was: Re: extending chkdsk to fat32)

Hi Rugxulo :-) > What practical choices do we have? [for old PC] > > 1). Stick to lowest common denominator. E.g. 8086 with conventional > memory only (say, full 640 kb). That would be easiest: People can use Mateusz' 16 bit version of the package manager to add more packages at any time,

Re: [Freedos-devel] The block device driver interface

Hi Georg, thanks for your detailed explanations of Bret's point! > So again, the block device driver interface is not limited to FAT disks. Correct, but non-FAT devices, be it raw BIOS or supported by a block device driver, do not directly allow DOS to do things with the files on those

Re: [Freedos-devel] The block device driver interface

Hi Georg, > I would go for your third alternative and try to map e.g. an ext2 formatted > disk to a FAT32 disk for DOS. This has some problems which you can observe > with the utilities which make an ext2 disk available for Windows. It could > be done within a single block device driver and

Re: [Freedos-devel] extending chkdsk to fat32

Hi Sparky, > is this [extending chkdsk to fat32] possible? My answer is based on "CHKDSK works on all computers where DOS works and behaves as in old MS DOS times": Yes and no. To do proper checking, you want to have more memory available, so you want a 32 bit memory space. The DOS port of

Re: [Freedos-devel] extending chkdsk to fat32

Hi, to join this discussion... I agree that the best way to install DOS on a very old PC is to use a floppy distro. If you ask me, one which users can install using manual FDISK FORMAT SYS XCOPY steps as needed depending on their wishes. No need to waste space on a floppy for a complex installer

Re: [Freedos-devel] FreeDOS 1.2

Hi, at the risk of being controversial: >> I do know that the new version needs to support 16bit >> legacy systems. > > The installer certainly do. FDNPKG being 16bit sure would be "cool", > but I don't see it happening any time soon. IF you can boot from CD then you have 32 bit in 99% of the

Re: [Freedos-devel] FreeDOS

Hi Jerome, > That is why it would be a Super Scary Halloween Release!. Just finished, > completely untested. Probably full of creepy bugs and scary ghosts. :) That is a preview or technology demo, not a release. > Localizing: Unlike a normal executable, I don’t think there is a really good >

Re: [Freedos-devel] FreeDOS

Hi Jerome, > Without vecho, multi-color text highlighting won’t be viable. You could do this EECHO style, where $ is echoed as ESC char, making it easy to use ANSI escapes for color. Actually this feature is also supported in the FreeDOS kernel, but not in FreeDOS command.com ... Still it could

Re: [Freedos-devel] FreeDOS

Hi Jerome, > Who is going to determine what packages go in base and full versions? Base is "clones of stuff that would be included with MS DOS": http://www.freedos.org/software/?cat=base Plus maybe some important drivers and things like ZIP. > Who is going to collect all of them up? Mateusz

Re: [Freedos-devel] The block device driver interface

Hi all, Tom pointed out some important limitation of all interfaces: No matter what you do, DOS interfaces still do NOT support handling of files above 4 GB in size. Even if you use the network redirector interface. A normal DOS app can only access the first 4 GB of a file, or at least it can not

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Bruno, > Em Mon, 7 Sep 2015 15:37:18 -0700 Michael Brutman > escreveu: > >> If the lack of source code prevents you from using mTCP I regret >> that and I encourage you to question your assumption that without >> source

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

Hi Maarten, Barry, Bruno and of course Michael, > Why is it important to have it open source? While I have not read this code either, nor contributed to it, I generally appreciate a possibility to read it. In that sense, it is a pity that code currently is not open. I am sure there would be

Re: [Freedos-devel] FreeDOS 1.2 Installer Project

Hi Mateusz, >- the tricky part might be to make it possible to install FreeDOS on > a system where there is already something (ie. multiboot), and make it > actually bootable, without breaking the other stuff. Personally I > wouldn't object if FreeDOS would just trash whatever there is

Re: [Freedos-devel] FreeDOS 1.2 Installer Project.

Hi Jerome, if you want to store temp results in your batch, you could work with errorlevels, the FreeCOM magic errorlevel variable or indeed a ramdrive. In the past, we often used "memdisk", which is a BOOTABLE RAMDRIVE. That way, the installer used a virtual floppy to boot. As you cannot

Re: [Freedos-devel] FreeDOS 1.2 Installer Project

Hi Jerome, Jayden, Rugxulo, Jim, Matheusz, others! Some more thoughts: > I don’t see a way to install the KERNEL.SYS without updating the > boot sector. But, should always at least ask to back stuff up. Read the output of SYS /? or the HTMLHELP page about SYS or the readme of SYS to find such

Re: [Freedos-devel] FreeDOS 1.2 Installer Project

Hi, nitpicking and ideas coming up :-) > This gives the user the ability to partition and format elsewhere. > But, you cannot do an install without the drive C:. Actually a "live CD" mode would be nice. Give the user some menu item to load a large ramdisk and install (with fdpkg / fdnpkg) a

Re: [Freedos-devel] FDI 1.2 Questions?

Hi! >> * for the same reason, there could be an option to just RENAME the >> old DOS directory instead of moving the contents into a zip file, >> as suggested by Mercury. > > And if there is already an FDOS.OLD? :-) As with your ZIP solution: In that case, rename to another name, such as

Re: [Freedos-devel] FreeDOS 1.2 Installer Project

Hi Jayden (and Mateusz and Jim and...) :-) > Will we implement an "advanced" setup? [...] > The first would be the user friendly setup,and the second would allow the > user to manually choose packages,and even access the command line (I think > it has the prompt of X:\).This way,if the user

Re: [Freedos-devel] FreeDOS 1.2 Installer Project

Hi! > How many of you remember the DOS 6.22 install process? If possible, it > should aim for that. It's simple and straight to the point. It worked As far as I remember, it was 3 floppies and only "base" software... Also, under which conditions would it format / partition your disk? > across

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

Hi Jim and Geraldo, of course I agree that exFAT should be accessed using the network redirector or CDEX interface: It would be too large to be in the kernel, should not be carried around with the kernel all the time and should be kept separately for the case that there are licensing issues.

Re: [Freedos-devel] FDI 1.2

Hi Jerome, basically the "is the newest DOS already installed" check has to wait for the target selection. Plus it should not be necessary to use black magic* for this: I would prefer if the installer only checks if a DOS with LSM & package manager data structures is installed or not. Then other

Re: [Freedos-devel] XFTOOLS - exFAT access a la LTOOLS

Hi Rugxulo, (sorry about the long thread while the FS candidate list shrinks...) >> as mentioned earlier in this thread, generic operating systems >> are allowed to implement VFAT (FAT32 and LFN) without fees, so >> I would not be too worried about those two more years. Referring to two items

Re: [Freedos-devel] FDI 1.2

Hi Jerome, thanks for your work on your installer :-) > 1) boots from floppy or floppy image (like boot CD) > > (Note: if user manually lauches installer, skip 2 and goto 3) > > 2) Detects if latest FreeDOS version is installed (actual test not > written) If it is the latest version, returns

Re: [Freedos-devel] XFTOOLS - exFAT access a la LTOOLS

Hi Eduardo and Georg, actually BLOCK drivers are only suitable for making FAT partitions on non-BIOS drives (e.g. USB) usable by DOS. For other filesystems, you would use other interfaces: CDEX / network redirector API, as used for ISO9660 CD/DVD and for VMWare in VMSMOUNT :-) Regards, Eric

Re: [Freedos-devel] XFTOOLS - exFAT access a la LTOOLS

Hi Rugxulo, as mentioned earlier in this thread, generic operating systems are allowed to implement VFAT (FAT32 and LFN) without fees, so I would not be too worried about those two more years. Regarding LTOOLS quality: This thing is ancient and of course it supports only ext2, not ext3 or ext4.

Re: [Freedos-devel] FDI 1.2

Hi Jerome, combining 20 tools of 1-2 kilobytes each into one tool of 10 kB sounds like a good plan and using "residency" sounds even better: Outside the floppy world, each of your tools will use at least 4 kB because sizes get rounded up to full, often large, clusters. Also, having some sort

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

Hi Ralf, > ExFAT is indeed covered by Microsoft patents, the Samsung driver is said > to be in violation of those and should be avoided at all cost if you > don't want to risk patent litigation with M$ at some point... > >

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

Hi FreeDOS-ers, > We could undercut the competition and make our own free FAT > implementation which does fills the same niche as exFAT. Extremely unlikely to succeed! For example OGG Vorbis audio works very well and is free but still companies rather pay to license MP3. On Sony Smart TV

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

Hi Steve & Mercury, >> While I agree that further information would be welcome, >> I am generally optimistic about possibilities for exFAT. > > ...prolly best still to leave it to the network redirector, and keep it > out of the kernel proper, just in case. > > But perhaps it could be

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

Hi Mercury, (note: 2 GB and one core are no problem even for DOS - but for example 8 GB and several cores are supported by almost nothing in DOS, as there are no nice DOS extenders for it) > I don't see where we need multitasking for NAS use. A program could be > made to both handle incoming

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

Hi Mercury, thanks for having a look at the existing solutions, keep us posted. Note that HFS+ is by Apple so it will also have license details. As Linux already supports HFS+ it seems that Apple is friendly on that. For ext2, note that you may be able to read ext3 and ext4 contents by

Re: [Freedos-devel] FDI 1.2 Questions?

Hi Mateusz and Michael, the installer should NOT try to be more clever or automatic than we can SAFELY make that. I disagree with Mateusz about the "simply give me a button to destroy my harddisk contents and put DOS on it" because that is too destructive. Default should be to ADD DOS to an

Re: [Freedos-devel] FDI 1.2 Questions?

Hi! > Disc boots: > > Offers to install or quit. What happens if you select "install"? > (note: if DOS is already installed, setup does no “launch”. > The installer does this specifically for the disc to be used for recovery and > whatnot. > What makes a better recovery disc than a live

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

Hi, I noticed that since 2013, there is free open source exFAT support for Linux, originally coming from Android, in spite of exFAT being quite proprietary... However, as memory cards above 32 GB size and probably other (embedded) devices will probably use exFAT more often in the future, would it

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

Hi again, > Maybe some DOSers want to have a look at the exFAT driver code, > to check complexity: https://github.com/dorimanx/exfat-nofuse Some other interesting links are: https://github.com/relan/exfat and: https://en.wikipedia.org/wiki/ExFAT#Adoption which states that one of the drivers

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

Hi Mercury, so you want to run a NAS or home automation on DOS? For NAS, you need a multitasking OS, not DOS. For home automation, which limitation of FAT would be a problem? Same for other light embedded devices. Flash does not give good performance for FAT, but embedded devices would have

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

Hi Tom, as I have noticed that your drivesnapshot website also contains tools for exFAT support: What is your opinion about possible patent and licensing issues for exFAT? Regards, Eric >> I don't want to sound harsh, but "drawing specs" is easy, anybody can do >> that. Do some code that

Re: [Freedos-devel] FDI 1.2

Hi Jerome, for clarification: I was referring to the specific case where your tools are used as a part of the install process of FreeDOS :-) In your given "pick a file and unzip" example, it would be possible to do alternative tricks like: VASK-PRO /F *.zip "Pick a file to unzip" "unzip $F"

Re: [Freedos-devel] XFTOOLS - exFAT access a la LTOOLS

To remove GRUB from your boot process, FDISK /MBR or the Linux or Windows equivalent of that is usually enough. In the less common case that you had GRUB in the boot sector of your Linux and NOT in the MBR: Simply make something else than Linux the active partition ;-) You can also wipe those

Re: [Freedos-devel] XFTOOLS - exFAT access a la LTOOLS

Hi Georg, > I gave up on Grub plus DOS after I locked myself out from my PC. The usual way to fix this is to boot e.g. Linux from CD to edit the GRUB config and/or to reinstall the GRUB binary. There also is a limited interactive feature in GRUB, but it usually is not convenient at all to

Re: [Freedos-devel] XCOPY issue

Hi Tom, > whoever is responsible currently for XCOPY (Blair?): Good question! >if (chsize(fddest,filelength(fdsrc)) == -1) > ... > > Borland RTL fills the file with '\0', using a small buffer, and is > sloow. > > use > > filesize = filelength(fdsrc); > >

Re: [Freedos-devel] fdisk translation

Hi! We already have command line control for at least one of the fdisk variants which usually ship with FreeDOS, but using that to let the installer auto-kill all the data of the user gives me nightmares. You can simply use FDISK /? (who would have guessed it) to get a list of the command line

Re: [Freedos-devel] FDI Additional Languages

Hi Paul, > mmm is code page (437 is default, 850 is updated form, 1252 for Windows) In general, you can assume that 437 is what comes with your BIOS and graphics card BIOS while 850 is popular in DOS. Codepages of Windows are not popular in DOS :-) Maybe Mateusz or Aitor can say what the most

Re: [Freedos-devel] FreeDOS 1.2 ALL packages

Hi Rugxulo, while DJGPP is rather large, in particular if you include lots of sub-packages, I think FPC (Pascal) and FreeBASIC can be a lot smaller to install and OpenWatcom C in the middle... Also, I would assume that LFN drivers are part of the ALL install, so why not install ALL compilers?

Re: [Freedos-devel] FDINST

Hi Jerome, > COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS > DOS=HIGH > DOS=UMB > DOSDATA=UMB > DEVICE=C:\FDOS\BIN\HIMEMX.EXE > SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT I recommend to NOT use shellhigh with the XMS swap command.com: It already has a small RESIDENT

Re: [Freedos-devel] FreeDOS 1.2

Hi! Let me take your question as an excuse to talk a bit about support of non-English languages in any DOS, maybe some of our experts can add interesting comments and hints about the status of support in FreeDOS :-) Of course I also answer the original two questions, a bit further below ;-) >

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

>From Ben Hutchinson By minimal, I mean that the boot sector program, and the kernel (kernel.sys), don't do any displaying of text. All they need to do is set up the DOS interrupt vectors (so that they behave correctly just as with MS-DOS), and then load and execute the first

[Freedos-devel] FreeCOM beeping problem suspicion

Hi! This might be warming up long-fixed bugs, but at least in my personal DOSEMU installation, I notice that FreeCOM fails to beep. As Stas found some question about FreeCOM beeps, I looked at the code and notices that it explicitly beeps, instead of sending a BELL character to CON. The problem

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

Hi :-) >> I just downloaded the FDI-USB.ZIP file (now 178 MB .ZIP'd, unpacks >> to 256 MB .img). > Yeah, It’s a little big. But, on the other hand it is really hard to find > a USB stick under 512mb. So, other than download size, it isn’t to > important. However, that being said. It should be

Re: [Freedos-devel] FreeDOS 1.2 Preview 11

Hi! > I just don't think most people downloading FreeDOS really need FPC or > FBC or DJGPP (even if I do like them). I think they can just grab them > separately. But OW and NASM are officially recommended and much > smaller, so to those I have no complaints. FreeBasic has a rather cool QB

Re: [Freedos-devel] FDI USB stick

This is tricky - replacing the MBR when things already work would be dangerous! It can destroy boot menus and similar. I would say if there is NO MBR at all yet, it would be okay to automatically replace it. If there is some MBR, but the DOS partition is not yet marked as bootable, it would be a

Re: [Freedos-devel] Useful Tools for FreeDOS: Bilgisayarcılık DOS Tools

Iyi Günler Ercan! > REBOOT: A small program for rebooting on DOS. How does it differ from the FDAPM options for rebooting? > SCREEN: Screen mode changer on DOS. How does it differ from the MODE CON options for screen modes? Looking forward to the extra details :-) Regards, Eric >

Re: [Freedos-devel] FDI and FreeDOS 1.2

Hi Tom, Maarten, Jerome and Rugxulo, >> I emailed with Jim the other day. He is extremely busy at present. > fine. we should look for a new boss with more time to care. Not THAT, permanently, busy - Jim is busy at the MOMENT with some current news :-) Regarding Maarten's mail: No need for

Re: [Freedos-devel] FDI and FreeDOS 1.2

Hi Rugxulo et al, indeed xgrep and grep both have their uses... Regarding BWBASIC, current FreeBASIC is extremely cool while BWBASIC was small but somewhat sketchy, I would agree to drop BWBASIC from the distro. Note that the modern compilers (OpenWatcom, FPC (Pascal), Free- BASIC, DJGPP and so

Re: [Freedos-devel] FDI and FreeDOS 1.2

Hi! >> 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 anyone > anymore. Most DJGPP stuff mandatorily has to be cross-compiled > anyways, for various reasons. Still

Re: [Freedos-devel] FDI and FreeDOS 1.2

Hi Jerome, Jim et al, In view of available disk space on normal computers, I would like to interpret Jim's view in a broad sense: If ANY version of MS DOS had the feature and we have something to provide the same feature, then we should make it part of a BASE install. This includes DEBUG, EDIT,

Re: [Freedos-devel] FDI and FreeDOS 1.2

Hi Jerome, if Mateusz' repository has "500 MB of packages", then that would make a good choice for ALL as far as I am concerned: It easily fits on a CD and you get plenty of DOS stuff :-) Also, it should fit on most USB sticks as well. Maybe you could make a list of the LARGEST packages in the

Re: [Freedos-devel] FDI and FreeDOS 1.2

Hi Rugxulo, whether to repackage FPC using LZMA depends on whether it would unpack with the same hardware requirements that FPC has anyway and whether it really makes a difference. I could imagine that other files apart from the EXE take much of the space in FPC installations... What are the

[Freedos-devel] GUI shell - and ReactOS 0.4

Hi Maarten, whether you want to make a GUI shell depends on how happy you are with the existing solutions. Also, it depends on whether you mainly want to make a file manager (various, at least free, sometimes open, solutions already exist) or something where you can run graphical apps. Louis and

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

Hi Jose, to shorten that thread a bit, I would like to let you know that as far as I understood Maarten in off-list chats, he only ponders the creation of a graphical file manager, not of a GUI based desktop shell or even graphical operating system :-) Which leads to the question: Which COOL

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

Consider improving TriDOS. Maybe replace the built-in DPMI engine by a more mainstream, more comprehensive implementation, as well? http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/system tridos.zip 22k tridos_s.zip 371k source tridos.txt 3k direct link:

Re: [Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake platorm.

Hi Rugxulo et al, of course when I said that: >> In related news, the tab completion beep of FreeCOM can hang in DOSEMU. I was not looking for a work-around like that: > You could always zero out the "BEEP\0" string to disable the interactive > command, but the actual beeping code is still

Re: [Freedos-devel] Beep command can't stop sounding when run in Intel Skylelake platorm.

Hi :-) >> I’m BIOS vendor-AMI. >> >> When we test FreeDOS latest version, w found beep command can't stop >> sounding in Intel Skylake platform. In related news, the tab completion beep of FreeCOM can hang in DOSEMU. Regards, Eric

Re: [Freedos-devel] Compiling PowerPaint

Hi David, > I've changed to using the TP compatibility mode, and that has resolved > most of the problems. Now, my biggest problem is getting far pointers to > work, since they're only enabled for msdos. You probably only use those to access the graphics RAM. Check the web, 32 bit compilers

[Freedos-devel] making himemx and jemmex more foolproof on old bios versions

Hi experts, some interesting observations about an old 486 PC in the thread with Dimitris about "Which freedos on 486" on freedos-user... His BIOS answers with AH=86h, carry=UNCHANGED to int 15.e801, also leaving AL unchanged. So it seems to be a good idea to STC before INT 15 when doing the

Re: [Freedos-devel] [Freedos-user] after find, Error reading from drive A: DOS area: general failure: fixed

to illustrate his patch here? Thanks! Cheers, Eric > Hello Tom, > > Did you get hold of the maintainer? > > The package lists that as Eric Auer. But, that could be incorrect. > > I just haven’t heard anything for a couple days and was > wondering what was going o

Re: [Freedos-devel] Incompatibility issue due to FreeCom Dir command's output layout and Dosbox kernel limitations

For some extra details about the COUNTRY settings idea :-) > if the DOSBOX simulated DOS kernel is missing country functionality > and you do not want to boot freedos (because you do not want to use > diskimages) then you could load a TSR which answers COUNTRY requests > by freecom command.com

Re: [Freedos-devel] Incompatibility issue due to FreeCom Dir command's output layout and Dosbox kernel limitations

Bonsoir Denis, if the DOSBOX simulated DOS kernel is missing country functionality and you do not want to boot freedos (because you do not want to use diskimages) then you could load a TSR which answers COUNTRY requests by freecom command.com with country preferences of your choice :-) Dosbox

Re: [Freedos-devel] Incompatibility issue due to FreeCom Dir command's output layout and Dosbox kernel limitations

Hi Denis, country.sys is not a driver, it is a data file. So you can not load *that* with DEVLOAD. However, you can load other drivers, if that helps you. Read the manual of our DISPLAY and MODE: By first loading DISPLAY, then running MODE, you can switch fonts, in case codepage 437 is not

Re: [Freedos-devel] Incompatibility issue due to FreeCom Dir command's output layout and Dosbox kernel limitations

Hi everybody, see yet another FreeCOM feature request below... ;-) Thanks for filling in the table, Denis! A proof of concept tool for your task, for compilation with "NASM -O CANADA.COM CANADA.ASM" is implemented in the following code: > start:jmp short setup ; 100h > chain: > db

Re: [Freedos-devel] Incompatibility issue due to FreeCom Dir command's output layout and Dosbox kernel limitations

Hi Denis, you write that for getting 2 digit, AM/PM, space 1000s sep DIR output from freecom, you use SET DIRCMD=/-4 but failed to find a way to set COUNTRY to 002,863,c:\fdos\bin\country.sys in the context of DOSBOX. I still think it would be a lot easier to find out how to change DOSBOX

[Freedos-devel] FAT32 CHS boot sector problems since we introduced FAT32 LBA support?

Hi everybody, apparently the same SYS update which introduced FAT32 LBA support also broke FAT32 CHS support: On Dimitris' PC, CHS based FAT32 boot always fails, but his BIOS lacks LBA support. After installing MBR-based disk drivers to add LBA support and support for 4 instead of 2 harddisks,

Re: [Freedos-devel] FAT32 CHS boot sector problems since we introduced FAT32 LBA support?

Hi Jayden, both SYS (which puts boot sectors on drives) and the kernel already automatically detect LBA support. They both also already have options to manually select CHS or LBA. However, some old computers do not have LBA support. People with old computers must use CHS. The support for boot

Re: [Freedos-devel] Making a task switcher “from scratch”. Some problems..

Bonsoir Sebastien! > Since more days, I develop "from scratch" my "task switcher" on FreeDos in > asm/c++ > for preemption. Have you tried improving the existing TriDOS instead? > * I succeeded to create stack memory in array, for each > tasks added. > * I was not able to "switch" with

Re: [Freedos-devel] keyb us does not work

Hi people, it might be sort of obvious but... >> US is much more usable for us. >> >> But then, when I type >> keyb us >> >> the 2 output lines, seems to suggest that it worked. >> >> But I still have AZERTY (french) keyboard layout... You possibly loaded 2 instances of keyb - the easiest way

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

Hi Jerome, as said, I would recommend a little dialog in the installer for the MKEYB keyboard languages only, with a REM line in the config to let people enable other layouts with the bigger KEYB manually at a later moment. See the list here: > C:\>mkeyb /L > mKEYB 0.34 [Sep 18 2002] - all

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

Hi Juan, ... > Full Formatting (wiping all data) > [DEBUG] Formatting: Cylinder: 0 Head: 0 Sectors: 18 ... > [DEBUG] Formatting: Cylinder: 79 Head: 1 Sectors: 18 > 98% 100% > [DEBUG] File System Creation > [DEBUG] Boot Sector -> 0 > [DEBUG] FAT Sectors: 1 to 18 -> >0%

Re: [Freedos-devel] Getting ready for FreeDOS 1.2

Hi Maarten, > I got an error when trying to format a floppy in Virtualbox (which is > a completely logical error). It was a int 0x13 write error. But after > that the system hangs. It is 'fatal' but I would think fatal for that > piece of software. So can't it go back an try to go to [a

Re: [Freedos-devel] development workflow?

Hi Wolfram, > And is there something like a release script for tools? Looking at bug > #142 ("MODE command - can't set "STOP=2" ), the fix is really trivial > and the patch is already there. Just the release missing. I am sure that I have already sent that to people taking care of the new

[Freedos-devel] slow FreeDOS install - was: FreeDOS 1.2-RC1 on Hyper-V 2012 R2

Hi everybody, update on the 2 Nov mail by Matthew: > The release candidate announcement encouraged people to try FreeDOS out > and report any problems, so here I am to say that I successfully booted > and installed 1.2-RC1 in a generation-1 Hyper-V 2012 R2 virtual machine > using the ISO image.

<    2   3   4   5   6   7   8   9   10   11   >