Jump to content











Photo
- - - - -

Problems with latest version of GRUB4DOS

grub4dos map error. os2 win95 error

  • Please log in to reply
16 replies to this topic

#1 ppgrainbow

ppgrainbow

    Member

  • Members
  • 31 posts

Posted 2 weeks ago

Hello there! :)

I'm using the latest version of GRUB4DOS v0.4.6a (rev 2017-10-05) and I found that I can neither boot OS/2 Warp nor Windows 95 when I map drives.

When I select OS/2 Warp 4 when booting from the second hard disk image mapped as the first hard disk image, this is the error message that I get:

https://imgur.com/a/Id7fx

And when I try to boot Windows 95 from the third hard disk image mapped as (hd0), this is the error message that I get:

https://imgur.com/a/TJEc3

On a side note, when trying to boot with the Windows 95 boot disk, to try to access the third hard disk, I end up getting massive data corruption (almost 600 MB worth). I'm really lucky that I have backed up hard disk images incase something terrible goes wrong.

Now, here's are the current parameters that are used to boot OS/2 and Windows 95 under GRUB4DOS:
 

title IBM PC-DOS 6.30 / IBM OS/2 Warp 4\n\n
hide (hd0,0)
hide (hd0,4)
hide (hd0,5)
hide (hd0,6)
unhide (hd1,0)
unhide (hd1,4)
unhide (hd1,5)
unhide (hd1,6)
hide (hd2,0)
hide (hd2,4)
hide (hd2,5)
hide (hd2,6)
map (hd0) (hd1)
map (hd1) (hd0)
map --floppies=1
map --hook
root (hd0,0)
chainloader +1

 

title Microsoft Windows 95\n\n
hide (hd0,0)
hide (hd0,4)
hide (hd0,5)
hide (hd0,6)
hide (hd1,0)
hide (hd1,4)
hide (hd1,5)
hide (hd1,6)
unhide (hd2,0)
unhide (hd2,4)
unhide (hd2,5)
unhide (hd2,6)
map (hd0) (hd2)
map (hd2) (hd0)
find --set-root /IO.SYS
map --floppies=1
map --hook
root (hd0,0)
chainloader +1

 

I have used the map --hook feature to hook INT13 after mapping hard disks, but it doesn't seem to work anymore in this latest release of GRUB4DOS. If I remove the first and third hard disk images, I can boot OS/2 and if I remove the first and second hard disk images, I can boot Windows 95.

 

Looking in the latest code change located here: https://github.com/c...325630e41692e64

 

I see that there are two new parameters, "--in-situ" and "--swap-drive=DRIVE1=DRIVE2". I never used these features before.

Has anything changed in GRUB4DOS? If so, what parameters should I use to correct this error?


Edited by ppgrainbow, 2 weeks ago.


#2 ppgrainbow

ppgrainbow

    Member

  • Members
  • 31 posts

Posted 2 weeks ago

Update: I had to downgrade the version of GRUB4DOS 0.4.6a to revision 2017-08-30 and I can boot both OS/2 and Windows 95. The mapping drive function either has changed or appears to be broke with the 2017-10-05 revision of GRUB4DOS. :(

 

Has anyone tested the 2017-10-05 revision to see if you can map drives under, VirtualBox, Qemu, VMware or on a real machine yet?



#3 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13694 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 2 weeks ago

-in-situ is not "new" at all, maybe the reference you found was a bugfix of some kind.

 

It is perfectly possible that a new release, particularly if only a few days old has (temporarily) an issue, but you should report it directly to the Authors, they do come here on reboot.pro from time to time, but not very often:

https://github.com/c...grub4dos/issues

 

:duff:

Wonko



#4 ppgrainbow

ppgrainbow

    Member

  • Members
  • 31 posts

Posted 2 weeks ago

-in-situ is not "new" at all, maybe the reference you found was a bugfix of some kind.

 

It is perfectly possible that a new release, particularly if only a few days old has (temporarily) an issue, but you should report it directly to the Authors, they do come here on reboot.pro from time to time, but not very often:

https://github.com/c...grub4dos/issues

 

:duff:

Wonko

 

I have reported the issue in regards to the latest version of GRUB4DOS and I hope that the authors see it and investigate: https://github.com/c...4dos/issues/157



#5 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13694 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted A week ago

I have reported the issue in regards to the latest version of GRUB4DOS and I hope that the authors see it and investigate: https://github.com/c...4dos/issues/157

Good, as Steve suggested on Github, do test and report that the previous version works flawlessly, as per your post #2, seemingly your note:

and it worked in rev 2017-08-30 and now, it doesn't work anymore in the rev 2017-10-05 release.

isn't clear enough (probably he suspects that *something else* has changed in the meantime).

 

:duff:

Wonko



#6 ppgrainbow

ppgrainbow

    Member

  • Members
  • 31 posts

Posted A week ago

Good, as Steve suggested on Github, do test and report that the previous version works flawlessly, as per your post #2, seemingly your note:

and it worked in rev 2017-08-30 and now, it doesn't work anymore in the rev 2017-10-05 release.

isn't clear enough (probably he suspects that *something else* has changed in the meantime).

 

:duff:

Wonko

 

I tested both the 2017-08-30 and 2017-10-05 versions of GRUB4DOS and if I don't update the version of GRLDR to 2017-10-05, then I can boot OS/2 or Windows 95. If I do update GRLDR to 2017-10-05, then disk read errors occur.


Edited by ppgrainbow, A week ago.


#7 ppgrainbow

ppgrainbow

    Member

  • Members
  • 31 posts

Posted A week ago

Update: Yaya, updated GRLDR to rev 2017-10-12 and I can now boot OS/2 and Windows 95 respectively! :)

 

I had to use rev 2017-10-04 version of GRLDR and something was really buggy with the 2017-10-05 version of GRLDR!



#8 steve6375

steve6375

    Platinum Member

  • Developer
  • 6619 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted A week ago

FYI, many versions of grub4dos are buggy. I have asked YaYa to differentiate the 'good' ones from the 'beta\experimental' ones, so that anyone wanting the 'latest' version gets the latest 'good' version, but so far my pleas have fallen on deaf ears.



#9 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13694 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted A week ago

FYI, many versions of grub4dos are buggy. I have asked YaYa to differentiate the 'good' ones from the 'beta\experimental' ones, so that anyone wanting the 'latest' version gets the latest 'good' version, but so far my pleas have fallen on deaf ears.

Well, to be fair, in the past you somehow contributed to the chaos, by often suggesting (even when it was not the case/it wasn't strictly needed) to use the latest-latest version (actually needed for doing the specific "advanced" thing that you were doing, but not needed at all for most of what the common use would do), and of course the developers didn't do really-really what they declared:

http://reboot.pro/to...grldr/?p=189012

 

ppgrainbow (I am sure in perfect good faith :) but tricked by the usual "latest is better" fallacy) is using the latest-latest version without any actual *need*, in the sense that for the uses he is using grub4dos for *any* version EXCEPT latest ones that are still experimental would do nicely, including the latest "stable" 0.4.5c version:

http://grub4dos.chen....5c-2016-01-18/

 

BTW, and just for the record, at the time also Climbing (and to a lesser degree Chenall) were deaf about making a minimally ordered way of having a "current" or "recommended" release:

http://reboot.pro/to...b4dos/?p=103328

 

 

:duff:

Wonko 



#10 alacran

alacran

    Frequent Member

  • Advanced user
  • 481 posts
  •  
    Mexico

Posted A week ago

FYI, many versions of grub4dos are buggy. I have asked YaYa to differentiate the 'good' ones from the 'beta\experimental' ones, so that anyone wanting the 'latest' version gets the latest 'good' version, but so far my pleas have fallen on deaf ears.

 

I am on the way to update from 0.4.6a (rev 2016-09-20). What is the latest review you recommend?

 

Thanks in advance



#11 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13694 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted A week ago

I am going on the way to update from 0.4.6a (rev 2016-09-19). 

 

Perfect. :frusty:

 

May I ask you WHY (the heck) do you believe you *need* to update it?

 

Does the 0.4.6a (rev 2016-09-19) in *any*  way not satisfy your uses of the tool?

 

Which particular feature (missing or not fully working) have you found in 0.4.6a (rev 2016-09-19) AND that you believe has been fixed in later versions?

 

:duff:

Wonko



#12 steve6375

steve6375

    Platinum Member

  • Developer
  • 6619 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted A week ago

I use http://dl.grub4dos.c...a-2017-08-30.7z

in Easy2Boot. It has been downloaded about 400,000 times with no grub4dos issues yet reported.



#13 alacran

alacran

    Frequent Member

  • Advanced user
  • 481 posts
  •  
    Mexico

Posted A week ago

Perfect. :frusty:

 

May I ask you WHY (the heck) do you believe you *need* to update it?

 

Does the 0.4.6a (rev 2016-09-19) in *any*  way not satisfy your uses of the tool?

 

Which particular feature (missing or not fully working) have you found in 0.4.6a (rev 2016-09-19) AND that you believe has been fixed in later versions?

 

:duff:

Wonko

 

Hello Wonko it is nice to talk with you again.

 

In fact it was named as rev 2016-09-20 (grldr into the 7zip is dated 2016-09-19), already fixed my previous post.

 

To be honest it has been working fantastic for my needs, even loading some non contiguous ISO files, but after a year using it I wanted to know steve6375 current preferred version.

 

Well I have been using grub4dos for very long time since the old v0.4.4 (do not remember review) and usually updated once a year, going through 0.4.5c and later to 0.4.6a when steve6375 told us in a post about it's new capabilities: embeded USB drivers (never tested it) and non contiguous file reading (very good when your USB stick is almost full and you replace an ISO).

 

alacran



#14 ppgrainbow

ppgrainbow

    Member

  • Members
  • 31 posts

Posted A week ago

Okay! Yaya, fixed the disk I/O bug in the 2017-10-12 revision of GRUB4DOS 0.4.6a! :)



#15 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13694 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted A week ago

I use http://dl.grub4dos.c...a-2017-08-30.7z

in Easy2Boot. It has been downloaded about 400,000 times with no grub4dos issues yet reported.

Yep, this is a good sign of "stability" though I believe that users of Easy2Boot will largely (like 99% of them) only use the functions that you use through your tool, so the only kind of issue that may come out of this would be something that is hardware specific, i.e. that you have tested successfully on your hardware that for *any reason* doesn't work "as is" on some esoteric hardware of a final user.

 

I am much more confident on the reliability of the version because it passed your own tests :) than because it became "popular" and no errors were reported.

 

I just checked the "history" of the 2017-08-31 (which is strangely only available in Chinese) and seemingly there are not that many changes, only refinements (good :thumbup: ) and bug fixing (actually seemingly largely fixes for newly introduced bugs :w00t: ), couldn't detect any groundbreaking new feature. :unsure:

 

The new vol command seems like useful, but most of its functionalities could be obtained by using other pre-existing commands, I beleive, and the   enhancement on the internal USB 2.0 driver/stack, while also good news are probably not particularly relevant (in the sense that I don't think that the feature is largely used).

 

@alacran

Check issue #154 (the initial report by Steve6375 is enough), now solved:

https://github.com/c...4dos/issues/154

to understand at a glance why one should be very cautious with new releases of the 0.4.6a and why if a given version works fine on a given setup/for a given scope there is usually no actual *need* for a "final user" to update to latest 

 

:duff:

Wonko



#16 alacran

alacran

    Frequent Member

  • Advanced user
  • 481 posts
  •  
    Mexico

Posted A week ago

@ Wonko:

Thanks for your comment about caution, I understand what you mean, and appreciate it.

I have had my own bad experiences with buggy reviews, so since then to be on the safe side I always ask steve6375 (our grub4dos expertician) for his current preferred review before try a new one. Nevertheless keeping my last good one in a safe place just in case.

On the other hand if nobody download and test new reviews:

How are we going to know if they are good or not?

How are the developers going to get feedback?

Then development and improvements are going to cese.

So, somehow progress involves some risks, then it is up to us to do everything we can to mitigate them.

alacran

#17 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13694 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted A week ago

@ Wonko:

Thanks for your comment about caution, I understand what you mean, and appreciate it.

I have had my own bad experiences with buggy reviews, so since then to be on the safe side I always ask steve6375 (our grub4dos expertician) for his current preferred review before try a new one. Nevertheless keeping my last good one in a safe place just in case.

On the other hand if nobody download and test new reviews:

How are we going to know if they are good or not?

How are the developers going to get feedback?

Then development and improvements are going to cese.

So, somehow progress involves some risks, then it is up to us to do everything we can to mitigate them.

alacran

Sure :), but one thing is when you set up a new system (or USB stick, etc.), in which case you are already into experimenting and testing latest-latest makes a lot of sense, even because there might be new features that may come into use in this new setup.

 

Another thing is, once you have something perfectly working, possibly since one year or more, risking to introduce a new bug for no actual advantage.

 

And BTW this applies also to Steve6375's "approved" releases, he has the advantage (through his dedication to RMprepUSB and Easy2Boot and the success of those projects :thumbup: ) to be - besides his extensive own testing - the recipient of lots of feedback and an excellent "communication officer" with out friends Chenall and YaYa, and thus the top submitter of both bugs and requests for new features, but he is also a very advanced user of the tool, knows perfectly the documented (and most of the undocumented) syntax, etc., etc., so he is "entitled" to be experimenting with latest-latest, but this doesn't really mean that *anyone* can (or should) go latest-latest, unless specifically told to.

 

Particularly, if an earlier "stable" version works fine on the specific hardware and software you have (though possibly containing some esoteric bug, where it fails to boot on wednesday nights with full moon on Acer laptops if both an external USB keyboard and a mouse are connected at boot time, but only if the mouse is connected on the right side USB port) the new release that the good Developers produce to fix that bug does not affect you, and updating to it (possibly the day oout it was published) exposes you to a risk of a regression bug being introduced accidentally to it.

 

Now, when a new feature is introduced AND you actually *need* that new feature, of course trying it (and reporting any bug found) is a good thing, but if it ain'0t broken, don't fix it.

 

If we could convince the good grub4dos developers to actually release the thingy along the "previous" scheme where there were often releases marked as "testonly" and once in a while one marked "featured" a good half of the trouble would be solved with no or very little effort.

 

:duff:

Wonko







Also tagged with one or more of these keywords: grub4dos, map, error., os2, win95, error

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users