New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.4.6a Problem with ISOs on exFAT volumes #33

Closed
steve6375 opened this Issue Jan 24, 2015 · 14 comments

Comments

Projects
None yet
3 participants
@steve6375

steve6375 commented Jan 24, 2015

This problem does not occur with 0.4.5c (e.g. 2015-01-20)
Using 230GB SSD formatted as exFAT under VBox

fresh boot:
image

if map --hook and ls (0xff)/ we get:
image

but 0.4.5c is OK
image
image

Also NTFS is OK
image

The weird thing is, if I boot to 0.4.5c and then chainloader /grldr_046_2015-01-24 on the exFAT drive - then it works!!!

@steve6375

This comment has been minimized.

Show comment
Hide comment
@steve6375

steve6375 Jan 24, 2015

I tried latest version and map --iso-types=x and cannot make any of them work.

steve6375 commented Jan 24, 2015

I tried latest version and map --iso-types=x and cannot make any of them work.

@steve6375

This comment has been minimized.

Show comment
Hide comment
@steve6375

steve6375 Jan 27, 2015

Are you able to reproduce/fix this? I think the problem may be due to uninitialised memory in exFAT code.
If I boot using 0.4.5c and then chainloader /grldr_046 then it works OK, but if I just boot directly to grldr which is 0.4.6a version then I get this problem.

steve6375 commented Jan 27, 2015

Are you able to reproduce/fix this? I think the problem may be due to uninitialised memory in exFAT code.
If I boot using 0.4.5c and then chainloader /grldr_046 then it works OK, but if I just boot directly to grldr which is 0.4.6a version then I get this problem.

@steve6375

This comment has been minimized.

Show comment
Hide comment
@steve6375

steve6375 Jan 28, 2015

Same problem on 2GB exFAT drive!

  1. Make 2GB exFAT drive using RMPrepUSB - exFAT option and choose grub4dos option to install MBR.
  2. Add 0.4.6a /grldr and an ISO
  3. boot
    debug 2
    map /new.iso (0xff)
    ... many errors
    map --hook
    ls (0xff)/
    ... many errors

If use 0.4.5c \grldr then works fine - no problems!
if boot 0.4.5c and then chainloader \grldr_046a then works fine too!
Only if fresh/clean boot to grldr v 0.4.6a do you get errors!!!

steve6375 commented Jan 28, 2015

Same problem on 2GB exFAT drive!

  1. Make 2GB exFAT drive using RMPrepUSB - exFAT option and choose grub4dos option to install MBR.
  2. Add 0.4.6a /grldr and an ISO
  3. boot
    debug 2
    map /new.iso (0xff)
    ... many errors
    map --hook
    ls (0xff)/
    ... many errors

If use 0.4.5c \grldr then works fine - no problems!
if boot 0.4.5c and then chainloader \grldr_046a then works fine too!
Only if fresh/clean boot to grldr v 0.4.6a do you get errors!!!

@yaya2007

This comment has been minimized.

Show comment
Hide comment
@yaya2007

yaya2007 Jan 28, 2015

Collaborator

0.4.6a 2015_01_20 for expat OK?

Collaborator

yaya2007 commented Jan 28, 2015

0.4.6a 2015_01_20 for expat OK?

@steve6375

This comment has been minimized.

Show comment
Hide comment
@steve6375

steve6375 Jan 28, 2015

No - 0.4.6a does not work with exFAT - 2015-01-20 or many previous or after!

steve6375 commented Jan 28, 2015

No - 0.4.6a does not work with exFAT - 2015-01-20 or many previous or after!

@yaya2007

This comment has been minimized.

Show comment
Hide comment
@yaya2007

yaya2007 Jan 31, 2015

Collaborator

感谢 steve6375 费心的对比测试,并提供了详尽的资料。

似乎可以得出结论: 问题在exFAT。
但是对比测试只能用 1 个变量,而 “fresh boot” 与 “but 0.4.5c is OK” 却有 2 个变量,即版本号与主分区0.
“fresh boot” 80,20 21 00,07,FE FF FF,00000800,1D1C3D42
“but 0.4.5c is OK” 80,00 01 00,00,3F E0 D4,00000000,001EA800
正是分区长度 1D1C3D42 惹出事端。
位于 bios.c 的 get_diskinfo 函数。
如果将 exFAT 的主分区0修改为: 80,00 01 00,00,3F E0 D4,00000000,001EA800 应当 OK。

当然分区长度比较大就做错误处理是否恰当,就得请教不点或其他高人。

Collaborator

yaya2007 commented Jan 31, 2015

感谢 steve6375 费心的对比测试,并提供了详尽的资料。

似乎可以得出结论: 问题在exFAT。
但是对比测试只能用 1 个变量,而 “fresh boot” 与 “but 0.4.5c is OK” 却有 2 个变量,即版本号与主分区0.
“fresh boot” 80,20 21 00,07,FE FF FF,00000800,1D1C3D42
“but 0.4.5c is OK” 80,00 01 00,00,3F E0 D4,00000000,001EA800
正是分区长度 1D1C3D42 惹出事端。
位于 bios.c 的 get_diskinfo 函数。
如果将 exFAT 的主分区0修改为: 80,00 01 00,00,3F E0 D4,00000000,001EA800 应当 OK。

当然分区长度比较大就做错误处理是否恰当,就得请教不点或其他高人。

@yaya2007

This comment has been minimized.

Show comment
Hide comment
@yaya2007

yaya2007 Jan 31, 2015

Collaborator

@steve6375
在某 issues,你反映 iso9600_Joliet 在使用 ls 命令时,文件名偶尔出现乱码。
问题是由于没有执行 “unicode16大尾转小尾” 的操作。
我仔细查看代码没有找到原因。反编译了从官方下载的 grldr,也没有找到原因。
请问:是使用官方下载的 grldr?还是下载源码自己编译的 grldr?
可否上传出问题的那个 grldr?

Collaborator

yaya2007 commented Jan 31, 2015

@steve6375
在某 issues,你反映 iso9600_Joliet 在使用 ls 命令时,文件名偶尔出现乱码。
问题是由于没有执行 “unicode16大尾转小尾” 的操作。
我仔细查看代码没有找到原因。反编译了从官方下载的 grldr,也没有找到原因。
请问:是使用官方下载的 grldr?还是下载源码自己编译的 grldr?
可否上传出问题的那个 grldr?

@steve6375

This comment has been minimized.

Show comment
Hide comment
@steve6375

steve6375 Jan 31, 2015

re. exFAT problem - Disk is same in both screenshots - only difference is \grldr file has been changed.
“but 0.4.5c is OK” 80,00 01 00,00,3F E0 D4,00000000,001EA800 >> This is ISO that is being mapped, not the exFAT disk.
In 0.4.6a I get warnings about exFATdisk geometry - in 0.4.5c I do not and it works OK.

CASE 1 - WORKS

  1. \grldr is 0.4.5c version
  2. Boot to menu.lst and goto console
  3. use map/hook/ls command - all OK - no error.

CASE 2 - FAILS

  1. \grldr is 0.4.6a version
  2. Boot to menu.lst and goto console
  3. use map/hook/ls command - FAILS!

CASE 3 - WORKS
I can get 0.4.6a to work as follows if I first boot to 0.4.5c:

  1. \grldr is 0.4.5c
  2. boot to grub4dos menu and goto console
  3. chainloader /grldr_046 (reloads grub4dos menu)
  4. use map/hook/ls command - all OK - no error.

steve6375 commented Jan 31, 2015

re. exFAT problem - Disk is same in both screenshots - only difference is \grldr file has been changed.
“but 0.4.5c is OK” 80,00 01 00,00,3F E0 D4,00000000,001EA800 >> This is ISO that is being mapped, not the exFAT disk.
In 0.4.6a I get warnings about exFATdisk geometry - in 0.4.5c I do not and it works OK.

CASE 1 - WORKS

  1. \grldr is 0.4.5c version
  2. Boot to menu.lst and goto console
  3. use map/hook/ls command - all OK - no error.

CASE 2 - FAILS

  1. \grldr is 0.4.6a version
  2. Boot to menu.lst and goto console
  3. use map/hook/ls command - FAILS!

CASE 3 - WORKS
I can get 0.4.6a to work as follows if I first boot to 0.4.5c:

  1. \grldr is 0.4.5c
  2. boot to grub4dos menu and goto console
  3. chainloader /grldr_046 (reloads grub4dos menu)
  4. use map/hook/ls command - all OK - no error.
@steve6375

This comment has been minimized.

Show comment
Hide comment
@steve6375

steve6375 Jan 31, 2015

re. 在某 issues,你反映 iso9600_Joliet 在使用 ls 命令时,文件名偶尔出现乱码。

I cannot reproduce this problem of garbled text with newer versions of 0.4.6a - if I find the problem again I will report to you.

Please look at exFAT problem. Very reproducible.
Format a USB drive using RMPrepUSB - exFAT and say Yes to install grub4dos MBR so you can boot to exFAT.
image

steve6375 commented Jan 31, 2015

re. 在某 issues,你反映 iso9600_Joliet 在使用 ls 命令时,文件名偶尔出现乱码。

I cannot reproduce this problem of garbled text with newer versions of 0.4.6a - if I find the problem again I will report to you.

Please look at exFAT problem. Very reproducible.
Format a USB drive using RMPrepUSB - exFAT and say Yes to install grub4dos MBR so you can boot to exFAT.
image

@yaya2007

This comment has been minimized.

Show comment
Hide comment
@steve6375

This comment has been minimized.

Show comment
Hide comment
@steve6375

steve6375 Feb 2, 2015

That version seems to work with exFAT (initial testing OK) 👍

steve6375 commented Feb 2, 2015

That version seems to work with exFAT (initial testing OK) 👍

@chenall

This comment has been minimized.

Show comment
Hide comment
@chenall
Owner

chenall commented Feb 9, 2015

@steve6375

This comment has been minimized.

Show comment
Hide comment
@steve6375

steve6375 Feb 9, 2015

Yes - looks OK so far. thanks. Will close in about a week if no problems found. Thanks!

steve6375 commented Feb 9, 2015

Yes - looks OK so far. thanks. Will close in about a week if no problems found. Thanks!

@steve6375

This comment has been minimized.

Show comment
Hide comment
@steve6375

steve6375 Feb 14, 2015

Still looking good. Will close now. Thanks for fixing it. 👍

steve6375 commented Feb 14, 2015

Still looking good. Will close now. Thanks for fixing it. 👍

@steve6375 steve6375 closed this Feb 14, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment