Question regarding .bat and .exe files?

Question

I'm on a user-restricted account at school that doesn't allow me to check my email, and I'd like to change that. I know some other workarounds for cmd, but most of them depend on batch or executable files.
And the school computer doesn't allow me to save or run either of those, so I'd wondering, if get cmd or one of my batch files to cmd on a flashdrive and bring it to the school computer, will it run it? Thanks again!
BTW- I know simply unlocking CMD won;t let me unblock my emazil website, but it;'s the first step.

Answer 1

The restrictions was there for a reason. Although there are other applications and techniques that you can employ to let you check your e-mail, bottom line is you can't because you have a user-restricted account. Unless you know the password of one of the Administrator account (which you don't) you can run any applications with an elevated account using "Run As" admin account.

Answer 2

running commands in the command prompt on a non-admin account has no effect unless you can run them with elevated rights... whether you run them directly from the prompt or through batch files makes no difference. Any modifications you would need to make to get unrestricted access will require elevated rights meaning you would need an admin password. When I was in school, the admin password was simply 1administrator1, but it's likely more cryptic now if not using multi-factor authentication. At the very least you can try accessing your email through a proxy server (or disable the proxy server if the site blocking is done by using one) but most of those are probably blocked as well.

Answer 3

Basically a .COM file was a literal blob of 8086 code (that is, 16-bit x86). .com files to be loaded at a fixed address, and the loader would jump straight to the first byte of its address. It’s always limited in size.



But an .EXE file has contained more header information. So it has required structures for things like dynamic linking, where code from a DLL can be patched into the .EXE's memory space at load time.. It originally comes from DOS, but it's today used in Windows