Your stuck on a deserted island, It has internet infrastructure but the only computer left on the island is an old emachine running windows 95, You will have to write your own drivers to use the network hardware, And if you don't have a compiler you will have to write your own compiler from scratch for windows 95.
this is your only way off the island, the only way to contact the outside world.
Will you survive?
Other urls found in this thread:
youtube.com
youtu.be
twitter.com
>Will you survive?
Yes
>old emachine
NEVER OBSOLETE !
>you don't have a compiler
How will you compile your compiler then?
Anyway, I used to tinker with C++ in Visual Studio on Windows 95 in my youth, and since then I've gained a fair understanding of both kernel programming and networks, so I think I will survive. Don't need to implement a feature complete network stack, just need to hack something together that can (mis)use whatever network equipment there is on the island that is connected to somewhere I suppose?
but.....I need man pages user.
kek'd hard.
I'll just live on the island, seems pretty comfy
You can also just choose to stay on the island and play solitare offline on windows 95 or maybe use the text editor to write a novel or a suicide note.
you will have to write your network program in C but you only have what comes availible with stock windows 95.
you also have a windows 95 restore disc and a copy of doom.
Copy of DOOM?
I'm fine with that.
>you will have to write your network program in C
No, you don't.
>copy of doom.
Well, Doom already had networked multiplayer over serial. I guess I don't have to write anything complex at all, I can just use the serial port.
you'll have to make your own hardware to connect because their are no ethernet ports.
how will you write your network program? in assembly?
Visual Basic and some assembly
There is the serial port, which is by definition network hardware. That's how people used to connect to modems in the older days.
>How will you compile your compiler then?
You write the compiler in bytecode
Bytecode will only run on a virtual machine.
You're running windows 95C which has java preinstalled.
No :(
Just connect using the wireless networks manager, kek
>And if you don't have a compiler you will have to write your own compiler from scratch for windows 95.
Well do we or don't we?
>Will you survive?
Unlikely. Writing drivers without documentation? Good chance of breaking something.
emachines systems never shipped with win95 dipshit
Erm. Gonna need specs on that network card and valid IP configuration information ...
What network card is installed?
What kind of network infrastructure?
Is it documented?
What development tools are available on the system?
break the computer apart, use wood and stones to forge the metal of the computer into a knife, use the knife to construct an outrigged kayak, then set out to sea
Brilliant.
Well I'm still better off than if I had a computer booting to grub recovery mode.
Unless you know the strict protocols, you're not contacting anybody. You'd have better chance of salvaging the machine for parts and making a ham radio.
Doom? I'd just play that until I die. Life well lived.
Sounds like Australia. So no different to my current predicament.
>95
>2000/ME icons
How about we say that the computer is a Toshiba Satellite 105cs, and for network cards you have a Conexant 56k modem card and a 3Com 10/100 Ethernet card model number 3CCFE575CT-D. Both PCMCIA cards. And of course the computer has a serial port as well.
(Arbitrary choice of computer and network cards because I happen to have one right here.)
Do we have access to documentation for the appropriate Windows driver interfaces and network interface?
uh.
uuuuh
jam a network cable into the modem card's phone port.
you can make it fit
That would depend if such material was shipped with any copy of Windows 95.
Salvage metal from computer to make a fork.
Jam fork in electrical outlet
Win95. Never again.
winrar
there's not enough copper in a computer to make an antenna worth any damn
>Your stuck on a deserted island, It has internet infrastructure but the only computer left on the island is an old emachine running windows 95, You will have to write your own drivers to use the network hardware, And if you don't have a compiler you will have to write your own compiler from scratch for windows 95.
Oh, so you mean hell then.
Sure, if you don't know how to use it.
>Jasc Paint Shop
my god the nostalgia
The only way a person could do this, assuming there is no documentation or compiler included in the operating system is to do it the hard way around my directly accessing and writing memory via a glitch.
Basically you're doing something like this:
youtube.com
I would be dead, as would 99.9999% of everyone else. Maybe like 3 people in the whole world could have done this once upon time, and I doubt they remember how to now.
Well, was it or not? You're gay, OP.
RIP me
Windows 95 comes with basic network drivers installed for telnet use.
I'll connect to a BBS and leave a message asking for help. Now if I can only remember the address for one of them. Surely at least one will be buried somewhere in the help files for Win 95.
Does doom come with the level editor? This is important.
>years of a great, free image editor
>suddenly not free
It was an end of an era.
You can write object code by hand in a hex edittor.
Dos came with a hex edittor. I'm betting windows 95 did too since it was made on top of dos.
Use the hex edittor to create a simple assembler IF you had intel 8086 documentation.. yeah fuck it. it's impossible
>emachine running windows 95
emachine was founded in 1998
why can't I just go on Facebook and keep saying Obama sux until the CIA comes and gets me
I think its impossible to contact the outer world given the conditions. If it had linux it would be a completely different situation.
The problem is not having a compiler.
> Your stuck
Use proper grammar you fucking retard.
Pretty sure old versions of Windows came with DEBUG.COM, which included an assembler. I remember writing some small programs using it when I was younger.
That laptop has a microphone and a speaker. You have said I have a modem and an ethernet card, so that means there is some kind of wired connection.
First thing you do is record an emergency message requesting help.
Then you splice the network cable into the audio output of the laptop. Then you set the laptop to play back your message through the speaker over and over.
Then you hope someone out there on the other end will notice this pattern in the noise of the connection and try to figure out what it is.
That's the best I've got.
Could this actually work??
>And if you don't have a compiler you will have to write your own compiler from scratch
Or I can just make everything in pure assembly and save some time to find resources.
It's a long shot but it isn't impossible.
Without documentation or proper development tools there wouldn't be much that I could do as far as driver development goes.
But I have a really retarded idea; functional internet infrastructure implies there are other functional computers running the show to manage and facilitate access, if that infrastructure is ancient like the shitbox I'm stuck with, there's a chance the local internet/telecom provider is probably running a Unix box or two, more than likely made by Sun, and owing to their status as the backbone of the dotcom boom, Solaris has shipped internet-ready since at least 7, maybe even before.
Assuming they haven't cleaned up the default installation image, I can wire up the laptop to the serial port and fire up HyperTerminal and attempt to send for help using a mail client, or even fire up the shitty bundled Java browser if there's a working monitor/keyboard/mouse console setup in the datacenter.
no you write it in another lang to initially bootstrap it.
>you must upgrade to win98se before they come and save you
Great, let's write in qbasic
>writing a network driver with no hardware documentation
safe to say, everyone would be fucked.
