[LoneCrusader]

jaclaz, on Feb 14 2010, 06:09 AM, said:

Sorry I missed the part where you wrote:
"I am using a modified Windows 98 install floppy boot disk image using JO.SYS as El-Torito floppy emulation using MSCDEX.EXE "

Boy, do I hate these Romulan cloaking devices!




jaclaz

Well, I did say those things, just not ALL in one post, or one sentence.

But you're dealing with a TOS Romulan, not one of those bastardized TNG Romulans, so I have some honor.
I very much appreciate your help and your expertise jaclaz, I think there's been a lot of miscommunication in this thread.

I'm going to go back to the basics on this one, and start by asking what should be a simple enough question to be able to get a definite Yes or No answer to, and should be able to verify with a simple experiment.

------------------------------------------------------------------

Is it possible to use a standard Windows 98 Boot Disk with standard El Torito Floppy Emulation to create a bootable DVD?


If the answer is Yes, I would greatly appreciate it if someone could actually test this for me and give me a detailed report on the process used, software/hardware/media used, and the results, as all of my tests have been unsuccessful. I would prefer to use this method, as it was my original intent. If I can get a standard floppy working this way, then I can work on finding out if my custom one works or not.

If the answer is No, then we can move on to discussion of MKISOFS and GRUB4DOS.

------------------------------------------------------------------

cdob, on Feb 14 2010, 09:47 AM, said:

Well mscdex does work with "-iso-level 4", as long you use DOS names. That's upper case names.
SHSUCDX support lowercase ISO9660 names too.

Anyway it's unclear still: hardware or software.
Did you read the CD to a image and write a DVD so far?


Win98 Jo.sys does work at a floppy emulation 4.29gb DVD.

mkisofs -v -D -N -V WIN9XDVD -b floppy.ima -hide floppy.ima -hide boot.catalog -split-output -o WIN9XDVD.ISO D:\temp\WIN98

manpage

Quote

-split-output
Split the output image into several files of approximately 1 GB. This helps to create DVD sized ISO-9660 images on operating systems without large file support. Cdrecord will concatenate more than one file into a single track if writing to a DVD. To make -split-output work, the -o filename option must be specified. The resulting output images will be named: filename_00,filename_01,filename_02...

I know what standard DOS filenames are.
What is puzzling to me about this, is that I have created DVD's before using mixed case and length file names (of course the DOS files were only accessed in DOS and vice versa) and never encountered a problem like this.

It seems that MKISOFS and/or the -iso-level 4 option translated ALL of my DOS filenames within the ISO to lowercase, even though they showed up as uppercase before under normal DOS conditions. This is idiotic.
I assume -iso-level 3 will not do this? Or will it translate all of the lowercase names to uppercase?
This must be a "bug" (from DOS/Windows standpoint) somehow left over from MKISOFS being a Linux command, as Linux is case sensitive.

I stand by what I said earlier, MKISOFS belongs in the trash bin.

You say it is possible to use standard floppy emulation on a DVD. I'm very glad to hear that, (per my question above) could you please give a more detailed report on how it is done?

I read the CD that I had successfully created earlier using my custom floppy image and standard El Torito emulation to an ISO. Then tried burning it to a DVDRW on a different machine. Nero refused to burn it, ejected my DVDRW and requested a CD or CDRW. MagicISO burned it to the DVDRW and reported success, but the disc was unreadable on any system I put it in.

[jaclaz]

LoneCrusader, on Feb 14 2010, 06:32 PM, said:

I very much appreciate your help and your expertise jaclaz, I think there's been a lot of miscommunication in this thread.

Not really, we're having some fun, that's all.


The problem is that you want to "lead" the discussion:

LoneCrusader, on Feb 14 2010, 06:32 PM, said:

If the answer is No, then we can move on to discussion of MKISOFS and GRUB4DOS.

Which is allright, but doing so it will take longer than you might expect, mainly because you have your own opinions (which is good ) but some of them are based on assumptions or presumptions:

LoneCrusader, on Feb 14 2010, 06:32 PM, said:

I know what standard DOS filenames are.
....
I assume -iso-level 3 will not do this? Or will it translate all of the lowercase names to uppercase?
This must be a "bug" (from DOS/Windows standpoint) somehow left over from MKISOFS being a Linux command, as Linux is case sensitive.

I'll astonish you telling you that DOS filenames on CD are NOT the same as the DOS filenames you know about (slightly).
If you want to take the RED pill, you should know that rabbit holes may be deeper than what you might think :
http://www.cs.cmu.ed...15p/iso9660.pdf


Now you have 3 (three) willing helping members:

• dencorso
  
• cdob
  
• jaclaz

that are telling you, more or less:

Quote

dump that d@mn MSCDEX.EXE and use SHSUCDX instead!

to which you reply, again more or less:

Quote

no, thanks, I love MSCDEX.EXE and won't change it.

I wonder what MSCDEX.EXE has done to you to get such an affection in return....

jaclaz

[LoneCrusader]

jaclaz, on Feb 14 2010, 01:10 PM, said:

The problem is that you want to "lead" the discussion:
....
your own opinions (which is good ) but some of them are based on assumptions or presumptions:
....
dump that d@mn MSCDEX.EXE and use SHSUCDX instead!
....
I wonder what MSCDEX.EXE has done to you to get such an affection in return....
jaclaz

If any or all of my assumptions are wrong, then feel free to correct me. I have said this before and have stood corrected by you before. Just be specific and explain WHY they are wrong.

You still did not answer the question that I asked.

You are leading the discussion, because you are trying to persuade me to use MKISOFS, GRUB4DOS, and SHSUCDX, without giving me an answer as to whether I can use a standard Win98 Boot Disk and standard El Torito emulation to do this.

I do not want to use ANY of these things if this project can be accomplished without them.

I seem to remember another thread where I asked you to recommend a specific program to do something, and you refused to do so. But now, you act as if MKISOFS, GRUB4DOS, and SHSUCDX are the only way to achieve this.

If they ARE the ONLY way to do this, then explain WHY?



MSCDEX has NEVER ONCE failed to work for reading ANY OPTICAL DISC that I have wanted to use.

I see no reason to change it simply based on someone saying "SHSUCDX is better."
If I followed this principle then I would be using Windows 7 because some id*** says that "It's better."

If it isn't broke, don't fix it. When it fails me under normal conditions then I will concede that you are correct. However, based on my experiences here, I do not consider anything created by MKISOFS to be "normal."

I might also add, that the first DVD that I created with MagicISO using the standard emulation CAN BE READ PERFECTLY with MSCDEX using a Boot Floppy to access it. It fails to Boot, but otherwise is PERFECT.

[cdob]

LoneCrusader, on Feb 14 2010, 12:32 PM, said:

If the answer is No, then we can move on to discussion of MKISOFS and GRUB4DOS.

First I suspect hardware still.

Quote

What is puzzling to me about this, is that I have created DVD's before using mixed case and length file names (of course the DOS files were only accessed in DOS and vice versa) and never encountered a problem like this.

Did you used mixed case ISO9660 names previously?
Did you used two independend filesystems? Upper cased ISO9660 names and mixed case Joliet names?

Quote

It seems that MKISOFS and/or the -iso-level 4 option translated ALL of my DOS filenames within the ISO to lowercase

As the manpage indicate -iso-level 4 map to ISO9660:1999.
ISO9660:1999 allows mixed case ISO9660 names.
Mkisofs print a warning if you request a -iso-level 4 file system.
Mkisofs preserve case:
a upper case name from the OS goes to a upper case ISO9660 name
a lower case name from the OS goes to a lower case ISO9660 name
The user requested this behaviour by selecting iso-level 4

Quote

even though they showed up as uppercase before under normal DOS conditions.

The OS case names are preserved at iso-level 4. I don't know normal DOS conditions. Which DOS do you use?

Win98 command prompt:
A directory name "DirectX" goes to "DirectX" at ISO9660 name. The case is preserved.

Quote

I assume -iso-level 3 will not do this?

ISO9660 level 3 allows uppercase names only. ISO9660 names are upper cased.

Quote

This must be a "bug" (from DOS/Windows standpoint) somehow left over from MKISOFS being a Linux command, as Linux is case sensitive.

It's follow ISO9660 requirements. Feel free to read ISO9660 specification.

Quote

I stand by what I said earlier, MKISOFS belongs in the trash bin.

I don't think so.
Mkisofs is a very reliable application.
Trash input result to trash output. Good input result to good output.

Quote

I'm very glad to hear that, (per my question above) could you please give a more detailed report on how it is done?

I used a Win98 SE OEM CD. This CD is bootable and joy.sys included already.
I extracted files including floppy image and added a 3.7GB file.
And installed at VMware Player.

Quote

I read the CD that I had successfully created earlier using my custom floppy image and standard El Torito emulation to an ISO. Then tried burning it to a DVDRW on a different machine. Nero refused to burn it, ejected my DVDRW and requested a CD or CDRW.

Yes, that's a well known Nero bug.

Quote

MagicISO burned it to the DVDRW and reported success, but the disc was unreadable on any system I put it in.

Broken burn application, DVD media or writer.
A CD image is writable and bootable at DVD.
We are back at broken hardware. CMC media are for the trash bin.

[jaclaz]

LoneCrusader, on Feb 14 2010, 07:59 PM, said:

You are leading the discussion, because you are trying to persuade me to use MKISOFS, GRUB4DOS, and SHSUCDX, without giving me an answer as to whether I can use a standard Win98 Boot Disk and standard El Torito emulation to do this.

I do not want to use ANY of these things if this project can be accomplished without them.

No prob.
Definitely they are not the only ones.
We have a whole catalog of alternate tricks.
But, JFYI, unless I am mistaken, under the terms of the contract I signed, I am in no way obliged to:

• answer all questions
  
• answer questions
  
• recommend (or NOT recommend) software
  
• attempt persuading anyone (or fail to) over anything
  
• prove (or fail to prove) ANYTHING

All I do is trying to see if I can help, but I will do it with my methods and at my own pace, take it or leave it, no offence intended, and no offence taken.

I won't get involved in a flame war about MSCDEX.EXE vs. SHSUCDX.EXE or mkisofs vs magiciso or whatever, they all seem to me like King Kong vs. Godzilla (and JFYI, the dinosaur can get rid of that grown up chimpanzee with one hand tied behind his back, anytime )

You want MSCDEX.EXE, have it, it's all yours.

Now, back to the problem.

Let me see if we can sum up the original problem:

• you made a DVD that does not boot
  
• you made it with a custom floppy image
  
• you made it with MagicISO

The problem can be:

• in your DVD hardware
  
• in your custom floppy image
  
• in MagicISO
  
• in a PBCAK

My first idea was that it was MagicISO or the PBCAK .

I simply suggested a way to test if that was the problem, but you have a number of limits in your current environment:

• no VM
  
• no certainty about the DVD hardware

From what you report and from results of your tests with Nero, I am starting to really think it is #1 above, and if this is the case there is no need to change anything.

Try doing yet another attempt with IMGBURN:
http://www.imgburn.com/
using these instructions:
http://forum.imgburn...?showtopic=1779
and your usual floppy image as boot image.

If it's another coaster, I would say that it is a hardware problem, so you can forget everything about mkisofs and it's commands and about MSCDEX vs. SHSUCDX, and even this whole thread, just go to your trusted PC dealer, fork from a few bucks and get a new burner.



jaclaz

[LoneCrusader]

cdob, on Feb 14 2010, 02:27 PM, said:

Did you used mixed case ISO9660 names previously?
Did you used two independend filesystems? Upper cased ISO9660 names and mixed case Joliet names?

Since I was using graphical tools, I never paid attention to these settings. All I know is that they worked, without any bizarre errors.

cdob, on Feb 14 2010, 02:27 PM, said:

As the manpage indicate -iso-level 4 map to ISO9660:1999.
ISO9660:1999 allows mixed case ISO9660 names.
Mkisofs print a warning if you request a -iso-level 4 file system.
Mkisofs preserve case:
a upper case name from the OS goes to a upper case ISO9660 name
a lower case name from the OS goes to a lower case ISO9660 name
The user requested this behaviour by selecting iso-level 4

If this is the case, I believe (I may be wrong) the problem may have been the fact that Windows 98 automatically displays file names in lowercase except for the first letter.

cdob, on Feb 14 2010, 02:27 PM, said:

The OS case names are preserved at iso-level 4. I don't know normal DOS conditions. Which DOS do you use?

Whichever one is standard in 98SE. 7.0 I think.

cdob, on Feb 14 2010, 02:27 PM, said:

I don't think so.
Mkisofs is a very reliable application.
Trash input result to trash output. Good input result to good output.

My input was specifically stated above. What was wrong with it?

cdob, on Feb 14 2010, 02:27 PM, said:

We are back at broken hardware.

I do not have broken hardware in multiple machines.

-------------------------------------------------------------------------------------------------------

jaclaz, on Feb 14 2010, 02:36 PM, said:

But, JFYI, unless I am mistaken, under the terms of the contract I signed, I am in no way obliged to:

• answer all questions
  
• answer questions
  
• recommend (or NOT recommend) software
  
• attempt persuading anyone (or fail to) over anything
  
• prove (or fail to prove) ANYTHING

All I do is trying to see if I can help, but I will do it with my methods and at my own pace, take it or leave it, no offence intended, and no offence taken.

None taken. You are under no obligations, and I appreciate your help and suggestions. However, if you're going to make suggestions, I feel that you should be able to explain why you are recommending one thing over another. One can go anywhere on the internet and find an endless supply of opinions and suggestions, but if they cannot be backed up with good reasoning, they are worthless.

I am not implying that you could not back up your recommendations if you so desired.

jaclaz, on Feb 14 2010, 02:36 PM, said:

I won't get involved in a flame war about MSCDEX.EXE vs. SHSUCDX.EXE or mkisofs vs magiciso or whatever

I have no desire to argue about these things either, I simply asked for an explanation of why you consider one to be better than the other and why I should use one over the other.

jaclaz, on Feb 14 2010, 02:36 PM, said:

Now, back to the problem.

Let me see if we can sum up the original problem:

• you made a DVD that does not boot
  
• you made it with a custom floppy image
  
• you made it with MagicISO

The problem can be:

• in your DVD hardware
  
• in your custom floppy image
  
• in MagicISO
  
• in a PBCAK

My first idea was that it was MagicISO or the PBCAK .
I simply suggested a way to test if that was the problem, but you have a number of limits in your current environment:

• no VM
  
• no certainty about the DVD hardware

Yes.

jaclaz, on Feb 14 2010, 02:36 PM, said:

Try doing yet another attempt with IMGBURN:
http://www.imgburn.com/
using these instructions:
http://forum.imgburn...?showtopic=1779
and your usual floppy image as boot image.
jaclaz

Why do I have a feeling this program might be a GUI for MKISOFS?
Just Kidding


BTW, it works now. No bizarre errors, long file names, short file names, all caps in DOS, MSCDEX functioning properly, JO.SYS booting properly, etc etc. MagicISO and Nero must have been the culprits, as both of them failed to produce a properly bootable DVD.

This post has been edited by LoneCrusader: 14 February 2010 - 03:40 PM

[cdob]

LoneCrusader, on Feb 14 2010, 03:21 PM, said:

Since I was using graphical tools, I never paid attention to these settings.

Well, that's the drawback of graphical tools.
A user dosn't learn back ground knowledge.

Quote

My input was specifically stated above. What was wrong with it?

The mentioned input was correct.
But the file names are hard disk wasn't mentioned.
I asssumed upper case names.

Quote

Windows 98 automatically displays file names in lowercase except for the first letter.

Don't trust explorer view. The explorer does NOT view direcctory and file names at hard disk.
DOS winfile does show direcctory and file names at hard disk.

Quote

I do not have broken hardware in multiple machines.

Then there is another reason.
Broken burn application was mentioned already.

Quote

BTW, it works now

Congratulations.
Then it was the burn application. Yes ImgBurn is a very trustworthy application as for burning a image.

I'm curious: did you used the Win98 machine and ImgBurn?

[LoneCrusader]

cdob, on Feb 14 2010, 05:22 PM, said:

Well, that's the drawback of graphical tools.
A user dosn't learn back ground knowledge.

This has definitely been a learning experience.

cdob, on Feb 14 2010, 05:22 PM, said:

Congratulations.
Then it was the burn application. Yes ImgBurn is a very trustworthy application as for burning a image.
I'm curious: did you used the Win98 machine and ImgBurn?

Yes, I took a few files out of my ISO_Root folder so that the ISO would be <4GB for FAT32, but I also noticed that ImgBurn has the ability to split the ISO into multiple files I have not tested that particular item yet however.

Thanks for your help!

This post has been edited by LoneCrusader: 14 February 2010 - 04:32 PM

[dencorso]

First of all, I'm glad you've solved your problem and now has the working bootable DVD you sought!
I decided to keep out of the discussion in the last two days, so as to let it progress unhindered, because I firmly believe in "too many doctors have killed a king!", the purported last words of the Emperor Hadrian.
Now I feel I must add some comments, about one thing that remained unsaid:

jaclaz, on Feb 14 2010, 04:10 PM, said:

I wonder what MSCDEX.EXE has done to you to get such an affection in return....

LoneCrusader, on Feb 14 2010, 04:59 PM, said:

MSCDEX has NEVER ONCE failed to work for reading ANY OPTICAL DISC that I have wanted to use.

But it will, rest assured it will!
And while I agree with jaclaz:

jaclaz, on Feb 14 2010, 05:36 PM, said:

I won't get involved in a flame war about MSCDEX.EXE vs. SHSUCDX.EXE

and I much less want to be the starter of such a flame war, I'll say that the reason for recommending quite strongly SHSUCDX is simply that it was written to be much more forgiving than MSCDEX, so that it can read many optical media that are beyond MSCDEX strict format requirements. Even if you don't feel like testing it right now, do have a copy of it in your toolbox, because, sooner or later, you'll find it quite handy. And because it's open source and very well documented (although you'd have to gather at least three versions to have access to all existing documentation: John McCoy's 1.4b, Jason Hood's 3.02 and Jack Ellis' 3.03E, which is the current one). And because it's still supported and actively developed (at least until last year).

[LoneCrusader]

dencorso, on Feb 15 2010, 12:10 AM, said:

First of all, I'm glad you've solved your problem and now has the working bootable DVD you sought!
I decided to keep out of the discussion in the last two days, so as to let it progress unhindered, because I firmly believe in "too many doctors have killed a king!", the purported last words of the Emperor Hadrian.
Now I feel I must add some comments:

jaclaz, on Feb 14 2010, 04:10 PM, said:

I wonder what MSCDEX.EXE has done to you to get such an affection in return....

LoneCrusader, on Feb 14 2010, 04:59 PM, said:

MSCDEX has NEVER ONCE failed to work for reading ANY OPTICAL DISC that I have wanted to use.

But it will, rest assured it will!
.....I'll say that the reason for recommending quite strongly SHSUCDX is simply that it was written to be much more forgiving than MSCEDEX, so that it can read many optical media that are beyond MSCDEX strict format requirements. Even if you don't feel like testing it right now, do have a copy of it in your toolbox, because, sooner or later you'll find it quite handy....

When that day comes I will be perfectly willing to give SHSUCDX a try.

I don't have a problem with any of the tools discussed in this thread except MKISOFS
In fact, I've had some ideas about using GRUB4DOS for another project, but I must find a way to use it to make a bootable ISO without having to use mkisofs, haha.

Anyhow, thanks for your help as well.

[jaclaz]

LoneCrusader, on Feb 14 2010, 10:21 PM, said:

BTW, it works now. No bizarre errors, long file names, short file names, all caps in DOS, MSCDEX functioning properly, JO.SYS booting properly, etc etc. MagicISO and Nero must have been the culprits, as both of them failed to produce a properly bootable DVD.

To sum up, we now know that two apps "automagically" created a coaster on your particular setup and a third one "automagically" created a working DVD.

We don't know whether it was:

• a "glitch in the matrix" (which would likely not happen again/be reproducible)
  
• an incompatibility of some kind with the media
  
• an incompatibility of some kind with the hardware
  
• an incompatibility of some kind with your source file structure or whatever
  
• a PBCAK

So, we have not learned much, apart from something we already knew , that IMGBURN is a very dependable app.

In other words, the problem is solved , but we don't know WHY it happened, nor HOW it can be fixed should it happen again.

Can we count you in the basket of happy bunnies, now?
http://www.msfn.org/board/index.php?showto...28727&st=10



jaclaz

[cdob]

LoneCrusader, on Feb 14 2010, 11:33 PM, said:

I don't have a problem with any of the tools discussed in this thread except MKISOFS

Well Nero and MagicIso provided a non bootable DVD.

I understand the main difference was the burn engine.
What about writing the CD image to DVD with ImgBurn?

The true reason may be hardware still: burner firmware or media
A good burn engine knows burner firmware limitations and provide exceptions for certain firmwares.

Another question:
Does mscdex support a media greater 4gb ?

Quote

I've had some ideas about using GRUB4DOS for another project, but I must find a way to use it to make a bootable ISO without having to use mkisofs

Well you decline the most reliable ISO build engine.

Grub4dos search a file menu.lst. A file menu.lst is not MENU.LST.
This is case sensitive at ISO9660 and Rock Ridge. Joliet is not supported.
Use either a ISO9660 menu.lst or a Rock Ridge menu.lst.

There are three approaches:

1) Use a ISO9660 MENU.LST and a Rock Ridge menu.lst.
Mkisofs and MagicIso support Rock Ridge.

2) A file menu.lst is possible within ISO9660:1999.
First set appropiate case at hard disk to files and directories.
Build a ISO9660:1999 media.

MagicIso, Nero and ImgBurn support ISO9660:1999 too.
All previous mentioned tools support ISO9660:1999.
So does mscdex at given limitations: DOS (upper case) names only

3) Or patch grub4dos: change menu.lst to MENU.LST
Then you may use a ISO9660 name MENU.LST.

BTW:
Win98 can't read a 8.4gb ISO9660 file from DVD.
A 8.4gb file is within ISO9660 level 3.

[LoneCrusader]

jaclaz, on Feb 15 2010, 04:24 AM, said:

To sum up, we now know that two apps "automagically" created a coaster on your particular setup and a third one "automagically" created a working DVD.

We don't know whether it was:

• a "glitch in the matrix" (which would likely not happen again/be reproducible)
  
• an incompatibility of some kind with the media
  
• an incompatibility of some kind with the hardware
  
• an incompatibility of some kind with your source file structure or whatever
  
• a PBCAK

So, we have not learned much, apart from something we already knew , that IMGBURN is a very dependable app.

In other words, the problem is solved, but we don't know WHY it happened, nor HOW it can be fixed should it happen again.

Can we count you in the basket of happy bunnies, now?
jaclaz

Yes I suppose I am a "happy bunny" now.
And I must thank you again jaclaz for another very good program recommendation (ImgBurn). I just wish we had taken this route to begin with.

Actually it may not be that difficult to reproduce, or maybe even to explain what was going on. This time I did pay attention to the filesystems settings during setup. The resulting DVD that worked had two filesystems - ISO9660 (Bootable) + UDF 1.02.

I do not claim to understand all of these different CD filesystems, however, we made references to Joliet in the MKISOFS command syntax, and it seems that Joliet was not used/required, but UDF was instead.

If any of you have questions about the resulting DVD, I'd be happy to try to answer them.

----------------------------------------------------------------------------

cdob, on Feb 15 2010, 06:36 AM, said:

What about writing the CD image to DVD with ImgBurn?

The true reason may be hardware still: burner firmware or media
A good burn engine knows burner firmware limitations and provide exceptions for certain firmwares.

Another question:
Does mscdex support a media greater 4gb ?

These will require further testing. When I get a chance, I will try to report back on these questions.

[submix8c]

JFYI (in case you didn't know)... In Win9x, there's an Explorer Folder Option "Allow Uppercase Filenames" that, if not set, displays/creates "Abc", as opposed to "ABC". In addition, in Windows, if only ISO is used on a CD, only ISO names will be displayed (uppercase, hopefully), and if Joliet is used, then the Joliet names will be displayed (ignoring the ISO "directory" on CD). For the purpose of Bootable Image, you need the ISO "directory", as DOS can't access Joliet "directories". This is true (AFAIK) for all bootable CD's (at least Windows). ...And I'm under the impression (?) RockRidge is not very useful for Windows.

This post has been edited by submix8c: 15 February 2010 - 10:19 AM

[cdob]

LoneCrusader, on 15 February 2010 - 09:04 AM, said:

I do not claim to understand all of these different CD filesystems

That's the most importand part at a multi boot CD.
Choose filesystems and extensions required by integrated parts.
You can easily shoot yourself in the foot.
A simple filesystem change may prohibit booting.

LoneCrusader, on 15 February 2010 - 09:04 AM, said:

it seems that Joliet was not used/required,

Yes, Joliet is not required for a windows installation.

Quote

but UDF was instead.

No, that's false. UDF is not required.
Mscdex dosn't read UDF. Installation dosn't use UDF.
UDF is a waste of space.

Remember you compare a ISO9660 (1988) media with another ISO9660:1999 media.

cdob, on Feb 15 2010, 06:36 AM, said:

Another question:
Does mscdex support a media greater 4gb ?

After testing, yes mscedx does read a file at end of a DVD. A media greater 4gb is supported.

[LoneCrusader]

Well, I'm back again everyone.

After using my new DVD for several days, I have only discovered two odd problems.

I have found no problems with booting the DVD or with JO.SYS, etc.
I have found no problems accessing the DVD is DOS with MSCDEX or using any of the DOS tools.
I have found no problems with the DVD in Windows 98SE or Windows ME.

However, I am having a strange problem with the DVD in Windows 95C. In Windows 95, and only 95, some of the names of the files and folders are truncated (not like DOS with a ~, they just stop), and some of the characters in the names of the files or folders are changed, ( ex. & , ! , and a Space changed to _ ).

I have previously used a CD in Windows 95 that contained these exact same files and folders, with the exact same names, and they were properly displayed. What would cause it to be different now?

The second problem - VPC 5 will not capture the DVD or the ISO at all, but it functions in a real environment.

This post has been edited by LoneCrusader: 27 February 2010 - 02:47 PM

[dencorso]

LoneCrusader, on 27 February 2010 - 02:43 PM, said:

I have previously used a CD in Windows 95 that contained these exact same files and folders, with the exact same names, and they were properly displayed. What would cause it to be different now?

It's probably a bug in CDFS.VxD... Try using the one from your Win 98SE installation instead (substituted by hand, the worst that can happen is it crashing windows, but then all you need to do is substitute it back).

[LoneCrusader]

dencorso, on 27 February 2010 - 07:26 PM, said:

It's probably a bug in CDFS.VxD... Try using the one from your Win 98SE installation instead (substituted by hand, the worst that can happen is it crashing windows, but then all you need to do is substitute it back).

Copied CDFS.VXD from 98SE (Which had a version number of 4.10.1998, guess it was not updated for SE?) and substituted it for the Windows 95 one (4.00.1112).

This resulted in the DVD Drive showing up as a "Removable Disk" like a USB stick in 98SE w/NUSB, and when I clicked on it said the drive was not formatted and it asked me if I wanted to format it.



EDIT: Obtained CDFS.VXD 4.00.1113 from MDGx, (Last version I could find a reference to for 95) this did not correct the error either.

This post has been edited by LoneCrusader: 28 February 2010 - 12:59 AM

[cdob]

LoneCrusader, on 27 February 2010 - 02:43 PM, said:

I have found no problems with booting the DVD or with JO.SYS, etc.
I have found no problems accessing the DVD is DOS with MSCDEX or using any of the DOS tools.
I have found no problems with the DVD in Windows 98SE or Windows ME.

However, I am having a strange problem with the DVD in Windows 95C. In Windows 95, and only 95, some of the names of the files and folders are truncated (not like DOS with a ~, they just stop), and some of the characters in the names of the files or folders are changed, ( ex. & , ! , and a Space changed to _ ).

Windows 98 support UDF and list UDF names.
Windows 95 dosn't support UDF and list ISO9660 names.

What about nice ISO9660 names at DVD?

[submix8c]

...Also (using OSCDIMG/CDimage) using NO udf and "Use ANSI vs OEM" may work (not sure if equivalents are in other burning software, e.g Nero, but probably...). This prevents the "truncation" but provides a warning instead. Using OSCDIMG/CDImage, this provides a "pure" ISO (no Joliet) with the original file/folder names.

OSCDIMG=CDIMAGE (same functions).

imgpgm -l"label" -tMM/DD/YY,HH:MM:SS -g -h -c -b"x:\path\boot.ima" -x -o -oc -os -w1 -w2 -w3 -m "x:\srcpath" "x\tgtpath\isoname.iso"

Just make an ISO (with whatever Image Program), mount it (several freeware ISO mount software, including Virtual CD from MS), and look at it...

HTH

edit - Still working on solution to other topic(s) as well. Good progress...

This post has been edited by submix8c: 28 February 2010 - 10:20 AM