Re: [Freedos-kernel] Fwd: [Freedos-user] Any interest in 486, 586, 686 kernels?
Louis Santillan schreef op 5-5-2013 18:28: Whoops, didn't realize that I replied to fd-user instead of kernel. One other note, all kernels are slightly bigger withe options I set. I guess it depends on what the compilers do: [1] optimize for certain processor architecture(s) [2] also keep backwards compatibility or not with lowest desired level if [2] then the binary might be larger on disk. If someone likes a real challenge, a smaller kernel can be produced using UPX --8086 --lzma --ultra-brute (instead of UPX --8086 --best) but the end-result is not bootable, requiring a decompressor stub. Savings is about 3KB disk footprint. As for the MEMDISK support there's additional support implemented at https://github.com/PerditionC/fdkernel but it requires me to first create additional testcases using some kind of floppy image file. Basically it allows specifying a CONFIG.SYS line at Syslinux menu so you can alternate memory driver in a menu for example, or specify UMB regions, that kind of stuff DEVICE?= and JEMMEX are quite revealing in option parsing :) (and some ctrl-alt-del issues crashing FreeCOM in VMware) Bernd -- Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2 ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Commit 1705
Op 19-2-2012 10:57, dos386 schreef:
(untested, just history.txt __IS__ updated this time)
but nobody annouced it :-D
It's a secret to everybody!
(hm, too much Zelda)
The pre-386/memdisk detection is a good thing, finally a unified kernel.
Right until someone does a append FD={INSTALL=FORMAT C: /Z:SERIOUSLY}
Having 2041 out when maintainers had time for it relieves them from
pressure for implementing stuff and releasing new versions.
Bernd
--
Virtualization Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Freedos-kernel mailing list
Freedos-kernel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] screen full of kernel warnings
Could someone please verify that a screen full of kernel warnings is shown when running option 2 from the following bootdisk? : [ http://www.reactos.org/bugzilla/attachment.cgi?id=7374 ]. A simple workaround I could do is commenting out the textline that gets printed and recompile. Cause of these warnings is that the bootdisk is hiding int13 drives (which I do on purpose to not mount any harddisk FAT partitions at boot-time as I like to use C: for a ramdisk occasionally). Bernd -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] [Freedos-user] Re : Support for 4k byte sectors
Op 14-1-2012 19:48, Bertho Grandpied schreef: It's been a few days and I'm surprised my first mail hasn't been acknowledged in any way, let alone answered; strange, I've been part of various lists before, usually 'newbies' are greeted rather than ignored altogether. So I'll reiterate and articulate the above question just in case it was not clear : have I done something wrong ? should I try posting to the kernel or developers lists instead ? Truth is we're not sure, this 4K sector size thing comes in several versions: 1) emulation with aligned 512byte sector emulation 2) emulation with non-aligned 512byte sector emulation 3) native 4K (especially USB bridges apparently) In other words, this is asking what the plan is for the FreeDOS kernel to be able to mount mass storage devices having 4 kilobytes per sector ? If the disk has traditional BIOS partitioning layout (MBR, primary/logical partitions with FAT16/FAT32 filesystems) then it might be possible for the kernel to work with this as long as it is a data disk. Booting from a partition without 512byte sector-size is probably more challenging, let alone guarantee file(-system) integrity and disk manipulating (defragmentation programs, filesystem checkers like CHKDSK and DOSFSCHK). GPT partitioning scheme isn't supported at all (nor is EFI/UEFI without BIOS emulation). As said in previous message, I for one am ready to test development kernels against my USB disk appliance (1 TiB Iomega Prestige). freedos-kernel would be most appropriate list as the developers on there have most expertise. However they're also the ones who are rarely present due to other interests or obligations, so getting answers can take a while. You could also try freedos-devel for this specific technical question but answers might take as long as getting answers on the users list. People usually don't answer if they don't have the correct answer, thus things stay quiet for a while. -- RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] FreeDOS 1.1 released
I'm happy to announce that the FreeDOS 1.1 distribution is finally available, including sources to all packages. You'll notice it's quite a basic version, lacking some features and programs that were present in the 1.0 release. I'm planning on restoring functionality in the 1.2 release. Please see www.freedos.org for more information about this 40MB CD-ROM image. Happy new year everyone! Bernd -- Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] [Freedos-devel] [PATCH] kernel - only print suspect partition warnings if FORCELBA is not in use
Op 18-12-2011 23:31, Pete Batard schreef: 1. I am the developer of Rufus [1], which is a DOS-bootable USB flash drive creation utility for Windows. One of the versions of Rufus embeds FreeDOS (kernel + freecom) for installation as the default DOS, in lieu of the WinMe DOS that can be extracted from diskcopy.dll. I've recently learned about your Rufus program from the Reboot.pro forums, it seems quite interesting indeed. Would likely be a nice addition from ReactOS (which you made use of already) but as that's GPL2 while your program is GPL3 that won't be possible I guess. 3. All the machines I have tried so far report the CHS vs LBA computed mismatch warnings. Considering that first time FreeDOS users might be put off because of these benign warnings, I would very much like to avoid them. There's a list of warnings indeed. A big one at that, especially when using syslinux's nopassany directive to hide physical disk drive units. Could this patch be considered for the mainline tree then? I can't answer this, as I'm no developer. It could be an interesting addition for kernel 2041 if any kernel maintainer is still active occasionally. PS: is there a reason why one must have an AUTOEXEC.BAT present, even a blank one, to avoid the prompts for datetime in FreeCOM? What is the purpose of mandatory prompting for those? Remove your CMOS battery and you'll see. Basicly, ancient machines often had no battery and yet needed to have a time and date set. I guess FreeDOS follows MSDOS design in this aspect. -- Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] possible to disable initdisk?
I'm in a situation where I got Syslinux bootloader on an USB flash drive. It loads the MEMDISK ramdisk module with a floppy image as contents which is then executed (as drive A:). I'd like to get into a situation where the USB flash disks doesn't get a driveletter assigned by the kernel when it loads but only after the DOS USB driver stack is loaded. To that end there seem to be 2 options: 1) /memdisk initrd=floppy.img pause followed by removing USB disk and pressing a key to continue. Later on, insert again. 2) keep kernel disk scanning/enumerating code intact but don't execute it for drive 0x80 and up, at startup at least. This way the drivers can be loaded, set interface to max supported speed, recognise devices, and get a driveletter assigned (C: likely) Is the kernel designed to allow such a specific scenario #2 ? It's very un-DOS-like to delay giving out driveletters. Initdisk.c seems to suggest scanning can be disabled [SCAN_PRIMARY], but I guess that's a permanent option instead of only for boot-time. -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] possible to disable initdisk?
Op 22-8-2011 0:47, Eric Auer schreef: You can hook int 13 function 8 (get drive parameters) and make sure that for dl = 80 or higher, it always returns carry set and dl = 0 to pretend having no harddisks. Of course DOS does a lot of work for you to parse partitions, so it is a bit odd to pretend you have none only to do that again manually later. No idea how to do such a thing, all modifications would have to happen at the kernel I guess as that's the first thing loading, and actually assigning those driveletters. Then, again, Syslinux/memdisk documentation lists a nopassany parameter to disable showing harddisk. Gotta test that next I guess :) You could also do the above and/or temporarily make int 13 access to all harddisks behave as if all disks are empty bit buckets. I hope you will not try to format later ;-) I've had a DIR E: at some point and ended up with batchfile content being listed. Talk about memory corruption.. There is no built-in function in the kernel, although you can SYS CONFIG the lba support away and hide your partitions after the first 1024 cylinders. Later, when you load USB drivers to do the processing on DOS block device level, you can get along completely without int 13 CHS / LBA access anyway, depending on what style of USB drivers you use, I guess. Again, in this scenario, the USB driver will have to do all partition table (MBR, chain of extra partitions) processing itself because DOS and int 13 itself has not int 13 disk hot-plugging. Luckily it is okay for DOS to have many drive letters managed by 1 driver. The USB drive is typically formatted with FAT32 so all FAT32/LBA code needs to stay intact or I can't access the filesystem on the USB flash drive after loading drivers. Using a FAT16 kernel would've been too easy, hehe. The scan constants are only for doing some things in some passes of scanning the partition table and other things in other, with some things being skipped then. It is not about skipping disks. There's an option for *showing* partition info (of which the output is can't get partition info half of the time anyway), as well as an option for the scan order (MSDOS style, or general style), unfortunately nothing for only scanning partial stuff. I'll try the Syslinux stuff for starters, see if it works. Thanks for your response -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] possible to disable initdisk?
Op 22-8-2011 0:58, Bernd Blaauw schreef: Then, again, Syslinux/memdisk documentation lists a nopassany parameter to disable showing harddisk. Gotta test that next I guess :) This works like a charm, however FreeDOS kernel happily lists about 50 lines with 'illegal partition table, drive nn, sector 00' FDISK also results in errorlevel 6 (no harddisk present) as intended. The USB driver stack seems to work except for happily killing keyboard input upon access to the USB drive. Not tested FDISK yet. Anyway, one issue semi-solved by 'nopassany' parameter, sleep well :) -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Kernel 2040 released
Op 20-7-2011 3:50, Bart Oldeman schreef: It's probably best to make things explicit (unless the goal is a true Win32-DOS cross-compile), using DOS16 utilities, by changing the last part of mkfiles\watcom.mak to: CFLAGS1 = -os-s-wx-bt=dos # *Implicit Rules* .obj.exe: $(BINPATH)\wlink sys dos f $ lib $(SUPPL_LIB_PATH)\SUPPL_$(SHELL_MMODEL).LIB op q .c.obj: $(CC) $ @$(CFG) But I haven't tested this! And now the fun part: compiling on Windows x64. No support for running 16bit programs at all. -- 10 Tips for Better Web Security Learn 10 ways to better secure your business today. Topics covered include: Web security, SSL, hacker attacks Denial of Service (DoS), private keys, security Microsoft Exchange, secure Instant Messaging, and much more. http://www.accelacomm.com/jaw/sfnl/114/51426210/ ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] [Freedos-user] Kernel 2040 16-bit
Op 14-7-2011 5:09, Marcos Favero Florence de Barros schreef: I'm now using the 32-bit 2040 kernel, because none of these errors has ever appeared under the previous 32-bit kernels, and I'm hoping they will not appear under the new one either [fingers crossed]. Any advice is welcome. Thanks for reporting the issues you're experiencing with the FAT16 kernels, multiple versions. Do you have a way of verifying file/filesystem/disk integrity outside of FreeDOS? FreeDOS has no 32bit kernels, there's a FreeDOS32 project somewhere but that hasn't gotten very far yet. The 16 and 32 for FreeDOS kernels purely indicate what they support: * either FAT12 and FAT16 filesystems * or FAT12 and FAT16, but also FAT32 filesystems (or rather partitions using these filesystems) It's usually fine to run FAT32-enabled kernels. However that's no reason to have FAT16-only kernels contain certain bugs. I've not tried FAT16 kernel and CHKDSK as you have. I've not tried using CHKDSK either on FAT32 drives, doubt it supports it. Latest FreeDOS CHKDSK is 0.92 ( http://users.telenet.be/imre/FreeDOS/ckdsk092.zip ). maybe I'll find some opportunity to try and see if I can reproduce your issues (CHKDSK on FAT16 kernels reporting errors with files, while on FAT32 kernels no such issues). Bernd -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] [Freedos-devel] confused by NLS-settings
Op 15-7-2011 0:42, Eduardo Casino schreef: Hi Bernd, hello Eduardo, good to see you're around :) Because it is harmless. Is it really necessary to treat that case in a different manner than a successful installation? If it is, I'll look into that, it is trivial to modify. it's not really necessary, was just looking at a way to branch from a hey I've already run this part earlier and it's not necessary to run it a 2nd time. Nope. INT2F/122b and INT2f/122d are not implemented in kernel 2040 (they were in 2039) Don't use NLSFUNC with kernel 2040. Ouch. Good to know, I'll take this into account. NLSFUNC seemed to work though initially, it's only CHCP that generates the errors. However maybe it explains andy KEYB or DISPLAY difficulties. -- AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on Lean Startup Secrets Revealed. This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Kernel 2040 released
Op 10-7-2011 13:11, Eric Auer schreef: Hi dos386, Ninja-ing thread here slightly: Can kernel 2040 please be mirrored to Ibilio? Can't be found yet at http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/kernel/ -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Kernel 2040 released
Op 10-7-2011 3:10, dos386 schreef:
Anyone can please upload the __correct__ HISTORY.TXT file for
the 2040 kernel release on some place where it is easily discoverable ?
Both SF and fdos.org ?
http://sourceforge.net/projects/freedos/files/Kernel/2040/
It's history.txt inside the doc directory, inside the zip archive.
I'm still to test if DEVICEHIGH/SHELLHIGH and DEVLOAD /H work as
expected, with various kernels and devload versions.
Changes Jeremy
* r1501 sys/sys.c: correct return value from NULL to FALSE -
fix compile with OW1.9
* r1500 docs/sys.txt, sys/sys.c:
handle case when source not specified but filename for boot
sector is given (sys X: bootfile.bin)
+ Changes Bart
* r1569 kernel/{config.c,kernel.asm,init-mod.h,globals.h}:
Allocate bigger chunk of memory for INSTALL for __WATCOMC__
because the memory layout is different from other compilers.
Fixes issues mentioned by Bret Johnson and Christian Masloch
in freedos-user/freedos-kernel.
* r1568 kernel/asmsupt.asm, mkfiles/owlinux.mak: Make sure the
DOS native and Linux cross-builds produce identical binaries.
* r1567 drivers/rdpcclk.asm,kernel/{asmsupt,entry,irqstack,kernel,
nls_hc}.asm, kernel/makefile:
Remove useless END from nls_hc.asm, add explicit byte
overrides for older versions of NASM for more compact code,
and adjust silent relocation segments.
* r1565 sys/sys.c: Change // to /* comments for Turbo C compatibility.
* r1564 kernel/dosfns.c: If handle valid, close file in PSP
table before the low-level close + (perhaps) critical error.
Avoids closing the file twice (and hitting the critical
error twice) on abort/program termination.
Also, close can only return error 6 (DE_INVLDHNDL), not 5
(DE_ACCESS), see RBIL.
* r1563 kernel/task.c: From Christian Masloch:
set flags to 0x200 (IF set) when transferring to int22
termination address.
* r1562 kernel/fatfs.c: Check errors for callers of dir_write
and shrink_file. Fixes: Bug: File creation does not check
whether buffers are written correctly
(http://www.bttr-software.de/forum/forum_entry.php?id=9783)
* r1561 kernel/blockio.c, kernel/fatdir.c:
No longer force flush1() and dir_write_update() to return
TRUE if there were disk write errors. Part 1 for fixing
http://www.bttr-software.de/forum/forum_entry.php?id=9783
Bug: File creation does not check whether buffers are
written correctly
* r1560 kernel/kernel.asm:
Enlarge clock and block driver stacks. Thanks to Damien Guibouret
damien.guibou...@partition-saving.com.
* r1559 kernel/fatfs.c: Fix value that is used before being initialised.
This lead to a drive to not be considered as FAT32 despite it is
(or vice-versa).
Thanks to Damien Guibouret damien.guibou...@partition-saving.com.
* r1499 kernel/makefile:
With the stack changes the DOS segment has moved to 0x79.
* r1498 kernel/irqstack.asm:
New irqstack.asm: irq 2, 3, 4, 5, 6, 10, 11, 12, 14, 15 now
use the IBM interrupt sharing protocol for STACKS. Affect
int 2 too, but not IRQ 7 (INT 0fh) and IRQ 9 (INT 71h)
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
___
Freedos-kernel mailing list
Freedos-kernel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] driveletter assignment?
Is it possible to have the FreeDOS kernel start with driveletter assignment from specific interfaces, or are we stuck with what BIOS offers us? When booting from USB, I've got multiple options: 1) syslinux + memdisk + floppy image 2) syslinux + memdisk + ISO file 3) syslinux + chain.c32 + kernel 4) syslinux + bootsector + kernel What happens is that BIOS presents a USB flash disk as 1st harddisk instead of IDE/SATA harddisk, with consequences of FDISK and driveletter assignments. Situations 3 and 4 as described above can't be helped, BIOS presents USB flash drive as 1st harddisk, FreeDOS kernel recognises it as C: and you happily boot from C: (only very small capacity USB drives used to boot as A:) Situations 1 and 2 however make you end up with booting from a virtual diskette (A:). However BIOS still presents the USB disk as first harddisk, and thus FreeDOS lists it as C:. My question thus is: can driveletter assignment be tweaked to start with primary partitions on SATA/IDE drives, or are we stuck with what BIOS presents us without ability to swap/shift drives? -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] [Freedos-user] New kernel
Op 30-6-2011 1:29, Santiago Almenara schreef: Thanks Eric! I'll try 2040 instead of 2030. Just for everyone's information, I'm still able to hit a double BAD FAT INFO - Run CHKDSK error message from the kernel occasionally The only situation in which I sometimes am able to trigger that, is by booting from USB flash drive (at 1.1 speeds, bah) and then deleting a 8MB (or more) ISO file from root of that directory. In addition to that the USB flashdrive and keyboard disappear, forcing a system reboot through the case's hardware button. Not narrowed down this situation, but wasn't using USB drivers. However, for general use 2040 should be perfectly safe as floppy and harddisk controllers aren't such a mess as legacy bios emulation. -- All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Kernel 2040 released
Op 25-6-2011 16:06, Kenneth J. Davis schreef: Hello all. Kernel 2040 has been tagged and should be made available on Sourceforge file releases within next few days. Nice to have an official updated kernel. Also available for download at fdos.org: installer compatible form - http://www.fdos.org/kernel/package/ same as sf releases - http://www.fdos.org/kernel/release/LATEST/ So this is a release with new official versions of: * KERNEL * SYS * COUNTRY.SYS ( same as http://eduardocasino.es/index.php?option=com_contentview=categorylayout=blogid=4Itemid=9 ? ) Are there any verified/stable working compiled versions available of the following? * COMMAND (there's an openwatcom CVS/SVN version somewhere?) * SHARE (thought there were 2 versions or so?) * NLSFUNC Note: these releases have not been compiled with the memdisk configuration checking as these are 8086 compatible builds. I will make available 386+ builds with it enabled within a 386 subdirectory. Good to know, so we don't end up with a 386 kernel on bootdisks. Ofcourse the preference is a 'universal' kernel supporting everything :) Thank you, Jeremy Davis Just for fun, try the following 2 statements in config.sys at same time, execute both and try executing a file in path. !SET PATH=C:\FDOS\BIN 1?SET PATH=C:\FDOS\BIN Also interesting is DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST FASTBOOT when booting from C:, followed by DIR A: Bernd -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense.. http://p.sf.net/sfu/splunk-d2d-c1 ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Intent to tag 2040 release
Op 21-6-2011 4:24, perditi...@gmail.com schreef: If there are no objections, then this week (tomorrow if I have time) I plan to tag the kernel at 2040 and make release builds available. By all means go ahead :) I suppose it includes Bart's earlier fixes, your modifications for Memdisk arguments and Bart's later fixes based on I think dos386's feedback (could be Christian Masloch, can't recall right now who reported). Not 100% convinced that file corruption is gone as I'm experiencing crosslinked files on USB flash disk, for example suddenly loosing all contents of a batch file. I'm not sure if that's my machine to blame, FreeDOS, or USB in general. Still, go ahead. Many issues are fixed and people's usage of a new kernel will get you some new feedback :) -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
dos386 schreef: PS: I would like to quote IBID_AG 2. Congratulations on a great kernel/OS 4. I would rather see more of the features from 2037 in stable List ??? * external Country.sys support (including MODE, DISPLAY, NLSFUNC etc) * That FNODES stuff (Bart seems to be working occasionally on this, but now based on 2038) * Windows 3.1x support WfW support in stable, these might be handy. WtF is WfW ??? Windows for Workgroups , which is a flavor of Microsoft Windows 3.11 And SHSUCDX with UDF support does seem higher priority. UDF-CDEX would be separate from kernel development As it always was. What does UDF support do? Enable copying video DVD? or enable packetwriting? Actually I had forgotten to point this one: there used to be SYS 3.5 or 3.6 back in 2005 ... that's what EDR-DOS SYS was forked from ;-) Jeremy Davis created SYS 3.5 yes with support for several other DOS-based operating systems by generating their bootsectors. Found some old info at my ancient Blog on Jeremy's server [ http://wiki.fdos.org/Blog/Bernd ] Indeed DR-DOS got its SYS from here. I seem to recall that SYS did not support FAT32 bootsectors for Windows 95OSR2.x and Windows98/98SE/ME. As we're on the kernel list anyway, would anyone be able to tell me if it's possible to modify the kernel enough with additional code so that it could read a Isolinux/Memdisk commandline including arguments? Followed by searching for a config=x option where x=[0..9] and then executing that menu option in (fd)config.sys. The benefit of this is taking away 1 keypress Currently it's : 1) select to boot FreeDOS from CD , 2) select which menu option you want. I'd rather create multiple Isolinux options which would then tell the same FreeDOS diskette image what to do, in config.sys already. Eric Auer had a commandline utility for this, which is already quite usefull, but means there's no support for loading device drivers (and specially DOS=HIGH, DOS=UMB, the kernel and FreeCOM , XMS saves a lot of memory) Bernd -- OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2038 discussion stuck? history.txt changes
Eric Auer schreef: Hi dos386! Can you forward details about that dmidecode / bttr forum thing? http://www.bttr-software.de/ http://www.bttr-software.de/forum/forum.php software: http://www.bttr-software.de/misc/dmide29b.zip (I guess) Nowadays a hardware diagnostics tool at boottime seems to be HDT, for Syslinux [ http://syslinux.zytor.com/wiki/index.php/Hdt_(Hardware_Detection_Tool) ], with a so-called COM32 module at http://konilope.linuxeries.org/hdt/hdt_0_3_3.c32 Bernd -- OpenSolaris 2009.06 is a cutting edge operating system for enterprises looking to deploy the next generation of Solaris that includes the latest innovations from Sun and the OpenSource community. Download a copy and enjoy capabilities such as Networking, Storage and Virtualization. Go to: http://p.sf.net/sfu/opensolaris-get ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] ASUS problem
Alain M. schreef: I use regularly FreeDOS in users instalations with brand new, superfast motherboards. The aplication is heavy Database usage and FreeDOS is prerforming better then MS-DOS... Great. Is switching kernel the only thing that's relevant or did you switch any other components as well? There is a systematic problem only with ASUS motherboards (in the last 3 years aprox.) System crashes, files get corrupted, etc :( :( Recent motherboards can be very picky about system memory. My Striker Extreme board won't accept any memory modules into its 4th slot. (or doesn't like dualchannel perhaps). Does anyone have any information or Idea about this problem? Would any of Jack's driver help? I don't know your usage cases of DOS + database. Provide more details if possible. Also try starting troubleshooting your system. Memtest+ could do miracles to test memory. Start with 1 memory module, test each module, then extend to 2 modules installed at same time, etc. Another option is to exclude harddisk access by using a RAMDISK, so there's no harddisk involved, nor cache, IDE controller, PCI bus, etc (install your DB on ramdisk, then use it as if it was on harddisk - just for testing. Not permanent ofcourse as changes get lost upon system reboot if you don't perform a manual backup). I'm not sure how to detect corruption of a filesystem explicitly. Bernd -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Hello again
Eric Auer schreef: Still no reason to add experimental things to stable now :-) The solution is easy: Add it to the UNSTABLE fork and, while doing so, show that there are people who are interested in new experiments with DOS! This will also draw more attention to this branch and make it more likely that safe goodies can be found in there and ported to stable and that on the other hand UNSTABLE will finally get updated with some of the fixes that stable received in the last few years... :-) Leave 2037 as a relic, go fork 2038 to add your experimental issues and make them appear in 2039 or 2040 :) Additionally, take things from 2037 as you like I guess. Seems rather strange to have a decent 2038 now, and then to have to resort to changing 2037 if you want to add experimental features. -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Hello again
Eric Auer schreef: Maybe we should have DVD playing software and a DVD- compatible version of DOSCDROAST first... :-p. And I repeat my earlier argument: Just split the bluray image into a few files, very easy :-). What's DOSCDROAST exactly? So far I'm quite happy with Blair's port of CDRKIT, with only drawback that we have to rely on drivers that we cannot supply and distribute (due to licensing matters), but that users have to provide themselves. For the IDE/EIDE/SATA/PATA/ATA/ATAPI ASPI shim, this is ASPI.SYS by Oaktech. Any opensource shim or addition to UIDE.SYS is not known to me, and at least mr Jack R Ellis isn't too much a fan of ASPI due to personal reasons so he's not inclined to add that to his driver. For other technologies, you'd usually need to load a driver for the mass storage controller (be it USB, FireWire, SCSI, whatever) which implements SCSIMGR$ blockdevice. This seems to be 3rdparty in all cases. Additionally you'd need a cd-rom driver also that chains to the SCSIMGR$. No opensource version of this is known to me, think there were plans for ATAPICDD in the past to have this. As for GENISOIMAGE (mkisofs basicly, creates ISO out of directory tree) I've finally found the -split-output option, which should result in FDBASECD.0[01..99], consisting of 1GB files each, I think, rather than FDBASECD.ISO The, through ASPI/SCSI, recording software WODIM should happily accept this .001 file and appends all further parts automatically on the same session (according to documentation, not tried yet). Jason Hood's OMI program is able to store entire DVD/Blueray on harddisk as a collection of 1GB files if the file system has issues with larger files. However it seems to be a custom format, and further usable only by shsudvdhd disk mounting utility. I wonder if Jason's programs (OMI, SHSUCDHD) could be made compatible with GENISOMAGE output or WODIM's expected input when considering split files. Would MPXPLAY support DVD somehow maybe? I know of no DOS players other than that 1minute-or-so trial program at http://www.freeweb.hu/doscdroast/dvd4dos.htm Have some developers vanished completely btw? Not seen any activity by Arkady for ages :) Bernd -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] fresh freedos svn kernel updates
Eric Auer schreef: Hi Bernd, *your KERNEL.SYS in renewed archive works fine, nice job. [ http://www.coli.uni-saarland.de/~eric/ke2007jul21.zip ] *JEMMEX v5.64 can be compressed and works, can't see it listed in MEM /C ( MEM /C /N ) listing though, maybe it\s hiding under SYSTEM :) (UMBs provided, Shellhigh works with Freecom loaded high) *No idea how to get Fastboot working, any reference platform/emulator to see it in action? (didn't try the additional driver as Eric said kernel binary should work out of the box) Bernd - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] fresh freedos svn kernel updates
Eric Auer schreef: Hi Rugxulo, Robert, kernel people, Hello Eric, branch of the kernel? Rugxulo, KEYBUF should obsolete having a keyboard extender around. Kernel people, IDLEHALT does not obsolete FDAPM APMDOS but it gives you some energy-saving even without FDAPM. I hope both can be used in parallel w/o problems. What's a keyboard extender exactly and what does it do? Sample kernel binary: www.coli.uni-saarland.de/~eric/ke2007jul21.zip Only KERNEL2.SYS works for me, better than the Fastboot supporting kernel I downloaded (I think) a while ago. KERNEL.SYS in your archive hangs my machine at the HMA/BUFFERS message. 1. This should make Robert happy. The kernel now produces messages as UMBs unavailable! instead of (Dutch) UMB's unavailable! Dutch is the only language where plural's are correct, I think. Depends, normally the [s] is added, but some english terms like 'baby' are plural with ['s]. Also depends what the kernel is trying to say: *UMB ['s/is] unavailable *UMBs unavailable *UMBs are unavailable 3. Usage: keybuf=n[,m] where n is in 0xac-0xde or 0x106-0x1de range and m is = 0x200 Relocate keyboard buffer from the default location at 0x40:0x1e-0x3e to 0x40:n-m. The buffer must be more than 32 bytes and must not touch offsets 0x100-0x105. Default for m is next multiple of 0x100 after n ... A reasonably safe choice should be keybuf=0x140,0x1c0. what's the benefit of this? a larger keyboard input buffer like Dos 7.10 (1024chars) ? All in all I'd suggest finding out what changed which makes Bochs and my system unhappy. Thanks for having a usable FreeDOS system again. Now to make that DOS Sioux webserver running from a Ramdisk :) Slightly offtopic questions: are Japheth's drivers compressed by UPX or do they support compression? 35KB disksize for a driver is a bit much. A single binary '286 XMS driver' + '386 XMS driver' + '386 EMS/UMB/VCPI/VDS driver' + '386 XMS/EMS' driver would be fun :) Bernd - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] fresh freedos svn kernel updates
Eric Auer schreef: Please test :-) You relying on me to test or does this new binary work for you in Bochs? Sample kernel binary: www.coli.uni-saarland.de/~eric/ke2007jul21.zip same filename yet updated release? Bernd - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] please change the default freecom and increase the kernel version
David O'Shea schreef: It says The UNSTABLE (aka development) branch is what I refer to as the development kernel (kernels with w suffix). It looks like those kernels actually have .dev or .dbgdev in them, right? There doesn't seem to be a discussion of the naming convention for FreeCOM. well, we have: kernel 2034, 2035 released by Bart kernel 2035A released by Jeremy kernel 2035B by Jeremy (2035A + stable features backported from 2035W) kernel 2035W by Jeremy, experimental/development line FreeCOM 0.82, 0.82patchlevel 1, 0.82pl2, 0.82pl3 by Steffen Kaiser flavour 1: XMS-swapping, 8086+ flavour 2: KSSF-swapping, 8086+ FreeCOM 0.84prerelease (CVS) by Jeremy flavour 1: XMS-swapping, 8086+, no LH, no ALIAS flavour 2: XMS-swapping, 80186+, full-featured flavour 3: KSSF-swapping, 8086+, full-featured, no binary available. I take it from the fact that we group the stable and development kernel/freecom/sys separately that you should only use a stable kernel with a stable freecom and a development kernel with a development freecom. Is this correct? Maybe we shoudl say it explicitly. We should probably also say that you can mix development and debug development files (at least I assume that that is correct). Everything may be mixed. What I'm afraid of is 80186+/80386+ binaries which somehow end up being transferred to older machines (8086). Then it might not work (kernel for example). That's why 8086-kernel and 8086-FreeCOM are provided by default. Only (major!) drawback to that is no LH functionality in FreeCOM. Bernd --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] please change the default freecom and increase the kernel version
Bart Oldeman schreef: To be fair I found Eric's email rather demanding. In general if you want things to happen in the NEAR future you either have to do it yourself or pay big bucks, not just pizza money. Certainly when the kernel doesn't have a real maintainer (just an interim one who does what he can when he has time). reason was for better bug reporting. People often only report the FreeDOS version, or something out of VER. Hardly ever VER /R, let alone the production date of a (CVS) kernel which can only be viewed at boottime. Personally I find it rather questionable that an unstable CVS snapshot is used for the official FreeDOS distribution, but that's just me, I would just stick with the latest official kernel version, with perhaps a few custom patches for important bug fixes, unless the (interim) maintainer has blessed the CVS as fit for general (non-developer) use. Or perhaps I'm missing something obvious, I only take a half eye on FreeDOS these days. Features. Jeremy is still working on implementing features in unstable tree as a voluntary interim maintainer (which means there's no guarantee that bugreports will be handled whatsoever), and on top of that he's also bigfixing FreeCOM, which has several severe problems. Luckily Erwin Veermans and Blair Campbell are also very capable of working with these components. None of this has been added/backported to 2035 official release or 2035A official release and then released under a brand new version number. The unstable kernel adds a lot of features not found in 2035/2035A: *NLS stuff (NLSfunc, country, display, chcp, mode) *silently working with SHSUFDRV (i-node complaints) *and a lot more things I currently can't remember, busy with study and playing World of Warcraft frequently. Bart Bernd --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] re: Re: reload partition table and reassign drive letters
Eric Auer schreef: Hi, yes, FreeCOM can handle changing drive letters. The PROBLEM is that harddisk letters are handled by a kernel driver which can only do one hole-free range of drive letters. So if you could enable a new partition on the fly, all subsequent drive letters would move. HOWEVER, you are free to write a RAMDISK style driver which MOUNTS an arbitrary FAT partition: You only have to provide sector read/write and calculate the right (read: offset by partition start position) sector numbers, and the kernel will do the rest. Such a driver can even be loaded from the prompt with devload... except it cannot re-assign already used driveletters I guess. Same as Jason Hood's disk mounting tools cannot use B:, the kernel already claims it as alternative for A:. There's no if B: refers to same drive as A:, then allow another disk mounting tool to install itself as B: (hm, nice idea. No idea if possible). Kernel can access the partition table, thus also count/determine how many FAT partitions are present. 1st FAT partition will be C:. So a certain range must be free [4 partitions: C..F ]. If C..F are still available, dismount + remount. I like this remount idea, it proves how much we consider the existing limits of DOS, even while writing replacement components that optionally may behave smarter/better as long as it doesn't hurt compatibility. Quarterdeck's quickboot was such an idea, and Eric implemented something like it in FDAPM (is there a single known case of hotboot works though?). Quickboot ment skip BIOS part of boot process upon warm reboot. DOS disk partitioning tools only insist on rebooting because the kernel only recognizes harddisk partitions upon initialisation of the kernel, not at runtime. If the FreeDOS kernel would allow rescanning somehow, FreeDOS Fdisk could be made to not reboot if user decides so. I realize the investment/profit ratio is very bad, which would mean this option would not be implemented any time soon, and would probably be a patch contributed by an 'external' developer instead of regular people working on the kernel. @echo off echo FAT partition on harddisk required, as drive C: if exist c:\nul goto skipfdsk fdisk rem let the used DOS kernel re-initialise driveletters assigned to disk partitions. Don't touch A,B, and driveletters installed by drivers. Fdisk /rescanharddisks if not exist c:\nul fdisk /reboot goto skipfdsk :skipfdsk a driver for mount/initialisation also sounds nice. Eric Bernd --- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Support for SATA disks?
Abrahan Sanjuas schreef: Is this feature missing on FreeDOS? if BIOS has support, DOS supports it. you might need the UDMA2.SYS driver for really large harddisks though. Bernd --- SF.Net email is sponsored by: Tell us your software development plans! Take this survey and enter to win a one-year sub to SourceForge.net Plus IDC's 2005 look-ahead and a copy of this survey Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel question
Jeffrey Chao schreef: I use sys config kernel.sys bootharddiskseconds=5 to configure the freedos kernel. Then I use this freedos as floppy image to burn a bootable CD. Then: what kind of bootloader is used on the cdrom, or what type of emulation does the cdrom use for diskette? Config: IDE CD-ROM and an empty floppy drive attached to my system. Booting with our SuperCD and wait for it to time out from the 5sec count, then system will hang after the count. Which kernel exactly? run VER /R on a succesfull boot. If IDE HDD is attached, then there is no problem. What are your devices (all IDE?) and how are they attached to your computer HDD: primary master? CDR: secondary master? Bernd --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: Re: [Freedos-cvs] kernel/kernel inthndlr.c,1.87.2.12,1.87.2.13
Eric Auer schreef: PS: Which kernels contain the DOSLFN compatibility patch (improved xBPB/DPB initialization and set extended error code implemented), only the development kernels at www.fdos.org/kernel, I think. Jeremy has been active lately. Only thing missing by default is that IF a compressor is used, SYS should also be compressed by it (UPX, Apack). did somebody contact GRUB people about 0.0.35 vs. 1.0.35 version ID, why exactly? I cannot connect to GRUB4DOS site. to work with DOS=HIGH (I seem to remember that recompiling with either Toms or my KITTEN version or recompiling ZLIB or both was what Bob did to fix the bug... maybe there are OTHER programs with CATS affected? Which programs still use CATS instead of KITTEN? Symptom was a CRASH when using HTMLHELP several times on SOME systems if DOS=HIGH...) ...? FreeDOS textmode installer still uses CATS. I could really use a smaller installer.. The texmode installer is quite old, and I cannot obtain the exact version of it (3.7.x), and newer versions should also exists (3.9, 4.0) somewhere in Jeremy's archives. And did Arkady re-add the seemingly but not actually unneeded BPB/... initialization at boot time which he had removed at some point? why 'not unneeded' ? Bernd --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] broken FreeDOS kernel.
Jeremy, the -dev kernel is BROKEN. Try booting, and then SET FOO=BAR I get 'environment full?' messages. previous kernel was from December 3rd, 2004 putting that version back eliminates the problem. btw: happy new year and best wishes, everybody! see you all in 2005 :) Bernd --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] question about the kernel with
Jeffrey Chao schreef: After booting into Windows, I can see there are two floppy drives in Windows Explorer, but I just have one floppy drive connected. Does anyone ever faced the same issue as me? A: is the emulated floppy drive (the floppy image and/or diskette you provided for bootable cdrom), B: is your real floppy drive. I haven't experienced this issue, as I use non-emulation booting using Isolinux cdrom bootloader. You: BIOS - cdrom - bootdisk.img - C: - Windows - 2 floppy drives Me: BIOS - cdrom - isolinux - C: - Windows - 1 floppy drive BIOS - cdrom - isolinux - Memdisk - bootdisk.img So, I select either floppy booting or harddisk booting, and not first floppy booting and then harddisk booting. Win98 cdrom may have the same issue: BIOS - cdrom - win98.img - io.sys - jo.sys - C: - Windows - 2 floppy drive Bernd --- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] bug! (unstable) MKDIR uses date 1980
Can somebody please fix the date for directory creation? Bugzilla? this is the unstable kernel, I used Lucho's latest binary. I'll compile my own binary soon enough. (if you're wondering: Freecom 0.82plAK-XMS, DIR C:\FDOS /OGN /Y) problem is not in kernel 2035 Bernd Volume in drive C is C_FREEDOS9 Volume Serial Number is 4020-19E3 Directory of C:\FDOS .DIR 00-00-1980 12:00a .. DIR 00-00-1980 12:00a APPINFO DIR 00-00-1980 12:00a BIN DIR 00-00-1980 12:00a CPI DIR 00-00-1980 12:00a DOC DIR 00-00-1980 12:00a HELP DIR 00-00-1980 12:00a INSTBASE DIR 00-00-1980 12:00a NLS DIR 00-00-1980 12:00a TEMP DIR 00-00-1980 12:00a CONFIG SYS11,197 01-24-2004 3:44a COPYING 18,353 08-15-2002 11:59p LOCALIZE EN 1,623 09-17-2004 7:05p POSTINST BAT 6,152 09-17-2004 3:56p 4 file(s) 37,325 bytes 10 dir(s) 1,015 Mega bytes free --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: test bootdisk
Arkady V.Belousov wrote: BB Bart, do you see the unnamed program, eating 48KB (probably just a BB viewing problem)? BB CTMOUSE 3,328(3K) 0(0K) 3,328(3K) BB 48,704 (48K) 0(0K) 48,704 (48K) BB Free 623,024 (608K)622,880 (608K)144(0K) Bernd, may you try: (1) MEM 1.6, (2) my MEM and (3) review complete lisintg (/F for Bart's MEM, /A in my)? I'll do that. Problem probably is in KEYB not loading completely successfull. Bernd --- This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder. More prizes in the weekly Lunch Hour Challenge. Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: test bootdisk
alright, MEM display is a MEM bug as Bart indicated, Lucho fixed, as final public developers's work for his part, the 'remainig' - 'remaining' cosmetic bug. now only this strange bug of why DISPLAY loads high if MEM is first run, and loads low (and atapicdd/cdrcache load high instead) if MEM isn't run. Keyb seems alright afterall, but I thought 1) 'keyb partially loading -- unnamed block eating UMB' 2) 'keyb loaded with valid parameters' -- MEM /C shows alright. My conclusion then: must be KEYB. Conclusion now: must be MEM displaying something wrong (as Bart indicates). no idea if the DISPLAY binary has been UPX'd, and if that has any affect. Bart, I'm not distributing a 386/BorlandC/Apack kernel, this was just an experimental bootdisk image to show some troubles I experienced. bootdisk will be 8086+, and I hope the SHSUCDX/SHSUCDHD parts can also become 8086+ in no way is this a full-featured usable bootdisk, but it does show how to load the various drivers. I'm still confused by syntax for DISPLAY/MODE/KEYB.., so it's good to have working examples at hand. I'm planning to use a 8086/Openwatcom/UPX version of either Jeremy's or Lucho's sources, and to distribute a 2035A (the conservative tree) as kernel for harddisk. Haven't figured out why not everything (except UDMA ofcourse due to lack of VDS) loads high. Plenty of UMB space (48K). perhaps I should test against official 2035, to see if self-UMB-loading programs work there. All my testing is done in VMware 4.5.2, btw. No Bochs/Qemu/DosEMU/VirtualPC etc. Bernd --- This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder. More prizes in the weekly Lunch Hour Challenge. Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] Re: test bootdisk
Bernd Blaauw wrote:
Hello all,
I've put online a new bootdisk with which I, and you, can easily
experiment. Download it from:
http://fdos.org/ripcord/beta9-final/test/testing.zip [274KB, 1.44MB
unzipped]
OK, just uploaded a new version, now includes fixed autoexec.bat and
mounting. program for small ISO file.
http://fdos.org/ripcord/beta9-final/test/testing.zip
Bart, do you see the unnamed program, eating 48KB (probably just a
viewing problem)?
(forgive me if you received this mail 3 times, but it probably is a
problem in MEM 1.7 and I'm not sure if you have the time to follow most
of list-only traffic)
Bernd
Modules using memory below 1 MB:
Name Total Conventional Upper Memory
SYSTEM 15,104 (15K) 9,984 (10K) 5,120(5K)
HIMEM2,480(2K) 2,480(2K) 0(0K)
EMM386 2,624(3K) 2,624(3K) 0(0K)
COMMAND 3,984(4K) 2,944(3K) 1,040(1K)
DISPLAY 11,648 (11K) 11,648 (11K) 0(0K)
UDMA 624(1K)624(1K) 0(0K)
ATAPICDD 4,848(5K) 0(0K) 4,848(5K)
CDRCACHE 6,160(6K) 0(0K) 6,160(6K)
SHSUCDHD 3,216(3K) 0(0K) 3,216(3K)
SHSUCDX 9,360(9K) 0(0K) 9,360(9K)
CTMOUSE 3,328(3K) 0(0K) 3,328(3K)
48,704 (48K) 0(0K) 48,704 (48K)
Free 623,024 (608K)622,880 (608K)144(0K)
---
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] The justice finally caught the criminal!
Luchezar Georgiev schreef: Lucho, whatever you do. Please leave that copyright message in. You made a proposal to change it. Then just removed it. Which is worse. The justice finally caught the criminal! I didn't remove it, I had just *moved* it to AUTOEXEC.BAT where it can be enjoyed in its full glory for as long as you wish instead of only for 3 seconds, and I announced that in my COUNTRY.SYS announcement, stating that I anticipate a stormy reaction to that. And here it is! OK, I added it back to main.c but the kernel became 40 KB. So I must find a way to optimise it further. When I do this (hopefully tomorrow), I'll upload the new files. How much space does the bootsector have? Loading FreeDOS kernel (licensed under GPL) bootsector: mentioning kernel + GPL kernel: commented out full notice (so does not get compiled in, but in sources) autoexec.bat: optional file, contains full notice as you currently have kernel should contain the GPL-message, but I don't think there's any need that it shows the GPL-message while being loaded. Bootsector can do that, IF there's enough space in it. Full (c) P Villani 19xx-20xx, licensed under GPL, see license for usage and distribution terms can be in the optional autoexec.bat file Bernd --- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Announce: COUNTRY.SYS
Lucho, impressive progress. Though I don't use any COUNTRY/codepage/keyboard_layout things myself, this can be quite usefull. I can imagine Aitor being happy, for example. He does a lot with these things. Now only NLSFUNC is missing (in progress by Eduardo Casino)? btw, no source for your country.sys provided (or did I not look good enough?) Bernd --- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] ludivmul.inc
Bart Oldeman schreef: I'm sorry but I simply don't have the time to go through all the other patches. If they were reduced to just bug fixes I'll promise that I'll have another look though -- I still monitor the mailing list every now and then. Guys *any* project that wants to be close to a 1.0 release must be in deep freeze, a stabilation, that means that we should really freeze the mainline kernel for anything but bug fixes. No optimizations, no reformatting, no new fancy macros, no nothing but bug fixes with the minimal amount of lines changed. Of course feel free to have your own branch, but I don't think it's in the interest of the project to use that for a 1.0. So I can make a deal, you isolate your bug fixes and I'll return and be friendly, or you don't and I'll simply disappear. It's that easy. Hi Bart!, thanks for showing up a brief moment. Arkady is doing a nice job, but I think you kernel developers should give him some more time to work out his changes. At a given moment, he should probably issue a code-freeze and then make stuff more readable/review-able Anyway, Lucho is reviewing Arkady's code, Tom started a private (more or less personal) branch, and Jeremy, I think, was both creating a 2035a (2035 + very conservative patches) and a development branch (Arkady's code into CVS). perhaps the utter-most conservative and really required patches (bugfixes) should be provided for review before going into 2035a. Meanwhile Arkady's version might become 2036 in a later stadium? all IMHO, ofcourse. It's the kernel (co)developers' opinions which should count for you, not mine :) are you planning on improving MEM again in the near future? I *still* (sigh!) postponed releasing a new FreeDOS distro..blame it on the holidays Bernd --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] ludivmul.inc
Arkady V.Belousov schreef: Hi! 19--2004 16:08 [EMAIL PROTECTED] (Bernd Blaauw) wrote to [EMAIL PROTECTED]: BB to work out his changes. At a given moment, he should probably issue a BB code-freeze and then make stuff more readable/review-able May you point, what in my code isn't readable (or, at least, less readable, than in original code)? :( replace readable by understandable for inexperienced C programmers the point is, the code should be as understandable as possible to as much people as possible, so everyone potentially can review the code, and contribute new code. I can't truely judge how understandable source code is. But, for example, I can see if I understand something like algorythms/code in config.c I'll have a look at FreeDOS again one of these days - I'm playing too much games anyway instead of releasing a new FreeDOS.. Bernd --- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel sources
Arkady V.Belousov schreef: PPS: About discussion of planned changes: how many times I wrote here? How many times I get any answer? If I will wait answers for my proposals before doing something, I will do nothing forever. :( PPPS: Of course, I open for discussion anyway. 1) implement your code 2) bugfix your code 3) make code understandable 4) upload up-to-date sourcecode to website 5) write to mailinglist about your changes, and point people to your sourcecode this way there is a discussion possible, as people can look into your code changes. You write the code, and then people ask you questions about your design decisions, and you defend your code changes. That's called discussion. Finally, people will approve your changes, and that makes your changes official, I guess :) be prepared to defend yourself against Tom's and Lucho's comments. I believe it's called peer review. I'm not one of those peers, the people who work(ed) on the kernel are. Bernd --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel progress
tom ehlert schreef: Hello Arkady, where the hell are the sources for these changes ?? I wonder, too. CVS read/download access is nice. Is it possible to fork the CVS kernel tree into an Arkady branch so he can work on the kernel and at same time provide sources (he doesn't have a website, and Lucho only offers a compiled binary as a service on top of his ROM-DISK program)??? You or Jeremy probably have the ability to do so. A nice requirement then might be that Arkady has to keep CVS up to date *before* sending any mail to the kernel/devel list about his progress. and just like Bart did, a daily .tgz can be offered. Download kernel sources: [released kernel] [official branch] [Arkady's experimental branch] No idea what the clear screen with white on black is. In what way a Win95 GUI behaviour? Logo on top of programs, hiding loading them? or the F8-menu ? so far for my non-programmer input.. Bernd --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] PATCH: config.c
Eduardo Casino schreef: Hi! Country code for Spain is 34, not 33. Eduardo. fixed in Arkady's version, and please check your clock - it's 23:15 here and your message is dated 30-06-2004 00:21 or so. one hour too much. thanks for the patch though :) Bernd --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel progress
Alain schreef: In my opinion this would be a _great_ improvement :) Many times I had ro reboot (in MS-DOS) because the critical instruction was executed ok and I didn't want to singlestep all the rest. BUT, IMHO the key for that should not be Esc but something completely different, like some other function key. yes, agree. I had a small discussion with Tom a year ago or so. It turned out that Win9x's DOS (7.x0) interprets the keys in a different way compared to older MSDOS. Y = confirm N = not confirm ENTER=confirm ESC = No (MSDOS7), YES (FreeDOS, older MSDOS). so a don't ask any other items unless explicitly mentioned in config.sys option/key would have to use something other than ESC. How about the space bar :) ? ..or even..F5 this causes only the commands explicitly using the sequence '?' followed by '=' to be asked: echo?=test (and ?echo=test , but not !echo?=test) Alain Bernd --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel progress
tom ehlert schreef: - when tracing, Esc now turns off asks for following lines with ? and assumes Y for all; F8 now behaves similar to Esc. I disagree. Esc turns of F8 'single stepping', nothing else. so if pressed ESC, then everything except a command?=value is auto-executed? Arkady, define similar (similar behaviour) please. You mean identical ? AFAIK, the only reason for INSTALL= to exist is, that programs will be INSTALL'ed without environment, and save a few unnecessary environments, else you could load it through autoexec.bat as well. You guys are the experts here. But Lucho showed the use of INSTALL= (and SET) commands, when using his ROMDSK (space is *very* precious there, thus no autoexec.bat). --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] config.c: progress
Arkady V.Belousov wrote: Hi! Arkady, I'll try to compile your kernel tonight, as I experienced some hardware upgrade glitches the last 2 days. as someone asked (I lost about 35 emails) : Lucho's site is at: http://linux.tu-varna.acad.bg/~lig/ it contains the Romdsk stuff and the UDMA DOS-driver. Bernd --- This SF.Net email sponsored by Black Hat Briefings Training. Attend Black Hat Briefings Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] [patch] #1758 - fix incorrect AskSingleLine function
Arkady V.Belousov schreef: - 123? present and statement not from selected menu? Skip. - ! present? Don't skip. - ? present or single step? Ask. Your proposal changes behavior: now it will look so: - 123? present and statement not from selected menu? Skip. - ? present? Ask. - single step and not ! present? Ask. I wanted 0123?!ECHO?=DUMMY.SYS also to be asked (because it contains ?= part) in current FreeDOS kernel, the ?= part is ignored because ! is present. cases 4 and 8 go wrong here (auto-executed..) echo=1// only ask when F8 echo?=2 // always ask !echo=3 // should never ask !echo?=4 // should always ask, even if F8 012?echo=5// only ask when F8 (and ofcourse menu 1, 2,or 3 selected) 012?echo?=6 // always ask 012?!echo=7 // never ask 012?!echo?=8 // should always ask, even if F8 ANY ?= should raise the ASK-question, even if ! is present. Eric optimized the function a bit :) Well... I hardly rework config.c and fix many bugs (most of them are not check input validness - for example, break=offk accepted as on). Also I add above your changes. If you wish/can/may, I send you my config.c for testing. I'll gladly receive your config.c please send entire file, not a patch. (I haven't learned using DIFF/PATCH yet, but learned compiling a bit) Bernd --- This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] [patch] #1758 - fix incorrect AskSingleLine function
Eric and I have been working a few hours on a patch to correct the
ask-user-to-execute-config.sys-line algorythm.
essentially (config.c, line 806 I think):
/* !device= never ask / device?= always ask / device= ask if singleStep */
/* ! does override singleStep but not ?, so !device?= will ask... */
if (! ( (singleStep !DontAskThisSingleCommand) ||
(askThisSingleCommand) ) )
return FALSE; /* do not skip, and do not ask either */
Eric also made some more changes. See below for the complete DIFF against 2035
Next steps *I* would like to take (still a non-programmer!) are:
-don't auto-add 0 as a menu-item
-set menudefault to lowest menu-item ('0' currently)
-don't show menu unless at least 2 different menu-items are available.
Bernd
http://www.coli.uni-sb.de/~eric/dos-config-patch.zip
--- config.old Tue May 25 01:02:46 2004
+++ config.cSun Jun 13 00:23:56 2004
@@ -549,7 +549,7 @@
umb_base_seg = umb_max = umb_start = umb_seg;
UMB_top = umb_size;
-/* there can be more UMB's !
+/* there can be more UMBs !
this happens, if memory mapped devces are in between
like UMB memory c800..c8ff, d8ff..efff with device at d000..d7ff
However some of the xxxHIGH commands still only work with
@@ -801,14 +801,15 @@
/* 123?device=EMM386.EXE NOEMS */
if ( MenuLine != 0
(MenuLine (1 MenuSelected)) == 0)
-return TRUE;
-
- if (DontAskThisSingleCommand) /* !files=30 */
-return FALSE;
+return TRUE; /* skip the line */
- if (!askThisSingleCommand !singleStep)
-return FALSE;
+ /* !device= never ask / device?= always ask / device= ask if singleStep */
+ /* ! does override singleStep but not ?, so !device?= will ask... */
+ if (! ( (singleStep !DontAskThisSingleCommand) ||
+ (askThisSingleCommand) ) )
+return FALSE; /* do not skip, and do not ask either */
+ /* if ( (s.s. d.a.t.s.c) || (a.t.s.c) ) then ASK THE USER */
printf(%s[Y,N]?, pLine);
for (;;)
@@ -902,6 +903,7 @@
/* Get the argument */
if (GetNumArg(pLine, nBuffers))
Config.cfgBuffers = nBuffers;
+ /* Second argument (0..8 buffers for read-ahead) not supported yet. */
}
/**
@@ -1004,7 +1006,10 @@
}
/*
-UmbState of confidence, 1 is sure, 2 maybe, 4 unknown and 0 no way.
+UmbState of confidence, 1 is sure, 2 maybe, 0 no way.
+Transitions: 0 - 0/2 depending on DOS=UMB, try init (2 - 1)
+after each driver load, as it could have been the UMB driver.
+If UMB really found, state 1 is reached and MCBs are adjusted.
*/
STATIC VOID Dosmem(BYTE * pLine)
@@ -1205,7 +1210,7 @@
#endif
if (!LoadCountryInfoHardCoded(filename, ctryCode, codePage))
-return;
+return; /* error message already displayed by LoadCountry... */
error:
CfgFailure(pLine);
@@ -1293,17 +1298,24 @@
STATIC VOID DeviceHigh(BYTE * pLine)
{
- if (UmbState == 1)
+ if (UmbState == 1) /* UMB already initialized? */
{
if (LoadDevice(pLine, MK_FP(umb_start + UMB_top, 0), TRUE) == DE_NOMEM)
{
- printf(Not enough free memory in UMB's: loading low\n);
+ printf(Not enough free memory in UMBs: loading low\n);
LoadDevice(pLine, lpTop, FALSE);
}
}
else
{
-printf(UMB's unavailable!\n);
+if (!umb_base_seg) /* only warn once */
+{
+ printf(UMBs unavailable!\n);
+ umb_base_seg = 0x; /* first 0, non-0 after umb_init success */
+}
+/* if UmbState is 2: still waiting for the UMB driver, after it is */
+/* found, UmbState will be 1 and umb_base_seg will be initialized. */
+/* UmbState 0 means that we do not want UMBs at all, DOS=NOUMB case. */
LoadDevice(pLine, lpTop, FALSE);
}
}
---
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: LBACache test results
The Somertons schreef: Justin If I recall correctly, Interlnk never had FAT32 support, so I hope C: isn't FAT32. as alternative to FD(X)XMS, we now use HIMEM.EXE , included in the EMM386 package. ftp://ftp.devoresoftware.com/downloads/himem64.zip [22-04-2004] is probably most recent. Bernd --- This SF.Net email is sponsored by the new InstallShield X. From Windows to Linux, servers to mobile, InstallShield X is the one installation-authoring solution that does it all. Learn more and evaluate today! http://www.installshield.com/Dev2Dev/0504 ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] Re: [Freedos-devel] Re: [Freedos-cvs] kernel/kernel fattab.c,1.30,1.31 fatfs.c,1.66,1.67
Bart Oldeman wrote: On Sun, 9 May 2004, James Tabor wrote: Hi Bart! Bart Oldeman wrote: Bart seems to be the only one with CVS access. So, if no time, the CVS snapshots stay identical (because of no imports to CVS), and people can start creating their own patches against this CVS-release? in stead of optimizing, is anyone of the kernel mailing list willing to review patches? I only can write pseudo code due to almost no knowledge of C, let alone DOS internals. However I did find a number of (trivial) bugs and as Bart has no time, I can try to correct a bug and let someone review it. Then, after reviewing + correcting, a patch collection like Lucho had could be prepared. only essential thing, IMHO, is that CVS contents should not change. MEM is Bart's tool, but it seems the changes are not so hard to make, in particular the 1.0 Todo-list options. perhaps *even I* can provide a patch for some issues. let's see if I can get some C experience. so for now: no optimisations, no new features, just bug fixing patches. is Lucho still (silently?) active? Bernd --- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel problems and problem loading high DISPLAY
DOS=UMB is causing a lot of problems. Unfortunately it's not possible to use UMBPCI (want to exclude EMM386 as a cause..) on Bochs. Bernd set path=a:\freedos LASTDRIVE=Z BUFFERS=20 FILES=40 DOS=HIGH DOS?=UMB ;DUMMY?=YES set dircmd=/ogn DEVICE=A:\DRIVER\HIMEM.EXE /VERBOSE DEVICE=A:\DRIVER\EMM386.EXE NOEMS I=C800-CFFF X=D000-EFFF /VERBOSE SHELL=A:\command.com A:\ /P:A:\autoexec.bat --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel problems and problem loading high DISPLAY
hi Bart, Bochs has no PCI, so UMBPCI does not work. any comments on the original message I posted? do you want me to publish a Bochs zipfile including my FreeDOS configuration, so anyone can reproduce my encountered problems? unlike VMware, Bochs is completely platform-independent and thus won't be influenced by host processor type and speed for example. my problems happen when DOS?=UMB is answered with Y (YES). I don't think it's EMM386 making problems, but the FreeDOS kernel. Bernd --- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149alloc_id=8166op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] Re: [Freedos-devel] Recent Bugzilla entries
I'm kicking this back to kernel. No need to let it stay on devel-list Arkady V.Belousov schreef: Hi! 19--2004 15:13 [EMAIL PROTECTED] (Eric Auer) wrote to [EMAIL PROTECTED]: EA In bug 1759, he also suggests that No UMBs available warning (when you EA use DEVICEHIGH) should be only displayed once - fixed in 2034? On the other side, this once warning may be missed - for example, because next driver quickly scrolls screen or clears it. a one time warning plus a 2second delay would be my choice. in current case I get LOTS of warnings about no UMBs available. MSDOS is silent. (and LH also does not warn, so why would DEVICEHIGH?) DEVICEHIGH=HIMEM.EXE DEVICEHIGH=EMM386.EXE DEVICEHIGH=ATAPICDD.SYS /D:FDCD0001 DEVICEHIGH=NANSI.SYS MEM /C now also works to show this. On the other side, I agreed - missing UMB may be easily detected later, by amount of available memory, whereas config.sys may be common for different configurations. So, this warning, at may taste, is completely useless. yes, Erwin Veermans on his NWDSK has to use different DEVICE and DEVICEHIGH lines for the same driver, just because of this warning. Arkady, is the auto-loadhigh part of Cutemouse difficult to integrate into other programs? I'm thinking about FreeCOM and KEYB. not DISPLAY, as that will become a driver file anyway. FreeCOM can be loaded high using SHELLHIGH, but this SHELLHIGH is strangely enough unknown on MSDOS 7.10. then use /LOW to keep FreeCOM loaded low. SHSUCDX 2.1a also has an auto-loadhigh function. anyone tried DOS=LOW,UMB and see if anything gets loaded high? in my experience it does not enable UMBs. Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] 2034rc feedback (and EMM386)
Bernd Blaauw schreef: EMM386: FDISK /REBOOT causes Invalid Opcode, FDAPM WARMBOOT does the same FDAPM COLDBOOT does reset the computer FDAPM HOTBOOT works like good old QEMM: reboot to bootsequence immediately. (not that it has that great effect, but OK..) anything that can be done about it? don't know if the mentioned applications need to change, or EMM386, to accept warmboots. I'll check against MS EMM386. Bernd just checked against MS emm386.exe : this is an FreeDOS EMM386 flaw I'm not using EMM386 on bootdisk, but a fix in EMM386 would be nice (but not essential) to allow warmboot Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2034rc for testing
Arkady V.Belousov schreef: Fine. For the future: show URL for complete diff patch on the main page, previous time I don't found it (if it was present). Also, when planned 2034 release? May be I wait this release and download it completely (instead patch), if it will be soon? the idea is to test *before* spreading to the general public. I include this 2034 kernel in the next FreeDOS distribution, next Sunday. there have been a few times where a kernel was released, and a few days later a new kernel followed it because a larger public found a few bugs. So, by all means, if you want to test it, download it. If not, wait until the final release and then the next cycle of improvements can be made. I think the largest test population in the wild would be if Erwin Veermans included the testing kernel on his Nwdsk (Netware bootdisk). do we even have testing procedures? or would testing specific things first require a kernel changelog (history.txt)? Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] handle 4 defaulting to PRN???
Erwin Veermans schreef: Forbidden You don't have permission to access /~lig/romdsk/romd-bin.rar on this server. What am I doing wrong, or should I send some cigars first ? ;-) confirmed. do you compile from source or always work with binaries like I did? latest binary from Jeremy took a while so in a few spare hours on a Sunday afternoon I decided to finally learn how to compile. Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patch: batch and make files
Arkady V.Belousov schreef: Hi! 4--2004 17:55 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov [EMAIL PROTECTED]: AVB I test batch and make files both under OW12 and BC31 te would be great if you ewoild ewoild=perform? would - 'if you would test them' te test them with TV 2.01 also (this is a reference compiler, BC31 not) How big is it? Where I may download it (without answering question and other scripting issues)? If it longer than 3M (www4mail limit), who may send it to me? te btw: there is absolutely no need to mess with them - they usually work. they=BC? It depends. :) 'they' = '(your changed) batchfiles' --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
[Freedos-kernel] devicehigh semi-patch
each DEVICEHIGH in config.c causes a warning
[ http://www.freedos.org/bugs/bugzilla/show_bug.cgi?id=1759 ]
is the document for getting Openwatcom packages (in order to compile the kernel) still correct
(except OpenWatcom 1.0 - 1.2 then)?
http://www.freedos.org/freedos/news/newsitem/137.txt
idea (excuse my lack of C knowledge):
static bool umbwarn=true; // somewhere in the start of config.c
and then check at DEVICEHIGH (line 1311):
STATIC VOID DeviceHigh(BYTE * pLine)
{
if(umbwarn) // true unless warning already given.
{
if (UmbState == 1)
{
if (LoadDevice(pLine, MK_FP(umb_start + UMB_top, 0), TRUE) == DE_NOMEM)
{
printf(Not enough free memory in UMB's: loading low\n);
}
}
else
{
printf(UMB's unavailable!\n);
}
umbwarn=false; // only warn user once about lack of UMBs, not for each DEVICEHIGH
}
LoadDevice(pLine, lpTop, FALSE);
}
Bernd
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] new conv mem highs.
The current nightly-kernel may have reached a new landmark in the quest for smaller conventinal-memory footprint but it lost ground in usability and compatibility. My test-machines halt on various arbitrary points telling me: more than two near fnodes requested at the same time if files=10 would work for you, then there are 10 of those f-nodes. maybe that's the minimum that should be kept in conventional memory? move all i-nodes except (the first?/lowest?) 10 into HMA don't know if this is possible. Bart is the expert here. Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] nevermind..
reason is speedup. It's faster to read a single 360KB file into RAM and then run from there, than to keep reading a diskette. guess you had the bootdisk from prerelease 4, or the one below: http://fdos.org/ripcord/beta9rc5/fdos1440.img the real floppy contents is accessible as B: are you the same Wørm who had a bootdisk site? it disappeared quite a while ago. Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] freedos boot problems / about me
it's the CDRcache driver which causes the cdrom disk resets, not SHSUCDX itself. option 2 should prevent it from loading, as no XMS driver is loaded. Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
