What you waiting for! The BetasCollector's Bootdisk Project is coming to BetaArchive and Custom OS Forums!

Status: Still in development using Visual Basic 4.0 Working Model on Windows 95 VM.
Version: 0.1

And... How to disable Windows 3.1 Boot Splash like Windows 95 is loading setup?

for the sake of taking the lazy route. I'd just say use WIN /B (Boot Logging) and let it write a BOOTLOG.TXT File. The Logo is not shown when the /B switch is present during execution.

else, you need to make a .RLE file that is black, and patch WIN.COM
Getting a link to a patching tool, will edit this post when done

EDIT:
http://www.conradshome.com/win31/files/winlogo.exe

If I remember correctly, The RLE file must have certain dimensions and must be 16bit. (I don't remember the dimensions it's been so long ago )

Hope that helps you on the Win3.1 Bootscreen part.

Use a resource editor and change the logo if thats what you're asking?

You correct! I used Virtual Basic 4.0 Working Model on Windows 95 VM. This is example. When I pressed "Partition and Format the drive", The new window appear. How to make like that?

... what... Sir, I am terribly sorry, but (and no offence), I cannot understand what you are saying, Do you want a window that has a command button that when pressed calls up a new window?

If this is the case

1. Create a new form and give it a specific Name, Let's say the form name is "MaxiForm1"
2. In the code of your command button (with the caption "Partition and Format the drive") on the "Click" event procedure, type in as follows



That should be it. If you want more of a visual representation, just ask.

Just

and show the window! You correct again! But I edited autoexec.bat and config.sys. I tryed on Windows 98 ISO Bootdisk, But failed. I tryed again on MS-DOS 6.22 and MS-DOS 5.0, But failed. I tryed to edit on MS-DOS 6.22 and MS-DOS 5.0 and get "Device I/O Error". How to fix this?

... That's not specific enough. What exactly were you trying to do?

I assume that might be BOOTLOG.TXT writing to the floppy. I suggest using my earlier (yet harder) method. If you use it. no file will be produced during boot.




Also, your autoexec.bat file should have.....


Replace C with whatever drive it will be booting from.

When I try to SYS D:, This message appears:
"Cannot SYS a network drive"
D: is an CD-ROM, not Network Drive.
Can you get the bootable MS-DOS CD-ROM that there is no RAM-DRIVE?
Also, I replaced the Visual Basic 4.0 to Visual Basic 3.0, Because 4.0 Working Model says can open 2 modules. 3.0 can open up to more modules.

What version of MS-DOS are you using?

In worst case scenario, you may have to create an image file and SYS to that, then have the bootdisk mount it.

If I installed Windows 3.1 on MS-DOS 7.00 then copied to MS-DOS 8.00
I got error, Should I use Setver and have the instructions?

Windows 3.1

win.com is comprised from three files, eg

copy /b win.cfg+vgalogo.lgo+vgalogo.rle win.com

The limitation is that Win.com is a true COM file, must be less than 64K.

Windows does stange things to DOS memory (recall that it contains a slice of alpha code), which is why it is a bugger of a thing to install and run in a VM etc.

MS-DOS 8 is intended to be a Win9x loader, does not support running things like EMM386 etc. Windows 3.1 does not run under MS-DOS 8, because MS-DOS 8 is missing the essential features. I'm pretty sure that running it under something that calls it DOS 8 will not cause any harm (i have a version of 6.22 that can be doctored to report any version of DOS).

I believe there is a patch floating around that allows Windows 3.x on MS-DOS 7x and higher..........

There is indeed such a thing. Google for '3xstart' to find it.

Actually, Windows 3.1 can be run straight from DOS 7.0. Its only for dos 7.1 that one needs the new patch.