Recommended Posts

Too bad you're living on a different continent than me, because I'd love to punch your face like I'd be trying to put out a forrest fire with a screwdriver! Either say what the deal is, aka the activation procedure (if you actually do know it, which I doubt), or **** off! Save yourself any further dickwaving!

haha.

he said 'dickwaving'.

:laugh:

Run DCE start commands, run MIL.BAT, repeat, and click okay on all error msgs.

Slow as hell though, and you need to port the files from 4029 to 4051 first (milcore.dll, sbctl.exe, etc)

23/06/2003 11:56 65,536 microsoft.windows.pplrtc-msgr.dll

19/06/2003 14:19 49,152 microsoft.windows.pplrtc-rtcv1.dll

19/06/2003 17:38 761,856 microsoft.windows.pplrtc1.dll

23/06/2003 11:56 443,392 microsoft.windows.pplrtc2.dll

07/02/2004 13:08 1,209,344 milcore.dll

02/10/2003 00:12 114,688 presentationbuildtasks.dll

02/10/2003 00:11 1,683,456 presentationcore.dll

02/10/2003 00:10 224,768 presentationcore2.dll

02/10/2003 00:11 2,007,040 presentationframework.dll

02/10/2003 01:10 1,027,584 presentationhost.dll

06/02/2004 18:59 4,608 sbctl.exe

02/10/2003 01:11 17,242,112 shell32.dll

14/02/2004 18:56 861,184 shellinterop.dll

Various other things you need as well, but that should get you started.

MIL.BAT

No problem :)

This might be of interest, as well.

Bounding box of geometry = (-0.948884,-0.930081,-0.10116) to (-0.751117,0.930081,0.10116).

Header {
	1; // Major version
	0; // Minor version
	1; // Flags
}

Material xof_default {
	0.400000;0.400000;0.400000;1.000000;;
	32.000000;
	0.700000;0.700000;0.700000;;
	0.000000;0.000000;0.000000;;
}

Material n_13___Default {
	0.588235;0.588235;0.588235;1.000000;;
	3.000000;
	0.000000;0.000000;0.000000;;
	0.000000;0.000000;0.000000;;
     EffectInstance {
      "res://shell32.dll/EFFECT/GlassEffect";
       EffectParamString { "tRefractionMap@name", ":background"; }
       EffectParamString { "tReflectionMap@name", "res://shell32/DDS/skyenvmap"; }
     }
}

// Top-most frame encompassing the 'World'
Frame Frame_World {
	FrameTransformMatrix {
  1.000000, 0.0, 0.0, 0.0, 
  0.0, 1.000000, 0.0, 0.0, 
  0.0, 0.0, -1.000000, 0.0, 
  0.0, 0.0, 0.0, 1.000000;;
	}

Frame Frame_Group01 {
	FrameTransformMatrix {
  1.000000, 0.0, 0.0, 0.0, 
  0.0, 9.208785, 0.0, 0.0, 
  0.0, 0.0, 1.000000, 0.0, 
  -0.850000, 0.0, 0.0, 1.000000;;
	}

// Note: The following matrix will be replaced by DirectX by the equivalent
//       concatenation of each keyframe's scale/rotate/translate values.
Frame Anim_MatrixFrame_Line01 {
	FrameTransformMatrix {
  1.000000, 0.0, 0.0, 0.0, 
  0.0, 1.000000, 0.0, 0.0, 
  0.0, 0.0, 1.000000, 0.0, 
  0.0, 0.0, 0.0, 1.000000;;
	}

sky_brightblue.dds

Material DeviceImage {
 1.000000;1.000000;1.000000;1.000000;;
 3.200000;
 0.000000;0.000000;0.000000;;
 0.000000;0.000000;0.000000;;

 TextureFilename  {
  ":deviceimage";
 }
}

Frame ChamferBox01 {


 FrameTransformMatrix {
  0.871527,0.372206,0.319222,0.000000,-0.239184,0.891003,-0.385881,0.000000,-0.428055,0.259953,0.865560,0.000000,0.000000,0.000000,0.000000,1.000000;;
 }

 Frame {
  

  FrameTransformMatrix {
   1.000000,0.000000,-0.000000,0.000000,0.000000,1.000000,0.000000,0.000000,-0.000000,0.000000,1.000000,0.000000,0.000000,0.000000,0.000000,1.000000;;
  }

Etc. DirectX meshes for WorldView; not sure where they can be obtained from, however.

Which reminds me... there'll be a refresh build supposedly with WinHEC, I hope that one has DCE already activated. From what I have grasped some longer time ago from Chris Andersons blog, they've switched the hard line to DCE sometime ago. Theoretically the WinHEC build should feature it activated. We'll see.

Run DCE start commands, run MIL.BAT, repeat, and click okay on all error msgs.

Slow as hell though, and you need to port the files from 4029 to 4051 first (milcore.dll, sbctl.exe, etc)

23/06/2003  11:56            65,536 microsoft.windows.pplrtc-msgr.dll

19/06/2003  14:19            49,152 microsoft.windows.pplrtc-rtcv1.dll

19/06/2003  17:38          761,856 microsoft.windows.pplrtc1.dll

23/06/2003  11:56          443,392 microsoft.windows.pplrtc2.dll

07/02/2004  13:08        1,209,344 milcore.dll

02/10/2003  00:12          114,688 presentationbuildtasks.dll

02/10/2003  00:11        1,683,456 presentationcore.dll

02/10/2003  00:10          224,768 presentationcore2.dll

02/10/2003  00:11        2,007,040 presentationframework.dll

02/10/2003  01:10        1,027,584 presentationhost.dll

06/02/2004  18:59            4,608 sbctl.exe

02/10/2003  01:11        17,242,112 shell32.dll

14/02/2004  18:56          861,184 shellinterop.dll

Various other things you need as well, but that should get you started.

Hi! Welcome to the forum and thanks for your help!!!!! :woot:

I tried your mil.bat on 4029. What is it supposed to be doing? The only thing that it does here is slowing down the Desktop :(

The DirectX Meshes can be found in shell32.dll :)

Michael

The slow down could be explained that you activated DCE but it chose to run on the software renderer of D3D. I don't know if that's actually possible, but it'd explain the slowness. Afterall, you need a DX9 compliant graphics card. Since the OS is still in alpha, it has highly likely fallback behaviour.

The slow down could be explained that you activated DCE but it chose to run on the software renderer of D3D. I don't know if that's actually possible, but it'd explain the slowness. Afterall, you need a DX9 compliant graphics card. Since the OS is still in alpha, it has highly likely fallback behaviour.

I have a Radeon 9800 Pro, which is a DirectX 9 compatible Card, so this shouldn't be the problem!

Activating DCE also worked by just typing "C:\WINDOWS\I386\SBCtl.exe wmgstart"

I noticed a drop in CPU-activity when moving a window, so I suspect that "C:\WINDOWS\I386\SBCtl.exe wmgstart" has already started DCE :wacko:

Michael

No clue. Not yet a DX9 card here, nor Longhorn installed outside VPC, so I can't test. The easiest way to test would be moving another windows on top and back over another application that has a lot of controls by itself. If DCE works, you should not see any white flashes from redraws.

Well, because MIL.BAT wasn't written by me, it's horribly incorrect and ineffective. Your best bet is to load up Milcore into depends.exe, look for the hooks, and then call them in whatever order you think makes more sense than the one in MIL.BAT (that's what I was doing before I got fed up of the networking bug in 4051).

I haven't tried any of this in 4029, but there shouldn't be any difference in the procedure. Just keep at it, and you should eventually get it. The DLL functions are named pretty descriptively, and when looking through them, and comparing it to MIL.BAT, there were a few functions which I was surprised weren't included by the creator.

But yeah, just try playing around with different functions in MILCore.dll, and eventually you'll find a combination which works :)

As to what the script does, if you grab your windows and move them around VERY fast, you should notice that the edges kinda warp and distort. That's the 'wavy windows' stuff attempting to manifest itself, but failing because of the draw lag. I'm 90% sure that Tom Servo is correct, and it's attempting to do it via software mode. The reason for this is that the hardware accelerated server is not being called via MILCore - again, something which can be sorted out by finding the right sequence of commands.

Well, because MIL.BAT wasn't written by me, it's horribly incorrect and ineffective. Your best bet is to load up Milcore into depends.exe, look for the hooks, and then call them in whatever order you think makes more sense than the one in MIL.BAT (that's what I was doing before I got fed up of the networking bug in 4051).

I haven't tried any of this in 4029, but there shouldn't be any difference in the procedure. Just keep at it, and you should eventually get it. The DLL functions are named pretty descriptively, and when looking through them, and comparing it to MIL.BAT, there were a few functions which I was surprised weren't included by the creator.

But yeah, just try playing around with different functions in MILCore.dll, and eventually you'll find a combination which works :)

As to what the script does, if you grab your windows and move them around VERY fast, you should notice that the edges kinda warp and distort. That's the 'wavy windows' stuff attempting to manifest itself, but failing because of the draw lag. I'm 90% sure that Tom Servo is correct, and it's attempting to do it via software mode. The reason for this is that the hardware accelerated server is not being called via MILCore - again, something which can be sorted out by finding the right sequence of commands.

OK, thanks! :)

I think will be playing around with it a bit!

Michael

Hey tell me

How do you ati guys out there install the drivers for your systems? When i try to install them it says 'SETUP was unable to complete the installation. Try to setup a your display adapter with a standard vga driver before running setup.

Any ideas?

I did get it working ounce with the windows selection and dropdowns working, and stable. The only bug it it isn't very stable, so it's either hardware accelerated? with no dropdowns, sometimes it some windows deforming that could be wavy windows or it just shows does somthing totally random. Its sort of unpredictable at the moment.

ATI hack: you need 4053 for this to work. Get the driver cab for 4053 and overwrite the 4029, then get the ati infs from windows\inf and put them in the right 4029 forlder, the update the driver, thats how I backported the ati drivers to 4029.

Edited by Nanorobot
I did get it working ounce with the windows selection and dropdowns working, and stable. The only bug it it isn't very stable, so it's either hardware accelerated? with no dropdowns, sometimes it some windows deforming that could be wavy windows or it just shows does somthing totally random. Its sort of unpredictable at the moment.

ATI hack: you need 4053 for this to work. Get the driver cab for 4053 and overwrite the 4029, then get the ati infs from windows\inf and put them in the right 4029 forlder, the update the driver, thats how I backported the ati drivers to 4029.

So do you have the dce thing working?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • My ice blue precision 3550 laptop
    • A coalition of publishers sued OpenAI and Microsoft over scraping content without consent by Hamid Ganji Image via Depositphotos.com AI companies often rely on readily available internet content to train their chatbots and provide users with instant answers. This method of AI training is fast and relatively inexpensive, but using a website’s content without permission or compensation is not something publishers like to see, and this is exactly why Microsoft and OpenAI are now being sued. As reported by Bloomberg, a group of publishers that collectively own nearly 400 newspapers has filed a lawsuit against OpenAI and Microsoft. The coalition argues that the two companies scraped their content to build AI chatbots like ChatGPT and Copilot without paying any compensation. The complaint, filed in the U.S. District Court for the Southern District of New York, argues that while AI products have generated billions of dollars in market value using publishers’ work, none of that value has been shared with the publishers. The plaintiffs are seeking statutory damages and injunctive relief for alleged copyright infringement and violations of the Digital Millennium Copyright Act. “Defendants systematically and secretly crawled the Publishers’ websites—including content behind paywalls and other access restrictions—and copied the Publishers’ articles, stories, and other original works onto their own servers without authorization,” the complaint states. The publishers also described the AI boom as a “death knell for local journalism” if AI companies that scrape content for free are not held accountable. Former New Jersey Attorney General Matthew Platkin and his law firm, Platkin LLP, are representing the publishers. “Our models empower innovation, are trained on publicly available data, and are grounded in fair use,” OpenAI spokesperson Drew Pusateri told Bloomberg. This is not the first lawsuit involving the unauthorized use of publishers’ content by AI firms, but it is one of the largest coalitions ever formed against the free use of content by AI chatbots. In 2024, OpenAI and Microsoft also faced a similar lawsuit from eight newspapers that claimed AI products were benefiting from their content without permission.
    • Rufus alternative Ventoy now supports Windows 11's mandatory update, fixes major boot bug by Sayan Sen While Microsoft has its own official Media Creation Tool used for making bootable USB media, there are some popular third-party utilities as well which offer additional options like bypassing system requirements, Microsoft Account creation, and more. One of these is Ventoy, and the software has received its latest update today. In fact, the app actually got a slew of updates over the last couple of days, three version releases in total, to be specific. The first release, version 1.1.13, was pulled as there was some unspecified error in the update, and as such, the corrected version 1.1.14 was pushed out. Following that on very short notice, 1.1.15 was published as well. For those unfamiliar, Ventoy is an open-source utility that lets users create a bootable USB drive once and then simply copy ISO, WIM, IMG, VHD, or EFI files onto it without repeatedly formatting the drive. It supports both legacy BIOS and UEFI boot modes, Secure Boot, and a wide range of operating systems, making it one of the most versatile tools in the category. The biggest change in version 1.1.14 is an updated Secure Boot shim file aimed at resolving the UEFI CA 2023 issue, which is basically a compatibility problem that has affected Secure Boot environments on some systems. If you recall, we reported about severe boot issues on HP devices following the release of updated Secure Boot 2023 keys. For anyone who may not be aware, back in early 2024, Microsoft announced that it was updating Secure Boot keys as they were going to become 15 years old in 2026, which is also when they are set to expire. As such, the new 2023 certificates have been rolling out with the newest Windows 11 updates. Updated boot manager and Secure Boot certificates are crucial for protection against malware like bootkits. These are mandatory updates. Alongside that, the VentoyPlugson graphical plugin configurator was updated in sync with the release. The update also introduces a new VTOY_SECURE_BOOT_POLICY option within the Global Control plugin, giving users more flexibility in managing Secure Boot behavior. Ventoy has also received a fix for a startup issue when Secure Boot was disabled. Microsoft does officially allow users to boot systems without Secure Boot as long as the PC is Secure Boot capable. The full changelog is given below: Update secure boot shim file to solve the UEFI CA 2023 issue. The new release use a new CA, so you need to enroll the new key for the first boot time. VentoyPlugson update synchronously. Global control plugin add a VTOY_SECURE_BOOT_POLICY option. Fix the boot issue when Secure Boot is disabled in the UEFI firmware. You can download the latest version of the app here on Ventoy's official GitHub repo or from Neowin software stories.
  • Recent Achievements

    • Rookie
      krychek57 went up a rank
      Rookie
    • Grand Master
      Jaybonaut went up a rank
      Grand Master
    • One Year In
      Philsl earned a badge
      One Year In
    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      441
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      134
    4. 4
      Michael Scrip
      78
    5. 5
      Xenon
      77
  • Tell a friend

    Love Neowin? Tell a friend!