Re: [Freedos-user] PRINT command
Thanks Alain! I've downloaded it and will give it a try! Alain M. wrote: I was used to printq because it was far better then print, you should give it a try. I found it at ibiblio (in Freedos, he he...) http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/dos/print/ Alain Chris Ruhl escreveu: I will certainly give the NEWDOS a whirl when I can. I've downloaded it, just need to get time to play! I will, no doubt, enjoy comparing the ms print with freedos print!! You guys are great at fixing things up right and I seem to have the perfect difficult hardware and applications for testing it! Eric Auer wrote: Hi Chris, I agree that MS PRINT is no long term option. Did you also try the shareware NEWDOS PRINT? Newdos is a German shareware collection of replacements for MS DOS commands, trying to be both user friendly and modern. See: www.newdos.de Another useful point in running MS PRINT in FreeDOS is that you can compare various settings and can compare how the various PRINTs behave. Maybe we can just fix some internal settings in FreeDOS PRINT or PRINTQ to get you going :-). Eric - 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user - 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] 1.0 CD install hang
FreeDOS 1.0 CD Page says; Wattcp.cfg Setup Menu It hangs at: Configuring through DHCP... I would skip this section if I knew how. Ideas? Ray - 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] 1.0 CD install hang
Ray Davison wrote: FreeDOS 1.0 CD Also, the make boot floppy item, didn't. It just took a readable disk and made it unreadable. The disk was in A:, and it complained that it couldn't read old info off B: Ray - 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] A faster SYS, a Watcom problem, and a new Borland problem
Hi all, I have been busy with bug 1840: www.freedos.org/bugzilla/cgi-bin/show_bug.cgi?id=1840 sys a: b: requires numerous disk swaps with single floppy system SYS 3.2 needed at least 15 disk changes to copy kernel and shell and write a boot sector if you had a system with only one diskette drive and were SYSing with 1 diskette as source and another as target (DJ system). This new experimental SYS 3.3 solves the problem by first reading both files from the source into RAM, then writing the boot sector, and then writing both files to the target :-). The updated SYS can be downloaded from the bugzilla page :-) So far for the freedos-user part. Now the freedos-devel problem: I could not figure out how to make a working far or DOS malloc to allocate memory blocks of more than 64 kB size from the far heap or from DOS (remember: SYS is a com file and must use tiny model) in the OpenWatcom case. I could only compile a working file with Turbo C 2.01 ... Could somebody have a look and fix this problem? The updated sources can be updated from the bugzilla page :-) Another problem: I cannot compile the KERNEL any more with Turbo C 2.01, I get this error message: Undefined symbol '_HaltCpuWhileIdle' in module dosidle.asm Could somebody tell me how to update the sources to make compiling work with BOTH Watcom and Borland compilers again? Thanks :-). If possible, please do also explain how to compile a FAT32 kernel with Borland again: It seems that something in linking or compression changed recently, and now I get a TGROUP is 64 kB style error with FAT32, but only with Turbo C. Either Watcom has a smaller TGROUP or it has some automatic decision for 64 kB / not 64 kB...? Happy testing and thanks in advance for your feedback and for giving me a clue about the Watcom and Turbo C problems... :-) Eric - 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
[Freedos-user] 4dos bug
Hi. Seems I have found a bug in 4DOS 7,57. Function [EMAIL PROTECTED],c,4] will return 1980-00-00. So, if you want true date, then use m instead c in second argument. Version 4DOS 7.54 are free from this bug. @FILEDATE[filename[,[acw][,n]]]: Returns the date a file was last modified, in the default country format (mm-dd-yy for the US). The optional second argument selects which date field is returned for files on an LFN drive: a means the last access date, c means the creation date, and w means the last modification (write) date, which is the default. @FILEDATE also takes an optional third argument for the date format: 0 - System default format 1 - U.S. format (mm-dd-yy) 2 - European format (dd-mm-yy) 3 - Japanese format (yy-mm-dd) 4 - ISO 8601 international format (-mm-dd) -- ice 0x696365*gmail,com - 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] 1.0 CD install hang
Hi Ray, FreeDOS 1.0 CD Wattcp.cfg Setup Menu It hangs at: Configuring through DHCP... This happens because you selected a package which tries to use the internet to download further files. It is a bit silly that the installer does not warn you about that. See: http://fd-doc.sourceforge.net/wiki/index.php?n=FdDocEn.FdInstall You can find a list of internet-using packages here: http://fd-doc.sourceforge.net/wiki/index.php?n=FdDocEn.FdDependencies From the dependencies page: The following packages need internet connection DURING INSTALL, cdrtool only indirectly because it recommends ASPI install: * fprot wattcp (fprot antivirus UTIL, big download) * aspi wget (aspi DRIVER) * scsi wget (scsi DRIVER) * usbdos wget (usb DRIVER, device detection can be very slow) * via wget (via sound DRIVER) Those only RECOMMEND packages which require internet during install: * cdrtool cwsdpmi (cdrecord and related MEDIA tools) * cdrtool dfl zisofs aspi * dfl cdrtool (file linker UTIL for cdrecord) The following packages are internet related, but Lynx, Arachne, HXRT and Lnxsmal are also useful without internet: * crynwr (the network packet DRIVER(s), card detection can be slow) * wget wattcp * fdstpop wattcp * bsflite cwsdpmi wattcp * lnxsmal lynx lynxexx * lynx cwsdpmi wattcp gnufile * lynx mouskey lynxex lnxsmal * openxp cwsdpmi wattcp tar gzip * vnc wattcp * hxrt wattcp * wattcp cwsdpmi crynwr (network, detection can be slow) * arachne cwsdpmi crynwr Various other dependencies - note that OWATCOM is very big: * xharbor owatcom ... * fdpkg infozip or 7zip, and command or 4dos * opengem ctmouse choice infozip fdapm ... If you want a smaller but almost complete install, avoid: OpenWatcom C/C++ (owatcom), XHarbour (xharbor), kraptor, doom, vi (vimrt/vim16/vim32), maybe FreePascal (fpascal) Then you might even manage to install on less than 100 MB ;-) Eric - 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-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
