How to set up a DVD project in UDF 1.50 Win 95 plateform ?

[ced_voyage]

All is the object.

 

I would like to set up a project in UDF with the following parameters :

UDF 1,50 with Win95 Platform compatibility.

 

I just manage to get a DOS, Win3.X compatibility with the software.

 

What is the option or the configuration to apply to have the expected Win95 compatibility ?

 

Thanks.

[LIGHTNING UK!]

That's the earliest OS it works with... and DOS / Win 3.x predates Windows 95, so Windows 95 is already supported.

 

So if you want to use UDF 1.50, just select it in the list and build your image.

[ced_voyage]

hello,

I think there was a misunderstanding. I know when came DOS Win3.x and Win95 ... I work in computer science for 20 years

 

I gonna explain in different words my need.

 

I have a DVD-data 8,5Go which includes two filesystems ISO+UDF. I checked the settings with ISOBuster, then I would like to reproduce it in a new project.

 

For the ISO part I can manage to do the settings correctly.

However, when I work in the UDF filesystem, I need to get the following settings : UDF 1,50 with Win95 platform.

These platform is one setting in the UDF filesystem format.

 

I tried dozen and dozen of burning software. I did not find one which is able to set this. Sometimes I get UDF 1,02 ; sometimes 1,50 but with DOS Win3.x plaftorm (never getting the choice to choose the platform compatibility at DVD creation).

 

And when finaly I found a software which is able to set a project in UDF 1,50 with Win95 platform compatibility , I do not have the ISO filesystem in my hybrid DVD.

 

I repeat again, I do not work on a Win95 OS, this is just one setting I would like to set up in the UDF filesystem format at DVD hybrid creation.

[ced_voyage]

oups doobloun

Edited July 26, 2014 by ced_voyage

[LIGHTNING UK!]

Sorry, I was wrong earlier...

 

The thing you're talking about is a debugging feature. It tells you (or rather the developer) which OS the disc was made on. ImgBurn actually leaves the fields blank (zeroed) which should translate to 'undefined' and not DOS/Windows 3.1 as IsoBuster is displaying.

 

Look up 'IdentifierSuffix' and 'OS Class' / 'OS Identifier' in the UDF specs.

 

There's no benefit to setting it to Windows 95, it has nothing to do with compatibility etc.