Discussion in 'Windows 10' started by RanCorX2, Feb 20, 2018.
Or even what commands an exe sends out, a sniifer.
You can't "sniff exe commands" like a network packet sniffer.In very simple terms when an exe is run it loads itself into the memory & execute machine language instructions it contained.Only way to know what exactly it is doing is by running it through a disassembler which converts machine language into assembly language which you can then try to analyze.
Thats ruled that out then, thanks whitestar
couple of issues remain for bluetooth (3rd party stack driver installation) so am working on correcting that atm. causes explorer to refresh randomly at certain times referencing bluetoothapis.dll as faulting module.
windows driver seems to work fine.
printer - check
xbox one controller - check
xbox 30 controller - check
usb hard drives - check
mouse - check
keyboard usb / bt - check
scanners - check
usb sd card readers - check
audio - check
usb wifi - check
lan - check
gpu installation - check
After stage 5 was unable to boot with spaceport.sys Status: 0xc000000f error.
LTSB RS1 UEFI NVME boot
@WindR will fix that.
anyone using uefi & nvme should avoid for now.
regarding bluetooth, managed to remove the bt telemetry agent, BthTelemetry.dll, deleting it breaks bluetooth, can't add devices or remove existing ones.
however, creating a dummy dll with the same name makes bluetooth work.
i suppose reverting back to older ms bt 4.x drivers might allow removal of the dll but i haven't tried that........................yet.
going to do a seperate version for users with the latest hardware, the other one will be for legacy users like myself who don't use uefi, nvme, nvdimm, storage spaces and anything else "new" that is system critical to said hardware.
Please keep UEFI in legacy version. There are computers from 2008 that have UEFI!
i removed those things because i was removing all the new stuff, when users report "critical" stuff broken i can add it back as i'll know what it was.
users on standard hardware, sata + ssd should have no issues booting. you don't have to roll your pretend eyes....
experimentation requires testing and "useful" feedback.
You need to login to view this posts content.
for RanCorX2 thanks for information, I remember this dude since 2004 on Neowin when he trying change things in Windows XP
still working on it, adding rs5 & rs6 support via testing some insider builds to stay updated.
i've added classic shell to the project to cut out installing that, placed it in windows folder as well as saved custom settings + 3rd party windows 7 menu skin & taskbar skin for best windows 7 look.
added back all the old windows help files to replace the ones that point to online help.
trying to make the project as complete as possible without the need to install extra 3rd party software.
good news dude, so waiting something for make test ok
yes open shell is what i'm using, recently switched to it from cs. i'm aware of the new codename but i like to think of it as rs6. (not a fan of the new codename as it sounds like a strain of flu)
"Oh, please help, I think my PC has catched a bad case of 19H1!" LOL, indeed.
fear not slimmers, still working no it, rs5 support is done, not bothering with 6 yet as it's too early, i tried the latest build and it's not much different to 5.
just sorting out a few issues with ie and speech recognition.
fixed all my batches so that they all work as intended (still have some disabled lines left in for maybe future use, so errors can be safely ignored as they are just saying the command is invalid)
sihost is even more integrated in the shell on rs5 so i had to do a seperate file replacing batch for rs5+, can no longer cripple-ish it (i.e. remove window management)
replacing sihost with older version on rs5 causes flashing desktop on logon.
that shouldn't happen if you use "rem"
^ thanks for tip, completely forgot about that dos command.