Re: [Freedos-user] PNG viewer
you can use this in conjunction ox HX extender (www.japheth.de) http://www.advsys.net/ken/util/kpic.exe Ken's PICture viewer. Supports: JPG,PNG,GIF,TGA,PCX,BMP. View all files in a directory or files inside a .ZIP. (no need to extract first!) Example: kpic /zduke3d_hrp.zip *.png *.jpg. Select any DirectX mode on the command line. Example: kpic /1024x768 *.* KPIC allows you to scroll and zoom quickly (hold mouse button). It supports a fancy 4x4 filter (uses MMX code) to interpolate samples cleanly when you use the zoom feature. This is a high quality filter - most 3D accelerators use bilinear interpolation which is only a 2x2 filter :) There are 3 interpolation modes; use TAB to select between them. (Mode 0:4x4 when stopped/nearest when moving, Mode 1:4x4 always, Mode 2:nearest always). (See PNGOUT.HTM for a more complete description of supported image formats) jasse...@itelefonica.com.br wrote: Robert Riebisch wrote: dos386 wrote: But there is a tool which has the name DISPLAY and There are simply too many DISPLAY's ... I mean the one from 1998 by ??? done with DGJPP closed source freeware ??? = Jih-Shin Ho This is available from any Simtel mirror /simtelnet/msdos/graphics directory. IMO this DISPLAY is an overkill if one needs just a PNG viewer, because it is an editor for a score of graphics file formats (including PNG), uses much memory and is very slow (45s just to load on my computer). I would recommend instead PICTVIEW, freeware available from www.pictview.com JAS -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- View this message in context: http://www.nabble.com/PNG-viewer-tp24027981p24029247.html Sent from the FreeDOS - User mailing list archive at Nabble.com. -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] USB Question
It must be supported by your BIOS. From cca 6 PC's I could test within last 2 years 1 tries but fails and the remaining 5 don't even try. So ... -- ~~~ wow ~~~ -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] PNG viewer
uses much memory and is very slow (45s just to load on my computer). DPMI host ??? Some faulty EMM386 ??? For me it isn't slow at all :-) ... I didn't test the memory requirements :-| -- ~~~ wow ~~~ -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] UIDE.SYS
would be useful as fallback to have at least SOME access to your non-BIOS disks Why not the fastest SATA AHCI DMA ? Apparently the problem is not inside UIDE ;-) Adding block-device support would take a LOT more code and isn't really necessary. There are two other schemes that can be used without changing UIDE -- I haven't asked for adding block-device to UIDE, just non-BIOS disks support, and I don't need it too __badly__ since I have none by now. -- ~~~ wow ~~~ -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] UIDE.SYS
Hi! would be useful as fallback to have at least SOME access to your non-BIOS disks Why not the fastest SATA AHCI DMA ? Apparently the problem is not inside UIDE ;-) If your motorbike fails, the fallback is not a plane. It is a bicycle. In other words, if for example a CF card only supports PIO, neither UDMA nor AHCI DMA will help you ;-). Adding block-device support would take a LOT more code A ramdisk is often a tiny driver. To give block device access to UIDE disks, you only need a partition table parser and a driver similar in size to a ramdisk. I would suggest that both is put in a driver for UIDE block devices which can be loaded separately from UIDE. Alternatively, UIDE could provide ASPI access to the found disks, then already existing drivers as ASPIDISK can be used for block device access :-). I haven't asked for adding block-device to UIDE, just non-BIOS disks support... Support means you access them somehow - just adding them to int 13 will not give them drive letters, only lowlevel access. Eric -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] A windows 9x replacement...
What are you talking about? ReactOS is not about Windows Me The request of M.R. (NO, I don't understand it well ... or at all) Yes, it seems you don't understand it, or at least not the same way I do. I don't see where he mentioned Windows Me at all. And Windows 3.x/9x is no DOS GUI from what point of view? They were sold as OS (what they aren't either) back then ... Yes, but everyone technically experienced could tell they weren't and aren't. (Windows 9x arguably tries more to work without DOS, but if it would have been a stand-alone operating system, why boot it from DOS? Because of the compatibility and to give customers a free MS-DOS with the new shiny Windows? You don't say.) Japheth writes on his site that HX's source code is about 100,000 lines of code When in doubt download it and recount :-D Sorry, my little (C) program to automatically count lines only works with NASM source code ;-) Regards, Christian -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] UIDE.SYS
Adding block-device support would take a LOT more code A ramdisk is often a tiny driver. To give block device access to UIDE disks, Okay.. you only need a partition table parser Yes, which would reside in the temporary (discarded) part of the driver. Of course that won't decrease it's size on disk. and a driver similar in size to a ramdisk. No. I haven't asked for adding block-device to UIDE, just non-BIOS disks support... Support means you access them somehow - just adding them to int 13 will not give them drive letters, only lowlevel access. Although it is *obvious* at this time, why not use Int2F.0801 (Add new block device [to the default DOS block device driver]) to add the drives after enabling the Int13 access? The only notice here is that some DOS versions use varying layouts (i.e. MS-DOS 7.10+ with FAT32 EBPBs, and I hope FreeDOS with FAT32 uses the same layout) so such a feature would have to be configured carefully for different versions and code is required to tell them apart. After all, that installation code (which leaves only the actual UPB (DDT) in memory) could easily be moved into another program. It could use a specific UIDE backdoor (or access UIDE's data, or do something else) to get to know which Int13 units are provided by UIDE exclusively; or a generic API could be written which could also process added Int13 drives provided by different drivers. Then the installation program would read from the provided unit to decide whether the first sector is the MBR, or a partition boot sector. It would parse the MBR (if any) and then add block devices for each DOS partition. Regards, Christian -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] A windows 9x replacement...
This is off-topic and irrelevant anyway ... -- ~~~ wow ~~~ -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] UIDE.SYS
If your motorbike fails, the fallback is not a plane. It is a bicycle. Or just your feet ... In other words, if for example a CF card only supports PIO, neither UDMA nor AHCI DMA will help you OK ... do the SATA PCI addon cards suport PIO also ? I see no arguments against supporting PIO also for non-BIOS disks, if the hardware supports it. The point was that the UDMA/ADMA support apparently could be added at very little cost ;-) Support means you access them somehow - just adding them to int 13 will not give them drive letters, only lowlevel access. I know ... maybe this problem could be somehow solved later outside of UIDE ;-) -- ~~~ wow ~~~ -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] UIDE.SYS
DOS386 wrote: I haven't asked for adding block-device to UIDE, just non-BIOS disks support, and I don't need it too _badly_ since I have none by now. Non-BIOS disk support for caching already exists in UIDE, in its external entry logic which can be conditionally- assembled into the driver. UIDE uses its first 48 cache unit numbers for diskettes and hard-disks, and the next 8 cache unit numbers for its CD/DVD drives, leaving 200 free cache unit numbers for other devices.Each such device can call UIDE for read/write access using a 48-bit logical block number (LBA), same as a system hard-disk. Each device also provides UIDE with a call-back routine pointer, which UIDE calls for actual I-O if the requested data is not in its cache. As noted before, CD/DVD units within UIDE actually use this external entry scheme, so I know it works fine and could serve other devices, too. Note that UIDE does not do actual I-O, the device's call back routine does. At present, UIDE has I-O logic only for SATA/IDE hard-disks, also SATA/IDE/PIO CD/DVD drives. Users of a non-BIOS device will have to provide their own call-back I-O logic for UIDE. I would consider adding other internal drivers to UIDE only for major classes of I-O devices, e.g. USB/Firewire, and only if somebody can provide me a firm and universally accepted spec for the devices. Otherwise, I prefer that an odd non-BIOS unit provides its own I-O logic and uses UIDE's external entry scheme, if caching by UIDE is desired. Also, Eric Auer wrote: ... To give block device access to UIDE disks, you only need a partition table parser and a driver similar in size to a ramdisk. I would suggest that both is put in a driver for UIDE block devices which can be loaded separately from UIDE. Alternatively, UIDE could provide ASPI access to the found disks, then already existing drivers as ASPIDISK can be used for block device access :-). Unless there is some intent by BIOS vendors to drop the Int 13h I-O method for disks/diskettes, accessing Int 13h devices using block I-O methods ought not be necessary. The Int 13h scheme, especially with its extended 48-bit block numbers, works perfectly well, and a driver such as Eric suggests would be surperfluous. Re: UIDE having ASPI support, I am not-interested. ASPI is a SCSI-like interface scheme, HUGE and overblown and has no business being in drivers intended to be SMALL, as UIDE is. SCSI has in effect been run out-of-business in the PC market by less-expensive IDE devices, so it is not the best use of my time to add ASPI handling in UIDE now. USB/Firewire perhaps, SCSI no. -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Thank you to kernel developers for new kernel 2038
I am also very glad for the new kernel. I am waiting for the 1.1 version impatiently. I have made a FreeDOS distro of my own. Philosoficaly it is an installer radicaly oposed to FreeDOS's. My intention was to get close to the original DOS installer, wich is... nothing :) ... I just added a very simple .bat menu for formating enc copying. This has been used by completly layman clients with great success I will release an english version soon after the 1.1 official comes out. Thanks all, Alain Mouette São Paulo, Brasil Marcos Favero Florence de Barros escreveu: Just want to add my own thanks for the new kernel. Marcos Regular FreeDOS user Sao Paulo, Brazil -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Getting sound to work in FreeDOS on Modern systems.
Well I finally found a ESS PCI card here: http://www.recycledgoods.com/item/32052.aspx Anyone have this card and if so have you already tested this on a modern motherboard without ISA slots? I planned on getting it but I want to check and see if someone tried this with FreeDOS and a modern motherboard, and in case it didn't work even if all the drivers have been loaded etc. I assume this unit isn't affected by the NMI requirement and DDMA judging by that other link earlier: http://www.it-he.org/sound.htm On Sat, Jun 13, 2009 at 9:30 AM, Eric Auer e.a...@jpberlin.de wrote: Hi Dos386, Intel ICH Pure AC97, does not attempt to support SB. Supported by few modern DOS apps as AC97, not supported by old games. ES1371/1373 AKA SB128PCI/SB16PCI, EMUxxx (SB512/LiveAudigy), ... (MPXPLAY) Supported by modern apps as AC97, comes with driver which creates virtual SB, apparently needs NMI and EMM386... will no longer allow SoundBlaster or similar clone cards to work correctly with Sound Blaster emulation. NO, but that wasn't a working solution anyway Actually DDMA / TDMA on PCI slots worked quite okay on my old K6-2 board which had PCI, ISA and AGP... At some time boards stopped with DDMA support and more recently, TDMA and/or NMI support stopped in nForce and Core2 etc boards. SB Live24 (ask Laaca, I don't use old games) See above - even that might fail on modern boards. Note that more full emulators such as DOSEMU (Linux) NOT a full emulator Correct. It only emulates the devices, not the CPU, which makes it much faster than a whole-PC emulator :-). BOCHS and QEMU do work in FreeDOS and can emulate SB16 ... I meant running them in Linux or Windows, but nevermind ;-) so the only lacking thing is the connection from HX WINMM DLL to PCI sound hardware ;-) Cute idea actually! Run Bochs/Qemu with DOS as host, using the Win32 support layer of HX, and then run ANOTHER DOS INSIDE Bochs/Qemu to have sound... Of course it will be slow as hell, but it CAN work :-) Emulated CPU of course wastes CPU time Much time, but a non-issue (or even desirable) for old games + new CPU ;-) I remember that DOSBOX was too slow for my taste on any normal single core CPU even though DOS games only need CPU speeds of 486 or Pentium I times... :-p Eric -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] USB Question
dos386 wrote: It must be supported by your BIOS. From cca 6 PC's I could test within last 2 years 1 tries but fails and the remaining 5 don't even try. So ... ... you did something wrong. From hundreds of PCs only a few failed here. Robert Riebisch -- BTTR Software http://www.bttr-software.de/ -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] A windows 9x replacement...
Michael Robinson schreef: There are many Windows programs that only work in dos based Windows. There is such a thing as a dos based Windows program, try to run it at the dos prompt ( any version ) and you'll get a this requires Microsoft Windows error. Many of these same programs either don't work or don't work correctly in Windows NT and other NT based versions of Windows. Isn't this exactly what HX Extender is for? to run win32 console programs Right now, one of the goals of the kernel developers is to support Windows 3.x better. Yep, let's see where kernel 2039 brings us sometime :) -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] which open source libraries work?
Just wondering what Open Source libraries in the graphics/multimedia/audio areas anyone's had any luck getting to build and work with on FreeDOS? I read programs with SDL library work in some cases with HX Extender. Am assuming SDL doesn't build on its own in djgpp or a similar C/C++ compiler for DOS. PDcurses works. Djgpp looks like it has an ncurses port (or maybe it's just using PDCurses in some form). Read something about WxUniversal (a port of WxWindows using MGL). Anyone been able to get it working or even find the sources for the proper version of MGL anymore? Saw something about Nano-X too, but it needs the MGL library as well. Also saw mention of miniGLX, GGI, DirectFB but no information on whether there are DOS ports. Anyone had any luck using one of these libraries or something like them? Any other cross-platform GUI or screen libraries that have a DOS port out there? Is there a good C/C++ audio library to use with programs? Was wondering if the code from the DOS version of Timidity could be plugged into the latest version or maybe someone knows of a better source for a sound API? Thanks. Sincerely, Laura http://www.distasis.com/cpp -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] A windows 9x replacement...
On Mon, Jun 15, 2009 at 5:00 PM, Bernd Blaauw bbla...@home.nl wrote: Michael Robinson schreef: There are many Windows programs that only work in dos based Windows. There is such a thing as a dos based Windows program, try to run it at the dos prompt ( any version ) and you'll get a this requires Microsoft Windows error. Many of these same programs either don't work or don't work correctly in Windows NT and other NT based versions of Windows. Isn't this exactly what HX Extender is for? to run win32 console programs Right now, one of the goals of the kernel developers is to support Windows 3.x better. Yep, let's see where kernel 2039 brings us sometime :) HX Extender is not a very good Win32 console runner, but it is better than nothing. In the future, this might be used as the basis of such a Win 3.x/9x replacement. Hopefully kernel 2039 does bring us good support for Windows 3.x... -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] UIDE.SYS
Eric Auer wrote: as your driver already has built-in caching, UIDE does not need to make int 13 device numbers for non-BIOS devices ... I assume you mean its ability to cache devices other than its own SATA/IDE devices, by using UIDE's external call routines, and I agree with you. A non-BIOS device needs its own I-O logic, which except for USB/Firewire I am not interested in adding into UIDE, and so I will dismiss the idea of UIDE making Int 13h device numbers.UIDE was meant to handle caching for already-existing devices, and not add its own devices. I still think that allowing PIO for harddisk in case UDMA fails would be nice, and maybe it could share most of the logic with CD/DVD PIO mode. I have heard of cases where my older drivers through 2006 caused FAILURES, if they tried setting UltraDMA to values other than what the BIOS set. That logic was deleted by me around 2006, and UIDE now takes whatever UltraDMA mode the BIOS sets for disk/CD/DVD units. I have NEVER heard proven cases where UDMA fails either due to a BIOS-made UltraDMA setting, or at run-time which would give MANY disk I-O errors! If this occurs, a disk or mainboard controller likely has died, likely a 3 year warranty disk, and a user needs to run diagnostics, then go buy NEW hardware! Cases where UDMA fails by itself as you describe are very rare! During init, note in UIDE.ASM after label I_MSNm: where it calls I_ValD and validates a disk as being UltraDMA. If NOT valid, an error message is displayed and the Non- UDMA disk count is incremented, meaning UIDE then calls the BIOS to handle I-O for that disk at run-time. Thus UIDE is already doing what you ask, since the BIOS likely will handle such a non-UDMA disk using PIO mode. The block device thing is a separate issue - I also agree. This is an item that should not be a part of UIDE, which is an I-O driver for already-existing hard disks of the Int 13h variety. Block devices require different drivers which really should be kept separate. -- 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
