There are billions of winsock tutorials out there... my advice is to search for +win32 +"winsock tutorial" on google. When I designed a simple chat program I did it by barely modifying a skeleton client/server example that was already out there. (No, this was not a school project...
Ok, I feel like an idiot... I knew that, but I guess I didn't really think ;-) Ad, you are quite right... 09 is the same as 09h... wow I feel like a tard :-)
--------
It is an honor to recieve an honest reply. (Prov 24:26)
It's been a long time since I've done ASM programming in dos, but is the interrupt you're looking for 09, or 09h? You could try that.
--------
It is an honor to recieve an honest reply. (Prov 24:26)
Your problem is that you forgot to null-terminate the string.
change the line:
message db "HelloWorld!$"
to:
message db "HelloWorld!",0
...and you should be fine.
--------
It is an honor to recieve an honest reply. (Prov 24:26)
Lionelhill's probably right: you'd probably best post your code for quickest response.
--------
It is an honor to recieve an honest reply. (Prov 24:26)
You could do this if you wrote a program that used your modem. Many modems support more than just data connections, you know. So I suppose you'd have to have the RIGHT modem for the job, but if you did it'd be pretty simple to write a program that would play a recording over the phone line...
I'd personally recommend ClarkConnect... It's made to be a firewall/router distro, but it doesn't have to be. The web administration for it is INCREDIBLE. It'll let you access the ssh on the box with any browser on a computer with a JVM, update your packages, administrate e-mail/web server...
Your program needs to send a command over the network? If you're using tcp/ip (internet protocol) and windows (I remember you were talking about win32 assembler) then you should check out the winsock api. The standard winsock documentation was enough info for me to make a small encrypted chat...
There are tools out there (NTFSDOS comes to mind) that will let you modify an ntfs partition from dos, but they may be read-only... not sure. At any rate, you'll need to find the registry files which (as adholioshake mentioned) are different for different versions of windows. If you can boot...
I absolutely LOVE Crimson editor, but I don't think it'll highlight errors :-(.
It does great at everything else a programmer needs, though, including backups. I use it for all my php, vhdl, and assembler.
--------
It is an honor to recieve an honest reply. (Prov 24:26)
I know that if you use VESA there's an interrupt you can call to get the base address for the SVGA memory... last I remember, though, I tried it out when I was doing dos 32bit protected mode assembler, and found that the memory mapping scheme for even a simple 800x600 16bit was DIFFICULT to work...
I wrote up some sample code to try a few things out... it seems to work fine for me. The following code compiles just fine:
--Declare all your libraries, etc--
--SmallerItem is the item you will instantiate as a component.
--In this case I just used 3 downto 0 as its size.
entity SmallerItem...
1. For a great reference guide and some examples, go to
http://www.acc-eda.com/vhdlref/index.html
2. You'll find loads of useful links at
http://www.vhdl.org/
3. For good examples, sample code, reference, and downloads check out
http://www.vhdlbuilder.com/
4. Yet...
Logitech1234 could be right. It's pretty hard to put your network card into promiscuous mode without meaning to, so either you or someone else probably did it. You may have done it accidentally by playing with packet sniffers and other various networking tools.
The other possibility is that...
There are lots of people that can help with this one... but first I want to make sure you know to ask this type of question in the linux (client) forums rather than the (server) one. No huge deal, but it keeps things more organized.
As far as volume goes.. are you running XFree86? If you are...
You could assign w_clk to a device that takes a clock input, and have it output a high every clock pulse... It's pretty much just tricking the vhdl compiler. It doesn't want the clock pulse used for non-clock devices, but you can have a device pretty much just echo the clock pulse it recieves...
I see no flaws in the idea (raid1, etc). With just a little advice and training from someone who knows what they're doing you'd be well on your way.
It's worth the time investment- who knows where else the knowledge will be useful, after all.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.