Skip to contentSkip to conversation

unable to boot as user

DISCUSSION Stas Sergeev 3 participants 4 messages Jun 16, 2002 – Jun 17, 2002

lore
Share & tools
lore
#0 lore raw

Hello.

Quoted 2 lines · Baurjan Ismagulov

I've thought about that, but was not sure whether that was indended behaviour for bootoff.

That is intended behaviour for bootoff but since you don't use bootoff...

Quoted 3 lines

however, for some
reason, dosemu disables a: after booting, which results in "Current drive is no longer valid>" prompt (I don't use bootoff)

Yep, I can see something similar here.

Quoted 3 lines

which is kind
of unexpected -- all I needed floppy for was doing "sys c:" and copying a couple of files to c:.

Agreed that it is confusing, but
I don't see any clear logic to handle this setuation.
What I can propose is only the attached hack. Does it fix your problems this time?

base/misc/disks.c +9 -4
@@ -891,6 +891,12 @@
     else dp->rdonly = dp->wantrdonly;
   }
 
+  if (!FDISKS && use_bootdisk) {
+  /* if we don't have any configured floppies, we have to use bootdisk instead */
+    memcpy(&disktab[0], &bootdisk, sizeof(bootdisk));
+    FDISKS++;	/* now we have one */
+  }
+
   /*
    * Open hard disks
    */
@@ -1011,10 +1017,9 @@
   int checkdp_val;
 
   disk = LO(dx);
-  if (disk < FDISKS) {
-    if (!disk && use_bootdisk)
-      dp = &bootdisk;
-    else
+  if (!disk && use_bootdisk)
+    dp = &bootdisk;
+  else if (disk < FDISKS) {
       dp = &disktab[disk];
     switch (HI(ax)) {
       #define DISKETTE_MOTOR_TIMEOUT (*((unsigned char *)0x440))
#1 lore raw

Hello,

Quoted 4 lines · Stas Sergeev

I don't see any clear logic to handle
this setuation.
What I can propose is only the attached
hack. Does it fix your problems this time?

Yes, thank you. Why you are considering it a hack? I.e., what, in your opinion, would be a "clean" solution?

With best regards,
Baurjan.

#2 lore raw
Quoted 8 lines · Baurjan Ismagulov
Quoted 4 lines · Stas Sergeev

I don't see any clear logic to handle
this setuation.
What I can propose is only the attached
hack. Does it fix your problems this time?

Yes, thank you. Why you are considering it a hack? I.e., what, in your opinion, would be a "clean" solution?

I was just thinking: isn't $_vbootfloppy *intended* to be used with bootoff, so it needs access to a "real" floppy?

If you want to use A: permanently as a file you ought to be able to specify something like

$_floppy_a ="atapi:/path/to/image"

I am not sure if that that works now (I saw several ioctl's in disks.c, except for "atapi" where it reads #sectors/track etc. from the boot sector).

Bart

#3 lore raw
Quoted 2 lines · Bart Oldeman

I was just thinking: isn't $_vbootfloppy *intended* to be used with bootoff, so it needs access to a "real" floppy?

This is exactly what I've meant in
http://marc.theaimsgroup.com/?l=linux-msdos&m=102424304029792&w=2 by saying "intended behaviour for bootoff" in an attempt to explain why I patched the documentation rather than the code.

Quoted 4 lines

If you want to use A: permanently as a file you ought to be able to specify something like

$_floppy_a ="atapi:/path/to/image"

This works if I boot from c:. "dosemu -A" gives "Disk I/O error".

With best regards,
Baurjan.

P.S. Please cc to me, I'm not subscribed.