What command is used to create an ISO9660 filesystem that can be properly accessed from a Windows 95/98 machine?

A.
mkisofs -l -o backup.iso /home/joe

B.
mkisofs -J -T -r -o backup.iso /home/joe

C.
mkisofs -D -T -o backup.iso /home/joe

D.
mkisofs -j -T -o backup.iso /home/joe

E.
mkisofs -d -T -o backup.iso /home/joe

Explanation:

mkisofs – create an hybrid ISO9660/JOLIET/HFS filesystem with optional Rock Ridge attributes.
-D Do not use deep directory relocation, and instead just pack them in the way we see them. If ISO9660:1999 has not been selected, this violates the ISO9660 standard, but it happens to work on many systems. Use with caution.
-T Generate a file TRANS.TBL in each directory on the CDROM, which can be used on non-Rock Ridge capable systems to help establish the correct file names. There is also information present in the file that indicates the major and minor numbers for block and character devices, and each symlink has the name of the link file given.
-r This is like the -R option, but file ownership and modes are set to more useful values. The uid

useful to the client. All the file read bits are set true, so that files and directories are globally readable on the client. If any execute bit is set for a file, set all of the execute bits, so that executables are globally executable on the client. If any search bit is set for a directory, set all of the search bits, so that directories are globally searchable on the client. All write bits are cleared, because the CD-Rom will be mounted read-only in any case. If any of the special mode bits are set, clear them, because file locks are not useful on a read-only file system, and set-id bits are not desirable for uid 0 or gid 0. When used on Win32, the execute bit is set on all files. This is a result of the lack of file permissions on Win32 and the Cygwin POSIX emulation layer.