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

    • Windows ME was worse.
    • Dude, im talking about simply disable it from settings app. Because of the eu regulation, you could disable it here for years.
    • One big question about Mars was answered thanks to Einstein's 100 year old theory by Sayan Sen Image via DepositPhotos Scientists at the U.S. National Institute of Standards and Technology (NIST) have calculated how time passes on Mars compared with Earth, adding detail to how timekeeping would need to work beyond Earth’s orbit. The study, published in The Astronomical Journal, found that clocks on Mars run an average of 477 microseconds, or millionths of a second, faster per day than clocks on Earth. A microsecond is one millionth of a second, a very small unit used in precise scientific timing systems such as atomic clocks, which measure time using consistent atomic behavior. This difference is not constant. Because Mars moves around the Sun in a non-circular path (an eccentric orbit, meaning its distance from the Sun changes over time instead of staying fixed) and is affected by gravity from other bodies, the daily difference can vary by as much as 226 microseconds over a Martian year. The study also identifies smaller repeating changes of about 40 microseconds per day linked to synodic cycles (repeating periods that describe how planets line up with each other as they orbit the Sun from different positions). These longer patterns affect how time differences slowly rise and fall. To make these estimates, researchers compared Mars with Earth and the Moon. The work looks at relativistic proper time (the time actually measured by a clock depending on its speed and the strength of gravity where it is located, as described in Einstein’s relativity). This shows that each world has its own slightly different “rate” of time. This becomes more important as space missions expand into cislunar space (the region between Earth and the Moon) and toward Mars. On Earth, time systems rely on atomic clocks and satellites, which stay closely synchronized for navigation and communication. The study is based on Albert Einstein’s theory of relativity, which shows that time is affected by gravity and motion. Stronger gravity makes clocks run slower, while weaker gravity makes them run faster. “The time is just right for the Moon and Mars,” said NIST physicist Bijunath Patla. “This is the closest we have been to realizing the science fiction vision of expanding across the solar system.” A day on Mars is about 40 minutes longer than on Earth, and a Martian year lasts 687 Earth days. But the main question is not just about days and years, but how fast time itself passes. An atomic clock placed on Mars would function normally, but compared with one on Earth, the two would slowly drift apart due to differences in gravity and motion. This requires careful calculation of what is similar to a time-zone difference across planets. Researchers modeled Mars using a reference surface and included gravitational effects from the Sun, Earth, the Moon, and other planets. This includes a multi-body gravitational system (often described as a three-body or four-body problem, where predicting motion becomes difficult because multiple large objects all pull on each other at the same time through gravity). Mars also follows a Keplerian orbit (an idealized elliptical orbit based on simple gravitational laws that assume smooth motion, before adding real-world disturbances from other bodies). In addition, the researchers accounted for solar tides (small changes in gravitational force caused by the Sun that slightly distort planetary motion and timing, especially in systems involving Earth and the Moon). These combined effects are described as relativistic proper-time offsets (small but measurable differences in elapsed time between locations caused by gravity and motion), which must be included when comparing clocks across planets. “But for Mars, that’s not the case. Its distance from the Sun and its eccentric orbit make the variations in time larger. A three-body problem is extremely complicated. Now we’re dealing with four: the Sun, Earth, the Moon and Mars,” Patla explained. “The heavy lifting was more challenging than I initially thought.” Although the differences are extremely small, they matter for navigation and communication systems that depend on precise timing. Even modern networks on Earth, such as mobile systems, rely on timing accuracy at very small fractions of a second. Communication between Earth and Mars currently takes about four to 24 minutes or more depending on planetary positions, meaning signals are not real-time. A shared and accurate time system could help future missions reduce confusion in navigation and data exchange. “If you get synchronization, it will be almost like real-time communication without any loss of information. You don’t have to wait to see what happens,” Patla said. Researchers note that fully developed interplanetary communication networks are still far in the future. However, understanding how time behaves across planets helps prepare for those systems. “It may be decades before the surface of Mars is covered by the tracks of wandering rovers, but it is useful now to study the issues involved in establishing navigation systems on other planets and moons,” said Neil Ashby. “Like current global navigation systems like GPS, these systems will depend on accurate clocks, and the effects on clock rates can be analyzed with the help of Einstein’s general theory of relativity.” Patla added that the results also help improve understanding of time itself under relativity. “It's good to know for the first time what is happening on Mars timewise. Nobody knew that before. It improves our knowledge of the theory itself, the theory of how clocks tick and relativity,” he said. Source: NIST, IOPscience This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • TeraCopy 4.0 Build 26 by Razvan Serea TeraCopy is a compact program designed to copy and move files at the maximum possible speed, also providing you with a lot of features. Copy files faster. TeraCopy uses dynamically adjusted buffers to reduce seek times. Asynchronous copy speeds up file transfer between two physical hard drives. Pause and resume transfers. Pause copy process at any time to free up system resources and continue with a single click. Error recovery. In case of copy error, TeraCopy will try several times and in the worse case just skips the file, not terminating the entire transfer. Interactive file list. TeraCopy shows failed file transfers and lets you fix the problem and recopy only problem files. Shell integration. TeraCopy can completely replace Explorer copy and move functions, allowing you work with files as usual. TeraCopy is free for non-commercial use only. For commercial use you need to buy a license. The paid version of the program includes the following features: Copy/move to your favorite folders. Save reports as HTML and CSV files. Select files with the same extension/folder. Remove the selected files from the copy queue. TeraCopy 4.0 Build 26 changelog: Added support for receiving files via the LocalSend protocol. Improved exception handling and automated bug report upload. Fixed several minor bugs and small memory leaks. Build 26 (June 24) Fixed a rare exception when a transfer completed. Features added since version 3.17: Enhanced speed graph. New multi-threaded copy engine. Support for copying to multiple targets. Queue system for managing multiple copy operations. Support for receiving files via the LocalSend protocol. TeraCopy entry in the modern Windows Explorer context menu. Integrated toolbar in the title bar. Why receive LocalSend transfers with TeraCopy? Handle file conflicts: Skip, overwrite, or rename files when a file with the same name already exists. LocalSend always creates another copy, which can waste time and disk space, especially when resuming an interrupted transfer. Filter unwanted files: Apply ignore lists or remove files manually before accepting a transfer, so unnecessary files are not downloaded. Better performance on fast networks: In tests over a 10 Gbps connection, TeraCopy received files several times faster than the standard LocalSend app on Windows. Download: TeraCopy 4.0 Build 26 | 14.5 MB (Freeware, paid upgrade available) View: TeraCopy Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Briefly used Turbo Pascal (and Turbo C++) in 97 and soon after that I bought PC magazine that included a full version of Delphi 2. I still use Delphi today, some 29 years later.
  • Recent Achievements

    • 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
    • One Month Later
      D0nn13 earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      453
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      124
    4. 4
      Michael Scrip
      78
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!