Tripredacus

What motherboard is it?

I think I've been to East Texas. Does Houston count?

It seems to not be a file size limit relating to DOS, but a size limit set by the application itself. I have given up trying to determine how to increase it. Instead I have been figuring out how the data is stored and I have been making some progress in that. The data is stored in fixed sized regions, so replacing the "deleted" data may end up being easier than trying to figure out how to make the flat file database larger. I may end up posting a topic into the programming section later about it.

I've run into what is either a file size or address limit with a game that I often use. I had run into this issue many years ago with the same program using actual DOS, but I had figured it was caused by some other limit. I had been running the program again, under that impression, and did not run into the issue again until now. The program allows for entering new data into it, and it gets saved into a file. The size of the original file, and the modified file is the same. DOS reports that size as 50,991. The program allows for the removal of data, however I have found that it doesn't remove it from the file, rather it marks it as deleted. So there is a finite amount of additions that can be made, and previous data cannot be removed easily. There is no EOF marker that I can determine. I have tried to increase the size of the null portion at the end of the file, but the program just will overwrite the last section anytime new data is input. There appears to be some ID value that is stored, because when the data is overwritten, ghost entries appear in the data viewer. I tried to search for what the possible limitation could be caused by, but not able to find anything helpful. Making a larger data file does not effect the program's operation, so it does not appear to be a filesize limitation. Here are the details. Main application was compiled with IBM BASIC 2.0. It uses BASRUN20.exe for runtime but no library is present. No source is available. Program currently running in DOSBox with default config. DOSBox has upper memory set at 63Kb as seen in MEM command. Data range start of last entry in data file is c6e9 / 50921. Maximum position of the original file, as seen in a hex editor is c72e / 50990. Is there some address limit that matches up with this behaviour? If it is related to the upper memory size, how can I increase this?

A program that I wrote for Windows 7, that works in 8.1 and all versions of Windows 10 up to 1809, does not work in 1903. The one thing that is changed is running a .cmd file, and I am supposing what the "context" of where the file is run. This seems to be correct, but others can test if they want. In Windows 7 through Windows 10 1809, executing a CMD would run relative to the CMD or call origin to the cmd.exe. Example. On the desktop is a .exe and a folder. Inside of the folder there is a .cmd file. From the compiled .exe, execute a call such as: "cmd /c c:\users\Administrator\desktop\folder\batch.cmd" and inside of that .cmd is "cd folder." This would have to be done because the source .exe is sitting on the desktop, and you would have to CD into the folder to get to those files. A person writing batch would do this for situations where abolute paths do not work (because programs inside required relative paths, or other situations). In Windows 10 1903, the .cmd is run relative to the default CMD path? Example: same as above, but it will fail. Running manually from default CMD context (Win+R cmd.exe) which will default the path to C:\users\Administrator. Running the absolute path to the .cmd will result in the error of unable to find the folder you CD to. It is because now a direct call using CMD will be running in the context of C:\Users\Administrator, rather than C:\Users\Administrator\Desktop, where the initiator (EXE) resides or whatever the start path in the CMD is at the time of manual testing. If the location in CMD is C:\Users\Administrator, then the .cmd file needs to have CD Desktop\folder and it will work. Some small change but it delayed rollout of 1903 for some systems, because batch pathing behavior apparently changed. I hope I explained it properly. I can do a step-by-step breakdown tomorrow if someone doesn't figure out what I'm saying.

Welcome to the MSFN!

I have found it. The Tetris that was in the Entertainment Pack and the Best of Pack is not the original Tetris. It is a port of Mirrorsoft's DOS version, which was the first official release of the game on PC, the first overall being on micros. The info refers to it as Tetris 2.00. and is official insofar that Mirrorsoft sub-licensed the rights to Microsoft, who then put their copyright on it as you can see here: https://harddrop.com/wiki/File:Windtetrisstart.png

Well I don't have that disk, and the Wikipedia page doesn't help. In fact, it cites itself which I'm pretty sure is not how that's supposed to work. In any case, there are no details as to what Tetris that is, either.

I don't think so because you can't open the Emoji Panel from the lock screen. It seems like the Windows key gets disabled there.

It is also not the newest official Tetris for Windows either.

The Lock Screen is supposed to be designed in such a way that you can't do anything from it (that matters) except for logging into or changing the user account, shutdown/restart, turn on accessibility options, connect to wireless network or enable Airplane Mode. At least that is what we are promised. Quite by accident (and of course, I can't recreate it on purpose) I was able to open the Emoji Panel while in the Lock Screen. Through some miracle of timing, Windows had processed the command to open the Emoji Panel (Windows Key + ; /semicolon) and Lock the station (Windows Key + L) in some order which presented a usable Emoji Panel on top of the Lock Screen. Normally, you cannot access the Emoji Panel after locking the system, and if you open it before locking, it will be hidden. Fortunately, there does not seem to be any entry point into anything from the Emoji Panel, as it is not modal. It leads me to believe that it would be possible to (somehow) be able to use other keyboard shortcuts to get things to appear on the Lock Screen when they shouldn't.

I can't easily find which Tetris is actually included in that pack.

There is not much control available as an admin of a desktop host. You can only have the options to authenticate or to not. There does not appear to be a way to have both. Anon or Guest access is limited, and while it should allow access to shares without a prompt, the client only will get read permissions. https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-access-sharing-and-security-model-for-local-accounts Microsoft has nerfed the classic Guest ability of past OSes This has nothing to do with getting the other computers to see that the new computer exists.

Presuming the computers know each other's host names, and all computer are logged in using local account... You should be able to add users from the other computers to the share permissions on the host. They user ComputerName\UserAccount format. Additionally, all computers can be within the same workgroup, which may help. Ideally, you want to create a user account on the host computer, with a password, and then use those credentials to log into the share. If you choose to remember the credentials, it should not prompt you for them again. Outside of AD/NN, this is what I do. Which basically what I am recommending is NOT what you are asking. The way to get what you are asking is to enable Guest access, which would need to be done to all hosts. This is a terrible idea normally, and certainly should not be done on any systems that are moved between networks.

Is this for home or business use? If in an enterprise environment, I would query the asset management system for the old computer name and then use powershell to rename the computer. No entry into WinPE needed.

I will use the other five connected directly, but the Micron Storage Executive had no issue with the first disk being on a USB adapter. After noticing Testdisk was still trying to do something after about 20 hours, I decided to kill that and install the Micron software. It does actually use an image (a crossed out eye) to signify that TCG is enabled, but the software does not make it obvious. It was only after getting the debug info for the disk, and the log file says "TCG Status= Activated" was I able to find Micron's guide showing that image. And the PSID Revert worked fine. Afterwards I had to remove readonly attribute from the disk using Diskpart because Disk Management and Diskpart showed an error about the disk being write protected. Then I was able to format the disk fine. The Micron PDF is here. Page 20 shows the picture of what the icon looks like.

I have been sent six Micron SSDs to see if there is any way to save them. They are not covered under warranty and *should* have no data to recover. I have started with one of them, everything seems ok except that anything accessing the disk is very slow, and a partition cannot be created. It appears in Device Manager! It is MICRON_M 510DC_MTFSSAK480 SCSI Disk Device OH, perhaps important information ahead: this disk is in a SATA to USB 3.0 enclosure, connected to USB 3.0 port. Disk Management shows it ok, but there is a red mark on it. Actual size 480 GB seems to be an odd one to me... Crystal Disk Info seems to think everything is fine. Notice the power on count. These disks are not "used" ... and should be "new" but they were found during an acquisition with no asset information. This takes a long time, entire minutes to complete commands such as list disk and sel disk 1 and detail disk, however "clean" seemed to go through quite quickly. Alas, here there is an error trying to create a partition. Here are the things found in Event Viewer: The IO operation at logical block address 0x0 for Disk 1 (PDO name: \Device\00000064) was retried. VDS fails to write boot code on a disk during clean operation. Error code: 800701E3@02070008 The IO operation at logical block address 0x0 for Disk 1 (PDO name: \Device\00000064) failed due to a hardware error. Then I have this from TestDisk running, on partition type "None" and Analyse mode. Seems to be taking its time. If there is any particular tool I can run to get an actual error out of these things, it would be nice. I still have some other things I can try, but being very slow means I have time to post a thread and perhaps go home and take a nap.

I run into many different configurations and only have one process across all images. And that is accomplished by making sure only the disk or vdisk is visible during imaging process. This means not creating or having attached disks or controllers where the OS is not present until after imaging. If a system needs to have a large array built, it is built before imaging and the controller is disconnected until after. A Pro to this is the ability to have one process for tens of different configurations and hundreds of different images. A con is that disk/volume formatting is done manually after imaging process, but before quality phase. This type of process may only work properly in an environment where imaging is done in a specific area, but not work well in corporations that like to do the imaging after physical install in offices, etc. Another way to handle this specific scenario of yours would be to build a custom solution. Where your WinPE would boot to a selection menu of some sort. Present option 1 (1 disk) or option 2 (2+ disks) then execute the appropriate command for each. You would use setup.exe /unattend option and point to either XML file kept in root or wherever. PS: you would get an error if you specify Disk numbers that do not exist.

Add the local account from "This PC" to the share permissions of DESKTOP-ICEONI7. That is the ideal way without enabling guest access on the network. Otherwise, it may be that the new computer has a different network profile set, such as Public instead of Home.

I have installed them onto three computers so far, but have not noticed anything. All three were having issues reading certificates from various things, but the updates did not solve those problems. What are some known situations where you would need these? Are there any websites that are known to require these types of certificates? Something to test against?

There can be various reasons for this, but I would presume that said OEMs are trying to square peg a round hole in their market share. Microsoft makes builds for all sorts of different classes of hardware. If an OEM were to want to create a device that had a small amount of storage, they should be using one of the SKUs specifically designed for such devices, and not be using one of the desktop products. Licensing and product knowledge are things that you would think a company would know, but usually design decisions are not made from the bottom up. Meaning, those who do work with the software and hardware directly are not the ones who would recommend product configurations for their company to sell. The other issue is that most people are willing to just do as directed in order to not cause a fuss or shine a light onto themselves. So bad configurations end up getting into the marketplace because the guy who thought it was dumb just did it anyways. Then, of course, there is the other thing: No one really cares about anything except making a quick buck.

Both methods are doing the same thing. Mine is using AutoIT to read directly from the namespace, while his is reading the output of a WMIC query sent to text file. The registry read doesn't work in Win7 because those keys do not exist. I did a check on my system, and the UUID is not stored in the registry anywhere. There are some situations where you would want to know this information. I personally use it myself for generating hardware specific hashes to things. I do know some other software will use it. Typically you would only need to know it in a situation where a program is not working as desired, which is usually caused by malformed or default UUIDs. Then you would need to know the UUID in order to verify on your own records or to complain to the hardware manufacturer.

Your example is doing the same thing as mine, except using CMD and creating a text file. Mine would only be useful if you wanted to show that data on the Hardware Info MsgBox.

What is the make and model of the board?