Hacker News Reader

Comment by wizzledonker | Hacker News Reader

I've managed to get it to build about half way;

1. In linux

2. Install wine 7.5 (other versions may work, this is what I used)

3. Create a 32-bit wineprefix on a *case-insensitive* ext4 drive (https://www.collabora.com/news-and-blog/blog/2020/08/27/usin...)

4. Download MSVC 2.0 (https://winworldpc.com/product/visual-c/2x), extract and install it into the 32-bit wineprefix - Make sure you use `wine32 winecfg` and set the OS to Windows 95

5. Copy the files to C:\3d inside the wineprefix

6. Enter command prompt from wine (`wine32 cmd`)

7. `set include=C:\MSVC20\INC`

8. `.\setvars.bat`

9. `nmake`

Unfortunately wine segfaults for me when compiling one of the BRender files :'(

EDIT: Now I have Bren and Engine building! Studio does not build, reports that it doesn't know how to generate 'C:\3d\kauai\obj\wins\utilglob.obj'. Probably something simple...

View on HN

Wine dev, here. Feel free to throw me a wine log of that crash over email, I could maybe see if it's something obvious.

>case insensitive.

Just create a disk image and mkfs.ext4 it :)

   mkdir -p ~/wine/prefix

   truncate -s 10G ~/wine/wine.img
 
   mkfs.ext4 -flags -foo -bar ~/wine/wine.img

That is such an incredibly good idea haha Thanks :)

For the record, you don't need the case folding filesystem at all. Wine has been doing its own case insensitive lookups and comparisons for decades with the only problem being performance which is certainly not going to be a concern here.

i would use a real Win95,98,XP in virtualization, there could be many micro flaws using Wine with this old stuff :)

True! Might give this a go tomorrow. I'm kinda shocked it got as far as it did to be honest

im also shocked :)

maybe a step by step upgrade from 2.x->4.x->5.x->6.x needed

there are subtile changes between the very early studio versions but when reaching VS2005/2008 everything is fine for upgrade

builds for me under fresh XP with VC++ 2.0 until some globutil.obj file could not be build by nmake

Exactly the same issue I ended with. It might need some modifications. I'll have a dig

sorry this is Bens Branch: https://github.com/benstone/Microsoft-3D-Movie-Maker/commits...

Ben Stone is also working on it - maybe join forces :)

https://github.com/benstone/Microsoft-3D-Movie-Maker

there are a few that started to port: https://github.com/microsoft/Microsoft-3D-Movie-Maker/networ...

How about using Proton? It should be a little more completed for some cases.

he should just use the original system - porting to newer system always happen AFTER getting it to build on the original platform

Reply on news.ycombinator.com