Assembly line scheduling using dynamic programing technique?
402530
Is this academic or ral life problem?
406314
If you know Java, it is not hard to write code to do such task, it might be tedious though.\nIf you don't, Ms excel could handle the job too with reasonable time and effort.
897648
Are you asking for someone to develop this routine for you? If so, I suggest that you post your request on a Windows programmers' forum. Try the link below and see if that helps.
410767
This is a bit difficult question cause it takes lots of factors like how many resources you have (or going to allocate for the project). Do you have a clearly defined scope of work?? System Design??? if you have answers for these then lets break to project in to phases like  feasibility study, requirement gathering, analysis, design, coding and implementation. Each phase break it in to smaller tasks like getting approvals, visiting different locations etc. \n\nNow estimate number of days your resources going to spend on each task depending on the level of experiance the resources have. Here you need consider their previous experience and keep gaps for paper work and other manual processors.\n\nOnce you arrive on total number of days, then it is easy, you calculate what is your man day cost and add your profit margin. Then multiple Man Days * charge per day, that is the price estimation and number of days is the time estimation. Make sure you have buffers in case of something goes wrong in a phase. Size of the buffer needs to justify and realistic.
563755
you can use the Intel 8-bit assembly language, or C. You can probably find a free compiler for the assembly easily (if not, I think I still have it). For C, the compiler I recommend is Keil (www.keil.com). After that you need to load the software into the micro, or external RAM. Some support serial download through the serial port, but if not, you need a "burner" to load it.
1014632
chigidem, armen jan. :-p\n\nThis is why I've created my own language and compiling system. Sure, it took a TON of work at first... but in the end, I ended up doing menial tasks in seconds instead of minutes or hours. :-p
148920
UMC, Uniform Machinacal Code
892858
Not anyone, but someone who know PLC's and SCADA can teach you. I can't on this forum, it would be too lengthy.
1115832
The programming cycle\nThis can be represented as in the following cycle:\n\nWrite program \nCompile \nAsk question \nGet answer \nRestart cycle.
137074
the book published by Andrew S. Tanenbaum named: Computer Networks, Fourth Edition  contains in a very detailed level a C implementation of sliding windows operations.\n\nIn my opinion, the best available
215946
You're probably looking for manufacturing related software which is able to report on any trouble or disaster occuring in the shopfloor or main plant. \n\nCheck out http://www.wareprise.com/content/manufacturing-software.html
463145
binary generation or backtracking techniques
188400
best I could find for you (and me as I am in the midst of working on own company issues):\nwww.tradedynamics.com/docs/pdf/sclm_showcase.pdf
199601
An assembler is a computer program for translating assembly language — essentially, a mnemonic representation of machine language — into object code. \n\nA cross assembler  produces code for one type of processor, but runs on another. The computational step where an assembler is run is known as assembly time.
350187
Monthly statement generation.
764217
There has always been debate over the usefulness and performance of assembly language relative to high-level languages, though this gets less attention today. Assembly language has specific niche uses where it is important; see below. But in general, modern optimizing compilers are claimed to render high-level languages into code that runs at least as fast as hand-written assembly, despite some counter-examples that can be created. The complexity of modern processors makes effective hand-optimization increasingly difficult. Moreover, and to the dismay of efficiency lovers, increasing processor performance has meant that most CPUs sit idle most of the time, with delays caused by predictable bottlenecks such as I/O operations and paging. This has made raw code execution speed a non-issue for most programmers (hence the increasing use of interpreted languages without apparent performance impact).\n\nThere are really only a handful of situations where today's expert practitioners would choose assembly language:\n\nWhen a stand-alone binary executable is required, i.e. one that must execute without recourse to the run-time components or libraries associated with a high-level language; this is perhaps the most common situation \nWhen interacting directly with the hardware, e.g. in a device driver, or when using processor-specific instructions not exploited by or available to the compiler \nWhen extreme optimization is required, e.g. in an inner loop in a processor-intensive algorithm \nWhen a system with severe resource constraints (e.g. an embedded system) must be hand-coded to maximize the use of limited resources; but this is becoming less common as processor price/performance improves \nWhen no high-level language exists, e.g. on a new or specialized processor \nFew programmers today need to use assembly language on a day-to-day basis. For performance-critical applications, a low-level language like C would generally be chosen. It is now very difficult to write a C program which is less efficient than an assembly language program. However, a strong case can be made that any serious programmer should learn at least one assembly language – to understand the fine structure of how computers function, to anticipate how application design choices can improve generated code, and to appreciate all the work high-level languages save.\n\n\n[edit] Typical applications\nHand-coded assembly language is typically used in a system's BIOS. This low-level code is used, among other things, to initialize and test the system hardware prior to booting the OS, and is stored in ROM. Once a certain level of hardware initialization has taken place, execution transfers to other code, typically written in higher level languages; but the code running immediately after power is applied is usually written in assembly language. The same is true of most boot loaders.\n\nMany compilers render high-level languages into assembly first before fully compiling, allowing the assembly code to be viewed for debugging and optimization purposes. Relatively low-level languages, such as C, often provide special syntax to embed assembly language directly in the source code. Programs using such facilities, such as the Linux kernel, can then construct abstractions utilizing different assembly language on each hardware platform. The system's portable code can then utilize these processor-specific components through a uniform interface.\n\nAssembly language is also valuable in reverse engineering, since many programs are distributed only in machine code form, and machine code is usually easy to translate into assembly language and carefully examine in this form, but very difficult to translate into a higher-level language. Tools such as the Interactive Disassembler make extensive use of disassembly for such a purpose.
333593
May be you need a scheduler.\n\nIn version of Windows before XP there was an "at" utility, which you could use for scheduling.\nIn Windows XP just open Control panel->Performance and Maintainance->Sheduled tasks and add tasks you want. Interface is very simple.\n\nOr you may need a macros in Word or Excel or something like that.\n\nIn this case, open the Services->Macros in Word/Excel or see the manual of program you are using about macros.