Re: [Freedos-user] FreeDOS on USB stick?
Roughbert Strong wrote: > stick, booting starts OK but soon stops with "media What happens exactly? > test failure check cable". I've seen this error "Check cable" probably comes from your NIC (PXE), because BIOS couldn't boot the stick. Robert Riebisch -- BTTR Software http://www.bttr-software.de/ - 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] EDIT yes no hotkeys
Hello Eric,
you wrote:
> of if. Makes the code more readable and makes it easy to connect
IMHO Edit's code is a good candidate for winning on the IOCCC ;-)
> I guess you mean DN for next and UP for prev.
Yes, you're right.
>> I removed `static' keyword from {Next,Prev}Focus definitions and
>> declarations in the dialbox.c...
>
> Why?
Because of linker errors:
Error: Undefined symbol _PREVFOCUS in library file dflat.lib in module MSGBOX
Error: Undefined symbol _NEXTFOCUS in library file dflat.lib in module MSGBOX
> Interesting. Let me know if the suggestion above fixes the rest.
Your suggestions fixes only UP and DN keys. Left and Right arrows
are still does not work.
After placing prototypes for NextFocus and PrevFocus into msgbox.c, tcc says:
Warning msgbox.c 47: Suspicious pointer conversion in function YesNoBoxProc,
if I write NextFocus(wnd)..., and compiles w/o any warnings, if I write
NextFocus(wnd->extension). But in the last case only y / n keys works.
> it might be a bit tricky to avoid Cyrillic chars as CP866 has
> fewer line art chars, but still... If you notice other errors
CP866 differs from CP437 only in ranges 128..175, 224..239, and
(partially) 240..255. Line drawing chars located at the same places
in both CPs.
diff's output:
cut here
diff -ur C:\FDOS\SOURCE\EDIT\/dialbox.c ./dialbox.c
--- C:\FDOS\SOURCE\EDIT\/dialbox.c 2003-11-27 15:29:52.0 +
+++ ./dialbox.c 2007-08-09 14:29:28.0 +
@@ -6,8 +6,8 @@
static BOOL dbShortcutKeys(DBOX *, int);
static int ControlProc(WINDOW, MESSAGE, PARAM, PARAM);
static void FirstFocus(DBOX *db);
-static void NextFocus(DBOX *db);
-static void PrevFocus(DBOX *db);
+void NextFocus(DBOX *db);
+void PrevFocus(DBOX *db);
static CTLWINDOW *AssociatedControl(DBOX *, enum commands);
static BOOL SysMenuOpen;
@@ -775,7 +775,7 @@
}
/* change the focus to the next control --- */
-static void NextFocus(DBOX *db)
+void NextFocus(DBOX *db)
{
CTLWINDOW *ct = WindowControl(db, inFocus);
int looped = 0;
@@ -794,7 +794,7 @@
}
/* change the focus to the previous control --- */
-static void PrevFocus(DBOX *db)
+void PrevFocus(DBOX *db)
{
CTLWINDOW *ct = WindowControl(db, inFocus);
int looped = 0;
diff -ur C:\FDOS\SOURCE\EDIT\/msgbox.c ./msgbox.c
--- C:\FDOS\SOURCE\EDIT\/msgbox.c 2006-07-24 12:17:10.0 +
+++ ./msgbox.c 2007-08-09 14:34:38.0 +
@@ -6,6 +6,9 @@
extern DBOX InputBoxDB;
WINDOW CancelWnd;
+void NextFocus(DBOX *);
+void PrevFocus(DBOX *);
+
static int ReturnValue;
int MessageBoxProc(WINDOW wnd, MESSAGE msg, PARAM p1, PARAM p2)
@@ -35,11 +38,17 @@
ClearAttribute(wnd, CONTROLBOX);
break;
case KEYBOARD:{
-int c = tolower((int)p1);
-if (c == 'y')
+int c = (int)p1;
+if (c == 'y' || c == 'Y')
SendMessage(wnd, COMMAND, ID_OK, 0);
-else if (c == 'n')
+else if (c == 'n' || c == 'N')
SendMessage(wnd, COMMAND, ID_CANCEL, 0);
+else if (c == '\t')
+NextFocus(wnd);
+else if (c == RARROW || c == DN)
+NextFocus(wnd);
+else if (c == LARROW || c == UP)
+PrevFocus(wnd);
else {
beep();
return TRUE;
diff -ur C:\FDOS\SOURCE\EDIT\/watch.c ./watch.c
--- C:\FDOS\SOURCE\EDIT\/watch.c2003-11-17 19:33:22.0 +
+++ ./watch.c 2007-08-09 13:58:14.0 +
@@ -9,7 +9,7 @@
int rtn;
/* int i; */
static int tick = 0;
-static char *hands[] = { " L ", " - ", " ะบ ", " - " };
+static char *hands[] = { " \xc0 ", " \xda ", " \xbf ", " \xd9 " };
switch (msg)
{
case CREATE_WINDOW:
cut here
--
Oleg O. Chukaev
-
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] Install and dosfsck 211c
Hi, Eric Your 2.11c version is great! It's just what that utility needed to prevent confusion when using very large hard disks. I let 2.11b run overnight and it finished okay. The counter, at least, lets one know that it will take a l-o-n-g time to finish! Interesting twist on install routine: I downloaded the base ISO last night and tried it, plus my full cd, on the new computers that I have and it failed if I let installer finish. These PC's have proprietary ATX motherboards with PCI slots and one full-length ISA slot that I need for my serial expansion cards, Pentium 4, 3Ghz processor, 512Mb of RAM, one 80Gb SATA hard drive, Phoenix Award Bios. They are industrial computers assembled by a company in Canada -- Option Computers. The ISA card is used for my process control I/O I tried all three installation options on the full cd and the base install on the base cd. I let the installer run to the end and finish up but I got "illegal instruction" warnings with a load of addresses and opcodes when rebooting, the FreeDOS boot process halted and I never got a command prompt. I then tried the same installer on an old Compaq Deskpro C400 (400mhz Celeron, which is about six years old with IDE drives, and all installs finished okay. The only way that I could use the installer on my new PC's was to pick the packages that I wanted and abort the install process when the last package was installed and before the installer had a chance to do its final configuration. I then copied my configuration files from a floppy which set the paths and loaded drivers and such. I then installed my process control application and all is working fine. - 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] EDIT yes no hotkeys
Hello Eric, you wrote: > Still it is better to have the right pointer type. Not sure what the > bug is, but pointing to the wrong kind of object cannot be the solution. Of course. But you know the Edit's code much better than I know it... -- Oleg O. Chukaev - 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] DOSFSCK timer
Hi, Eric 12 minutes to do a 2045 Mb drive partition on one of my older Celeron 400Mhz systems -- not bad! Counter moves two-three times a second. - 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] Announce: dosfsck 2.11c with progress info
Hi all, please update your dosfsck to www.coli.uni-saarland.de/~eric/stuff/soft/by-others/dosdosfsck-2.11c.zip which now has progress in for for the -t option which can be enabled by the -v option. If you use -t without -v, is shows a hint "use -v" :-). Background: The -t option of dosfsck takes ages, as it is a full surface scan. Even worse, the scan works by FIRST test- reading all files and directories (so you get different types of checks for file X, then same checks for the next file, etc) and THEN test-reading all unused clusters in linear order. So no nice "read large chunks in block mode" or anything -> slow. Dosfsck already had a bit of progress info during "checking files and directories" (printed a "." every N files). Together with the new progress info (prints "N MB done" style text), even people who have the bad habit of using -t will no longer think that dosfsck got stuck. It only takes long with -t ;-). The full changelog entry is: version 2.11.dos3 (8/2007) - check.c, fat.c: Added messages about -t option being slow (effectively a full surface scan) and added progress info in -t -v mode for that, printing "N MB done" after each MB of scanned free space. Used space is already covered by the "print a dot each N files" progress info, which uses 10 times more dots now if -t mode is on :-). - check.c, fat.c: Set timestamp for undeleted or un-lost files to a non zero value (1.1.2007) and set un-lost to current date/time if in DOS. - 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] FreeDOS works for me!
I'm sorry guys and girls, but I've been working with FreeDOS for quite some time and I don't understand why on earth some of you have such problems, getting FreeDOS to work :-/ I've got FreeDOS working on a dedicated machine, without a glitch! In my point of view there's absolutely *nothing* wrong with the installation and configuration program. I simply don't get it, because it works perfectly for me, or am I crazy Huh? |_|0|_| Marti T. van Lin |_|_|0| http://ml2mst.googlepages.com |0|0|0| http://osgeex.blogspot.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
[Freedos-user] ssh to FreeDOS on LINUX under qemu...whew...
I am setting up a LINUX, openSUSE 10.2, with FreeDOS under qemu so that it can be accessed remotely for data updates through an old Clipper program. So my first try was to just setup a client to log onto LINUX box and try to boot a qemu image of FreeDOS. Well it booted but the screen did not show in the ssh session window but did appear on the LINUX box. It was not accessible at the LINUX keyboard or the ssh client machine. So I clearly do not have it setup to do show on the client machine. Where do I start to allow the remote access of the qemu-FreeDOS from the client? Can I access any FreeDOS setup remotely? -- John S. Wolter President Wolter Works Mailto:[EMAIL PROTECTED] Desk 1-734-665-1263 Cell: 1-734-904-8433 - 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
